[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal unlinked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
That's strange. Your Bluetooth chip looks like a common one that any Linux kernel version should support: https://ark.intel.com/products/66889/Intel-Centrino-Wireless-N-2230-Single-Band As a quick check, please live boot the original 18.04.0 release: http://old-releases.ubuntu.com/releases/18.04.0/ and verify it was working in that version before any updates. -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797288] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1757008 *** https://bugs.launchpad.net/bugs/1757008 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 1757008, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1757008 Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] -- 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/1797288 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: I tried to install the driver for wifi, but doesn't function, I just can connect to network via ethernet My version of ubuntu is 16.04 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 10 21:38:29 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2018-10-10 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1797288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
siyia, you're welcome to try it yourself from my ACPIDUMP attachment earlier. its not as simple as it normally would be. In some cases, it just causes iasl to segfault. https://github.com/acpica/acpica/issues/414 ** Bug watch added: github.com/acpica/acpica/issues #414 https://github.com/acpica/acpica/issues/414 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
After downgrading core bluetooth device disappeared, and installing most recent one didn't help to bring it back. I am just not enough familiar with linux to be able reinstall it manually. had to reinstall whole ubuntu from scratch - still have same problems. -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797314] Re: fscache: bad refcounting in fscache_op_complete leads to OOPS
** Description changed: SRU Justification - [Impact] A kernel BUG is sometimes observed when using fscache: [4740718.880898] FS-Cache: [4740718.880920] FS-Cache: Assertion failed [4740718.880934] FS-Cache: 0 > 0 is false [4740718.881001] [ cut here ] [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! [4740718.881040] invalid opcode: [#1] SMP - + [4740718.892659] Call Trace: [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] [4740718.895180] [] process_one_work+0x150/0x3f0 [4740718.895966] [] worker_thread+0x11a/0x470 [4740718.896753] [] ? __schedule+0x359/0x980 [4740718.897783] [] ? rescuer_thread+0x310/0x310 [4740718.898581] [] kthread+0xd6/0xf0 [4740718.899469] [] ? kthread_park+0x60/0x60 [4740718.900477] [] ret_from_fork+0x3f/0x70 [4740718.901514] [] ? kthread_park+0x60/0x60 [Problem] - In include/fscache-cache.h, fscache_retrieval_complete reads, in part: + In include/linux/fscache-cache.h, fscache_retrieval_complete reads, in + part: atomic_sub(n_pages, >n_pages); if (atomic_read(>n_pages) <= 0) fscache_op_complete(>op, true); The code is using atomic_sub followed by an atomic_read. This causes two threads doing a decrement of pages to race with each other seeing the op->refcount <= 0 at same time, and end up calling fscache_op_complete in both the threads leading to the OOPS. [Fix] The fix is trivial to use atomic_sub_return instead of two calls. [Testcase] - The user has tested the patch successfully on their fscache/cachefiles setup. + I believe the user has tested the patch successfully on their fscache/cachefiles setup. [Regression Potential] Limited to fscache. Small, comprehensible change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797314 Title: fscache: bad refcounting in fscache_op_complete leads to OOPS Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification - [Impact] A kernel BUG is sometimes observed when using fscache: [4740718.880898] FS-Cache: [4740718.880920] FS-Cache: Assertion failed [4740718.880934] FS-Cache: 0 > 0 is false [4740718.881001] [ cut here ] [4740718.881017] kernel BUG at /usr/src/linux-4.4.0/fs/fscache/operation.c:449! [4740718.881040] invalid opcode: [#1] SMP [4740718.892659] Call Trace: [4740718.893506] [] cachefiles_read_copier+0x3a9/0x410 [cachefiles] [4740718.894374] [] fscache_op_work_func+0x22/0x50 [fscache] [4740718.895180] [] process_one_work+0x150/0x3f0 [4740718.895966] [] worker_thread+0x11a/0x470 [4740718.896753] [] ? __schedule+0x359/0x980 [4740718.897783] [] ? rescuer_thread+0x310/0x310 [4740718.898581] [] kthread+0xd6/0xf0 [4740718.899469] [] ? kthread_park+0x60/0x60 [4740718.900477] [] ret_from_fork+0x3f/0x70 [4740718.901514] [] ? kthread_park+0x60/0x60 [Problem] In include/linux/fscache-cache.h, fscache_retrieval_complete reads, in part: atomic_sub(n_pages, >n_pages); if (atomic_read(>n_pages) <= 0) fscache_op_complete(>op, true); The code is using atomic_sub followed by an atomic_read. This causes two threads doing a decrement of pages to race with each other seeing the op->refcount <= 0 at same time, and end up calling fscache_op_complete in both the threads leading to the OOPS. [Fix] The fix is trivial to use atomic_sub_return instead of two calls. [Testcase] I believe the user has tested the patch successfully on their fscache/cachefiles setup. [Regression Potential] Limited to fscache. Small, comprehensible change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797492] 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 1797492 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: 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/1797492 Title: 18.10 - AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux https://bugzilla.redhat.com/show_bug.cgi?id=1608242 Looks like's it's fixed in kernel 4.18.10 This is the patch: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=3702a0585e64d70d5bf73bf3e943b8d6005b72c1 Other issues this causes is the systemd-udevd hanging on reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797492] [NEW] 18.10 - AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load
Public bug reported: Description:Ubuntu Cosmic Cuttlefish (development branch) Release:18.10 4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux https://bugzilla.redhat.com/show_bug.cgi?id=1608242 Looks like's it's fixed in kernel 4.18.10 This is the patch: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=3702a0585e64d70d5bf73bf3e943b8d6005b72c1 Other issues this causes is the systemd-udevd hanging on reboot. ** Affects: linux (Ubuntu) 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/1797492 Title: 18.10 - AMD AGESA 1.0.0.4 bios causes kvm_amd to hang on load Status in linux package in Ubuntu: New Bug description: Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux https://bugzilla.redhat.com/show_bug.cgi?id=1608242 Looks like's it's fixed in kernel 4.18.10 This is the patch: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=3702a0585e64d70d5bf73bf3e943b8d6005b72c1 Other issues this causes is the systemd-udevd hanging on reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer
I was able to verify that the fix in Xenial 4.4.0-138.164 works. The procedure was the same as in comment #4 [1], but with less run time. [1] https://bugs.launchpad.net/ubuntu/+source/linux- gcp/+bug/1788222/comments/4 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1788222 Title: Bugfix for handling of shadow doorbell buffer Status in linux package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: This request is to pull in the following patch for NVMe bug from https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel: === This patch adds full memory barrier into nvme_dbbuf_update_and_check_event function to ensure that the shadow doorbell is written before reading EventIdx from memory. This is a critical bugfix for initial patch that added support for shadow doorbell into NVMe driver[...]. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] Re: Wifi adapter not found after suspend (iwlwifi)
Solved by blacklisting Kernel Module "dell_rbtn". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
Thanks for you help. doubt about environmental reason because this laptop also has windows and everything continue to work fine in windows. even tried to reconnect my headsets in windows - still works. but it not convenient to boot in to win in order to use my headset. Anyway- trying to downgrade my kernel, will key you posted. -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
** Attachment added: "Dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5200205/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal linked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200190/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200193/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200181/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200185/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200183/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200188/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200191/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] Re: Wifi adapter not found after suspend (iwlwifi)
apport information ** Tags added: apport-collected ** Description changed: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: hardy 1061 F pulseaudio + /dev/snd/controlC0: hardy 1061 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-10-11 (0 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + MachineType: Dell Inc. Inspiron 7537 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-36-generic N/A + linux-backports-modules-4.15.0-36-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/24/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A16 + dmi.board.name: 0MFY55 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: + dmi.product.family: Shark Bay ULT + dmi.product.name: Inspiron 7537 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200180/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature:
[Kernel-packages] [Bug 1788073] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200194/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200192/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] Re: Wifi adapter not found after suspend (iwlwifi)
The problem also affects the "airplane mode". The loss of wifi connectivity can be restored by entering and exiting airplane mode provides the option to reenable the wifi board. Additionally, using the fn+ key combination airplane mode can be manually entered, but not exited. (which seems to be a common 18.04 problem, with a simple web search). I have just updated to the latest Dell firmware version for this device with no improvement. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200189/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200186/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200187/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200182/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788073] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1788073/+attachment/5200184/+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/1788073 Title: Wifi adapter not found after suspend (iwlwifi) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I am finding that the network adapter " Network controller: Intel Corporation Wireless 7260 (rev bb) " (iwlwifi) is reported as disabled, or not present after a lengthy suspend. This is an identical issue to those reported for Realtek, but I have not found an existing report for Intel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817 This was no a problem in 16.04 or 17.10 with the identical hardware. 18.04 was installed clean. Happy to provide more information, however, I am not exactly sure what information to provide? Thanks in advance, Description: Ubuntu 18.04.1 LTS Release: 18.04 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hardy 1061 F pulseaudio /dev/snd/controlC0: hardy 1061 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 7537 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=8686f213-39e9-4bc8-9a27-d3bf664af82c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0MFY55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0MFY55:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795598] Re: linux: -proposed tracker
** Summary changed: - linux: 3.2.0-137.183 -proposed tracker + linux: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Assignee: Brad Figg (brad-figg) => (unassigned) ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: Brad Figg (brad-figg) => (unassigned) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Brad Figg (brad-figg) => (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/1795598 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal unlinked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796944] Re: linux-aws: 4.18.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1796944 Title: linux-aws: 4.18.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1002.3 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: 1796346 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 713556] Re: Sharkoon Fireglider mouse is wrongly detected as a joystick
** Merge proposal linked: https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/343053 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/713556 Title: Sharkoon Fireglider mouse is wrongly detected as a joystick Status in udev: New Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-evdev I've been programming a game in SDL and I was surprised that SDL was reporting that 1 joystick was connected when there were none. SDL provides the name as "A4Tech USB Full Speed". "ls /dev/input" shows one joystick connected: by-idevent0 event2 event4 event6 event8 micemouse1 by-path event1 event3 event5 event7 js0 mouse0 lsusb shows my mouse as: Bus 003 Device 003: ID 09da:8090 A4 Tech Co., Ltd Unplugging the mouse makes /dev/input/js0 disappear. --- Architecture: amd64 DistroRelease: Ubuntu 10.10 InstallationMedia: elementary 0.2 Jupiter - Release i386 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: maverick Uname: Linux 2.6.37-02063706-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/udev/+bug/713556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
[5.334548] Waiting 300 sec before mounting root device... This is not a kernel issue, but an emergent bug from the combination of us specifying rootdelay=300 in azure images, and the fact that the minimal image boots initramfsless. The kernel interprets 'rootdelay' differently than Ubuntu initramfs-tools does. ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed Status in linux-azure package in Ubuntu: Invalid Bug description: Hi, We're planning to share a new Cosmic minimal image for Azure including the linux-azure custom kernel. I have found boot speed increase from ~55s in non minimal image to over 6mins for minimal image. I have gathered boot log, systemd logs and cloud-init logs for this instance @ https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/minimal/. You can see the same logs for the non minimal image @ https://private-fileshare.canonical.com/~philroche /azure-cosmic-20180927/base Most of the time seems to be spent in crng and "task swapper/0:1" (?) [5.774760] sd 3:0:0:0: [sdc] Attached SCSI disk [ 71.388989] random: crng init done [ 242.656057] INFO: task swapper/0:1 blocked for more than 120 seconds. [ 242.688434] Not tainted 4.15.0-1018-azure #18-Ubuntu Source: https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/minimal/iengal3seeSee-vm-imagedebug-boot.log Please let me know if you need any more information or would like me to launch an instance for testing. I understand that minimal images are intended to boot without initramfs but I did install initramfs-tools in another test image which did result in much better boot times. See https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180928/ for logs. Minimal image boot time 48.784s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797200] Re: [Bionic] ACPI / PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set
** Description changed: [Impact] Currently, we use the ACPI processor ID only for the leaf/processor nodes as the specification states it must match the value of the ACPI processor ID field in the processor’s entry in the MADT. - However, if a PPTT structure represents a processors group, it matches a processor container UID in the namespace and the ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI processor ID is valid. - - Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be consistent instead of using table offset as it's currently done for non-leaf nodes. - - Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology Table parsing) + However, if a PPTT structure represents a processors group, it matches a + processor container UID in the namespace and the + ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI + processor ID is valid. + Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be + consistent instead of using table offset as it's currently done for non- + leaf nodes. + + Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology Table + parsing) [Fix] This patch in is 4.18: 30998033f62a ACPI / PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set [Test] + -- testcase -- + #!/bin/bash + + stress-ng -q --vm 100 --vm-bytes 1G --cpu 210 --timeout 2400s --metrics-brief & + pid=$! + + for i in {1..210}; do + num=$((RANDOM%10+$i)) + echo "Offline CPU $num" + echo 0 > /sys/devices/system/cpu/cpu$num/online || exit 1 + sleep 3s + echo "Online CPU $num" + echo 1 > /sys/devices/system/cpu/cpu$num/online || exit 1 + done + + kill -9 $pid + + Executed the test case with stock Bionic kernel and with Bionic kernel with patches applied. No system hang or crash was observed. On Cavium CN99XX Thunder X2 system. [Regression Potential] + Regression tested on Cavium Thunder X2 CN99XX system, and none were found. Regression risk is low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797200 Title: [Bionic] ACPI / PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Currently, we use the ACPI processor ID only for the leaf/processor nodes as the specification states it must match the value of the ACPI processor ID field in the processor’s entry in the MADT. However, if a PPTT structure represents a processors group, it matches a processor container UID in the namespace and the ACPI_PPTT_ACPI_PROCESSOR_ID_VALID flag indicates whether the ACPI processor ID is valid. Let's use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be consistent instead of using table offset as it's currently done for non-leaf nodes. Fixes: 2bd00bcd73e5 (ACPI/PPTT: Add Processor Properties Topology Table parsing) [Fix] This patch in is 4.18: 30998033f62a ACPI / PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set [Test] -- testcase -- #!/bin/bash stress-ng -q --vm 100 --vm-bytes 1G --cpu 210 --timeout 2400s --metrics-brief & pid=$! for i in {1..210}; do num=$((RANDOM%10+$i)) echo "Offline CPU $num" echo 0 > /sys/devices/system/cpu/cpu$num/online || exit 1 sleep 3s echo "Online CPU $num" echo 1 > /sys/devices/system/cpu/cpu$num/online || exit 1 done kill -9 $pid Executed the test case with stock Bionic kernel and with Bionic kernel with patches applied. No system hang or crash was observed. On Cavium CN99XX Thunder X2 system. [Regression Potential] Regression tested on Cavium Thunder X2 CN99XX system, and none were found. Regression risk is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797202] Re: [Bionic] arm64: topology: Avoid checking numa mask for scheduler MC selection
** Description changed: [Impact] The numa mask subset check can often lead to system hang or crash during CPU hotplug and system suspend operation if NUMA is disabled. This is mostly observed on HMP systems where the CPU compute capacities are different and ends up in different scheduler domains. Since cpumask_of_node is returned instead core_sibling, the scheduler is confused with incorrect cpumasks(e.g. one CPU in two different sched domains at the same time) on CPU hotplug. [Fix] The following patch fixes this issue: e156ab71a974 arm64: topology: Avoid checking numa mask for scheduler MC selection [Test] + -- testcase -- + + #!/bin/bash + + stress-ng -q --vm 100 --vm-bytes 1G --cpu 210 --timeout 2400s --metrics-brief & + pid=$! + + for i in {1..210}; do + num=$((RANDOM%10+$i)) + echo "Offline CPU $num" + echo 0 > /sys/devices/system/cpu/cpu$num/online || exit 1 + sleep 3s + echo "Online CPU $num" + echo 1 > /sys/devices/system/cpu/cpu$num/online || exit 1 + done + + kill -9 $pid + + Executed the test case with stock Bionic kernel and with Bionic kernel with patches applied. No system hang or crash was observed. On Cavium CN99XX Thunder X2 system. [Regression Potential] + Regression tested on Cavium Thunder X2 CN99XX system, and none were found. Regression risk is low. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797202 Title: [Bionic] arm64: topology: Avoid checking numa mask for scheduler MC selection Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The numa mask subset check can often lead to system hang or crash during CPU hotplug and system suspend operation if NUMA is disabled. This is mostly observed on HMP systems where the CPU compute capacities are different and ends up in different scheduler domains. Since cpumask_of_node is returned instead core_sibling, the scheduler is confused with incorrect cpumasks(e.g. one CPU in two different sched domains at the same time) on CPU hotplug. [Fix] The following patch fixes this issue: e156ab71a974 arm64: topology: Avoid checking numa mask for scheduler MC selection [Test] -- testcase -- #!/bin/bash stress-ng -q --vm 100 --vm-bytes 1G --cpu 210 --timeout 2400s --metrics-brief & pid=$! for i in {1..210}; do num=$((RANDOM%10+$i)) echo "Offline CPU $num" echo 0 > /sys/devices/system/cpu/cpu$num/online || exit 1 sleep 3s echo "Online CPU $num" echo 1 > /sys/devices/system/cpu/cpu$num/online || exit 1 done kill -9 $pid Executed the test case with stock Bionic kernel and with Bionic kernel with patches applied. No system hang or crash was observed. On Cavium CN99XX Thunder X2 system. [Regression Potential] Regression tested on Cavium Thunder X2 CN99XX system, and none were found. Regression risk is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759330] Re: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296!
Getting the exact same BUG when my screen tries to turn on back after lock + screen off.. this freeze my station and have to reset it. can I do anything to help ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759330 Title: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296! Status in linux package in Ubuntu: Expired Bug description: dont know it just gave me the error messege ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm 966 F pulseaudio techterror12 1382 F pulseaudio /dev/snd/controlC1: gdm 966 F pulseaudio techterror12 1382 F pulseaudio Date: Tue Mar 27 12:22:22 2018 Failure: oops HibernationDevice: RESUME=UUID=b83a3832-8bd2-46ee-b79e-9bb804e1613d InstallationDate: Installed on 2018-02-25 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= acpi_backight_native vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: kernel BUG at /build/linux-bdpCf2/linux-4.15.0/mm/slub.c:296! UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => 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/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails
I built one more test kernel. This test kernel has a pick of commits 83b7739180de1 and 661bb943a98de. The test kernel can also be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792580 Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792580 Title: Mounting SOFS SMB shares fails Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Ubuntu 18.04.1 LTS 4.15.0-33.36-generic cifs-utils 2:6.8-1 Mounting scale-out SMB shares is failing. mount -t cifs -o credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs //s2dscaleout.cbs.com/glance-images /tmp/test_mount mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) What works: * mounting the share from a 16.04 host * mounting standalone smb3 shares Relevant error from the log (full logs attached separately): Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9 STATUS_NETWORK_NAME_DELETED Sep 14 11:12:05 r07-u13 kernel: /build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc0c9 to POSIX err -5 Share server os: Windows Server 2016 10.0.14393 PS C:\Users\jujuadmin> get-smbshare glance-images | fl * ShareState: Online AvailabilityType : ScaleOut ShareType : FileSystemDirectory FolderEnumerationMode : Unrestricted CachingMode : Manual SmbInstance : Default CATimeout : 0 ConcurrentUserLimit : 0 ContinuouslyAvailable : True CurrentUsers : 2 Description : EncryptData : False Name : glance-images Path : C:\ClusterStorage\Volume1\GLANCE-IMAGES Scoped: True ScopeName : S2DSCALEOUT ShadowCopy: False Special : False Temporary : False Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\ --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 7 16:51 seq crw-rw 1 root audio 116, 33 Sep 7 16:51 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R710 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-33-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0YDJK3 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R710 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I built the next test kernel, up to the following commit: e8e9608116593a54915a6ca8e343210e3aa6bce3 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1788997 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792957] Re: Provide mode where all vCPUs on a core must be the same VM
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-October/095982.html ** Description changed: + == SRU Justification == + This patch has been requested by IBM. It provides a mode where all vCPUs + on a core must be the same VM. This is intended for use in + security-conscious settings where users are concerned about possible + side-channel attacks between threads which could perhaps enable one VM + to attack another VM on the same core, or the host. + + == Fix == + linux-next commit: + aa2278644ae5 ("KVM: PPC: Book3S HV: Provide mode where all vCPUs on a core must be the same VM") + + + == Regression Potential == + Low. Changes limited to powerpc. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-09-13 07:12:48 == +++ This bug was initially created as a clone of Bug #171443 +++ Please, add the following patch: http://patchwork.ozlabs.org/patch/968786/ which adds a mode where all vCPUs on a core must be the same VM on POWER8 and POWER9. This is intended for use in security-conscious settings where users are concerned about possible side-channel attacks between threads which could perhaps enable one VM to attack another VM on the same core, or the host. ** Also affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792957 Title: Provide mode where all vCPUs on a core must be the same VM Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == This patch has been requested by IBM. It provides a mode where all vCPUs on a core must be the same VM. This is intended for use in security-conscious settings where users are concerned about possible side-channel attacks between threads which could perhaps enable one VM to attack another VM on the same core, or the host. == Fix == linux-next commit: aa2278644ae5 ("KVM: PPC: Book3S HV: Provide mode where all vCPUs on a core must be the same VM") == Regression Potential == Low. Changes limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-09-13 07:12:48 == +++ This bug was initially created as a clone of Bug #171443 +++ Please, add the following patch: http://patchwork.ozlabs.org/patch/968786/ which adds a mode where all vCPUs on a core must be the same VM on POWER8 and POWER9. This is intended for use in security-conscious settings where users are concerned about possible side-channel attacks between threads which could perhaps enable one VM to attack another VM on the same core, or the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Thursday, 11. October 2018 20:03 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Thursday, 11. October 2018 20:03 UTC - kernel-stable-phase:Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788754 Title: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1788744 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/1788754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792501] Re: [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm)
Bionic SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-October/095980.html ** Description changed: + == SRU Justification == + IBM is requesting this commit in Bionic. It fixes a regression + introduced by upstream commit 4bb3c7a020. + + Without this patch, package installation segfaults inside debian chroot + env in P9 KVM guest with HTM enabled. + + The fix has already landed in Cosmic master-next. + + == Fix == + f14040bca892 ("KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM workarounds") + + == Regression Potential == + Low. This commit fixes an existing regrssion and is specific to powerpc. It has been cc'd to + upstream stable, so has had additional upstream review. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + + == Comment: #0 - Satheesh Rajendran - 2018-09-11 04:10:09 == ---Problem Description--- package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled - + ---Additional Hardware Info--- FW with tm-suspend-mode enabled #cd /sys/firmware/devicetree/base/ibm,opal/fw-features/ #ls -1 tm-suspend-mode enabled name phandle - + qemu-kvm 1:2.11+dfsg-1ubuntu7.4 - - Machine Type = Power9 DD2.2 - + + Machine Type = Power9 DD2.2 + ---Steps to Reproduce--- - 1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on) + 1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on) tried with upstream kernel aswell(same results) create tap device in host # tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up #qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0 -device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0 -serial mon:stdio -enable-kvm -vga none -nographic -kernel /home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0 console=ttyS0,115200 init=/sbin/init initcall_debug -netdev tap,id=mynet1,ifname=tap1,script=no,downscript=no -device virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42 run dhclient inside guest. 2. # mkdir -p stretch # debootstrap stretch /stretch http://httpredir.debian.org/debian # chroot /stretch /# apt-get update && apt-get install -y make gcc ruby python ... [ 32.029474] random: crng init done [ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting [ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip 7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19] - [ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c 419e0074 85270004 394a0001 794a0020 - [ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14 2ea8 40960010 e9090008 + [ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c 419e0074 85270004 394a0001 794a0020 + [ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14 2ea8 40960010 e9090008 - ---uname output--- 4.15.0-34,4.19.0-rc3 - + ---Debugger--- A debugger is not configured - - Contact Information = sathe...@in.ibm.com - - Userspace tool common name: - KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, - Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 + Contact Information = sathe...@in.ibm.com + + Userspace tool common name: + + KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, + Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 Userspace rpm: - KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, - Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 - - The userspace tool has the following bit modes: both + KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, + Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 - Userspace tool obtained from project website: na - - *Additional Instructions for sathe...@in.ibm.com: + The userspace tool has the following bit modes: both + + Userspace tool obtained from project website: na + + *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. - - So latest update taken from https://github.ibm.com/powercloud/icp-ppc64le/issues/470 + So latest update taken from https://github.ibm.com/powercloud/icp- + ppc64le/issues/470 was able to recreate segfault using TM test cases /linux/tools/testing/selftests/powerpc/tm # ./tm-vmxcopy test: tm_vmxcopy tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty !! child died by signal 11
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I built the next test kernel, up to the following commit: 6a8b25abf1b79db6877645335c73ad6a5061d9b0 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1752961 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: See attached dmesg outputs for booting kernels 4.11.x (working) and 4.13.x (not working). dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x. btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have been discovered by the kernel. The btrfs RAID1 filesystem mounts, and everything is good. dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x. btrfs scans for devices after only 2 (sda, sdb) of the devices have been discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed to read the system array: -5"). The remaining 2 devices (sdc, sdd) are discovered by the kernel immediately afterward. At the end of the log, I run `btrfs device scan` and mount the filesystem manually. Hardware: HP ProLiant MicroServer Gen8 4x WDC WD20EFRX --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: aplay: device_list:270: no soundcards found... ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: arecord: device_list:270: no soundcards found... DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-10-15 (933 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ rootdelay=10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/16/2015 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792209] Re: net: hns: Avoid hang when link is changed while handling packets
Verified - has survived several minutes of: while :; do sudo ethtool -s enahisic2i1 speed 1000 duplex full sudo service systemd-networkd restart sleep 5 sudo ethtool -s enahisic2i1 speed 10 duplex half sudo service systemd-networkd restart sleep 5 done With ping/iperf still responding. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792209 Title: net: hns: Avoid hang when link is changed while handling packets Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] If an admin uses ethtool to change the link speed or duplex setting while the hardware is still processing packets, a hardware hang may result. [Test Case] While traffic is in-progress, use ethtool to change link speed/duplex. [Fix] Fixes have been applied upstream: 455c4401fe7a5 net: hns: add netif_carrier_off before change speed and duplex 31fabbee8f5c6 net: hns: add the code for cleaning pkt in chip [Regression Risk] The only Ubuntu-supported system that uses this driver is the HiSilicon D05 board, on which the fix was explicitly tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792501] Re: [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm)
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792501 Title: [Ubuntu18.04][Power9][DD2.2]package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled (kvm) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Committed Bug description: == SRU Justification == IBM is requesting this commit in Bionic. It fixes a regression introduced by upstream commit 4bb3c7a020. Without this patch, package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled. The fix has already landed in Cosmic master-next. == Fix == f14040bca892 ("KVM: PPC: Book3S HV: Fix guest r11 corruption with POWER9 TM workarounds") == Regression Potential == Low. This commit fixes an existing regrssion and is specific to powerpc. It has been cc'd to upstream stable, so has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Satheesh Rajendran - 2018-09-11 04:10:09 == ---Problem Description--- package installation segfaults inside debian chroot env in P9 KVM guest with HTM enabled ---Additional Hardware Info--- FW with tm-suspend-mode enabled #cd /sys/firmware/devicetree/base/ibm,opal/fw-features/ #ls -1 tm-suspend-mode enabled name phandle qemu-kvm 1:2.11+dfsg-1ubuntu7.4 Machine Type = Power9 DD2.2 ---Steps to Reproduce--- 1. Boot a P9 KVM guest Ubuntu 18.04 (with cap-htm=on, bydefault it is on) tried with upstream kernel aswell(same results) create tap device in host # tunctl -t tap1 -u `whoami`;brctl addif virbr0 tap1;ifconfig tap1 up #qemu-system-ppc64 -enable-kvm -M pseries -m 8192 -smp 4 -drive file=/home/sath/ubuntu-18.04-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0 -device virtio-scsi-pci,id=drive-scsi0 -device scsi-hd,drive=drive-scsi0 -serial mon:stdio -enable-kvm -vga none -nographic -kernel /home/sath/vmlinux_4.19 -append root=/dev/sda2 rw console=tty0 console=ttyS0,115200 init=/sbin/init initcall_debug -netdev tap,id=mynet1,ifname=tap1,script=no,downscript=no -device virtio-net,netdev=mynet1,mac=52:55:00:d1:55:42 run dhclient inside guest. 2. # mkdir -p stretch # debootstrap stretch /stretch http://httpredir.debian.org/debian # chroot /stretch /# apt-get update && apt-get install -y make gcc ruby python ... [ 32.029474] random: crng init done [ 32.029477] random: 7 urandom warning(s) missed due to ratelimiting [ 500.300835] dpkg-deb[8704]: segfault (11) at c00037fa nip 7fffac2d098c lr 7fffac2d08c4 code 1 in libc-2.24.so[7fffac17+19] [ 500.300863] dpkg-deb[8704]: code: 4828 eb090010 2eb8 4096006c 419e0074 85270004 394a0001 794a0020 [ 500.300881] dpkg-deb[8704]: code: 71280001 408200a0 1d2a0018 7d2b4a14 2ea8 40960010 e9090008 ---uname output--- 4.15.0-34,4.19.0-rc3 ---Debugger--- A debugger is not configured Contact Information = sathe...@in.ibm.com Userspace tool common name: KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 Userspace rpm: KVM Guest: Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27, Chroot inside KVM Guest: Debian GLIBC 2.24-11+deb9u3) stable release version 2.24 The userspace tool has the following bit modes: both Userspace tool obtained from project website: na *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. So latest update taken from https://github.ibm.com/powercloud/icp- ppc64le/issues/470 was able to recreate segfault using TM test cases /linux/tools/testing/selftests/powerpc/tm # ./tm-vmxcopy test: tm_vmxcopy tags: git_version:v4.19-rc3-0-g11da3a7f84f1-dirty !! child died by signal 11 failure: tm_vmxcopy this particular test on being run gets a signal 11 [267132.434651] tm-vmxcopy[641]: unhandled signal 11 at 0001 nip 000104ba122c lr 000104ba11e4 code 30001 [267253.708795] tm-vmxcopy[7861]: unhandled signal 11 at 0001 nip 00012a31122c lr 00012a3111e4 code 30001 [267385.064533] tm-vmxcopy[13314]: unhandled signal 11 at 0001 nip 0001235f122c lr 0001235f11e4 code 30001 == Comment: #12 - Michael Neuling - 2018-09-13 00:34:16 == Fixes r11 corruption. == Comment: #14 -
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
I finally tested the deb packages and it's working fine. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: 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: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795653] Re: 87cdf3148b11 was never backported to 4.15
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-October/095979.html ** Description changed: + + == SRU Justification == + Commit 87cdf3148b11 fixes a regression introduced by commit + 5efec5c655dd. However, it has not never landed in Bionic. Requesting + this commit in Bionic, so we don't have to wait for it to come down from + upstream stable. + + + == Fix == + 87cdf3148b11 ("xfrm: Verify MAC header exists before overwriting eth_hdr(skb)->h_proto") + + == Regression Potential == + Low. This commit fixes and existing regression by making sure teh MAC + header exists. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795653 Title: 87cdf3148b11 was never backported to 4.15 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == Commit 87cdf3148b11 fixes a regression introduced by commit 5efec5c655dd. However, it has not never landed in Bionic. Requesting this commit in Bionic, so we don't have to wait for it to come down from upstream stable. == Fix == 87cdf3148b11 ("xfrm: Verify MAC header exists before overwriting eth_hdr(skb)->h_proto") == Regression Potential == Low. This commit fixes and existing regression by making sure teh MAC header exists. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. Hello, After a few days of troubleshooting a problem with L2TP and IPSec a fellow from ServerFault pointed out that my problem is a known bug fixed by 87cdf3148b11 commit which wasn't backported on 4.15 kernel. Ubuntu 4.15.0-36.39-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1797062 Title: linux-gcp: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1797065 Title: linux-kvm: 4.15.0-1025.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
https://bugzilla.kernel.org/show_bug.cgi?id=201379 -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1797080 Title: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1797066 Title: linux-aws: 4.15.0-1025.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1797061 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788754 Title: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Committed Status in Kernel SRU Workflow promote-to-updates series: Fix Committed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
This bug was fixed in the package linux-azure - 4.15.0-1023.24~14.04.1 --- linux-azure (4.15.0-1023.24~14.04.1) trusty; urgency=medium * linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker (LP: #1788754) * linux-azure: 4.15.0-1023.24 -proposed tracker (LP: #1788751) * [Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is busy (LP: #1786313) - hv_netvsc: Fix napi reschedule while receive completion is busy [ Ubuntu: 4.15.0-34.37 ] * linux: 4.15.0-34.37 -proposed tracker (LP: #1788744) * Bionic update: upstream stable patchset 2018-08-09 (LP: #1786352) - MIPS: c-r4k: Fix data corruption related to cache coherence - MIPS: ptrace: Expose FIR register through FP regset - MIPS: Fix ptrace(2) PTRACE_PEEKUSR and PTRACE_POKEUSR accesses to o32 FGRs - KVM: Fix spelling mistake: "cop_unsuable" -> "cop_unusable" - affs_lookup(): close a race with affs_remove_link() - fs: don't scan the inode cache before SB_BORN is set - aio: fix io_destroy(2) vs. lookup_ioctx() race - ALSA: timer: Fix pause event notification - do d_instantiate/unlock_new_inode combinations safely - mmc: sdhci-iproc: remove hard coded mmc cap 1.8v - mmc: sdhci-iproc: fix 32bit writes for TRANSFER_MODE register - mmc: sdhci-iproc: add SDHCI_QUIRK2_HOST_OFF_CARD_ON for cygnus - libata: Blacklist some Sandisk SSDs for NCQ - libata: blacklist Micron 500IT SSD with MU01 firmware - xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent - drm/vmwgfx: Fix 32-bit VMW_PORT_HB_[IN|OUT] macros - arm64: lse: Add early clobbers to some input/output asm operands - powerpc/64s: Clear PCR on boot - IB/hfi1: Use after free race condition in send context error path - IB/umem: Use the correct mm during ib_umem_release - idr: fix invalid ptr dereference on item delete - Revert "ipc/shm: Fix shmat mmap nil-page protection" - ipc/shm: fix shmat() nil address after round-down when remapping - mm/kasan: don't vfree() nonexistent vm_area - kasan: free allocated shadow memory on MEM_CANCEL_ONLINE - kasan: fix memory hotplug during boot - kernel/sys.c: fix potential Spectre v1 issue - KVM: s390: vsie: fix < 8k check for the itdba - KVM: x86: Update cpuid properly when CR4.OSXAVE or CR4.PKE is changed - kvm: x86: IA32_ARCH_CAPABILITIES is always supported - powerpc/64s: Improve RFI L1-D cache flush fallback - powerpc/pseries: Restore default security feature flags on setup - powerpc/64s: Fix section mismatch warnings from setup_rfi_flush() - MIPS: generic: Fix machine compatible matching - mac80211: mesh: fix wrong mesh TTL offset calculation - ARC: Fix malformed ARC_EMUL_UNALIGNED default - ptr_ring: prevent integer overflow when calculating size - arm64: dts: rockchip: fix rock64 gmac2io stability issues - arm64: dts: rockchip: correct ep-gpios for rk3399-sapphire - libata: Fix compile warning with ATA_DEBUG enabled - selftests: sync: missing CFLAGS while compiling - selftest/vDSO: fix O= - selftests: pstore: Adding config fragment CONFIG_PSTORE_RAM=m - selftests: memfd: add config fragment for fuse - ARM: OMAP2+: timer: fix a kmemleak caused in omap_get_timer_dt - ARM: OMAP3: Fix prm wake interrupt for resume - ARM: OMAP2+: Fix sar_base inititalization for HS omaps - ARM: OMAP1: clock: Fix debugfs_create_*() usage - tls: retrun the correct IV in getsockopt - xhci: workaround for AMD Promontory disabled ports wakeup - IB/uverbs: Fix method merging in uverbs_ioctl_merge - IB/uverbs: Fix possible oops with duplicate ioctl attributes - IB/uverbs: Fix unbalanced unlock on error path for rdma_explicit_destroy - arm64: dts: rockchip: Fix DWMMC clocks - ARM: dts: rockchip: Fix DWMMC clocks - iwlwifi: mvm: fix security bug in PN checking - iwlwifi: mvm: fix IBSS for devices that support station type API - iwlwifi: mvm: always init rs with 20mhz bandwidth rates - NFC: llcp: Limit size of SDP URI - rxrpc: Work around usercopy check - MD: Free bioset when md_run fails - md: fix md_write_start() deadlock w/o metadata devices - s390/dasd: fix handling of internal requests - xfrm: do not call rcu_read_unlock when afinfo is NULL in xfrm_get_tos - mac80211: round IEEE80211_TX_STATUS_HEADROOM up to multiple of 4 - mac80211: fix a possible leak of station stats - mac80211: fix calling sleeping function in atomic context - cfg80211: clear wep keys after disconnection - mac80211: Do not disconnect on invalid operating class - mac80211: Fix sending ADDBA response for an ongoing session - gpu: ipu-v3: pre: fix device node leak in ipu_pre_lookup_by_phandle - gpu: ipu-v3: prg: fix device node leak in ipu_prg_lookup_by_phandle - md raid10: fix NULL deference in handle_write_completed() - drm/exynos: g2d: use monotonic timestamps -
[Kernel-packages] [Bug 1796253] Re: With one flash drive connected other flash drive doesn't connect anymore
Here dmesg output. I have tried to do steps as you explained. [0.00] microcode: microcode updated early to revision 0x20, date = 2018-04-10 [0.00] Linux version 4.19.0-041900rc7-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #201810071631 SMP Sun Oct 7 16:33:10 UTC 2018 [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.19.0-041900rc7-generic root=UUID=aed0a586-4802-41ed-b85a-dce4c8765b14 ro quiet splash vt.handoff=7 usbcore.dyndbg=+p [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d3ff] usable [0.00] BIOS-e820: [mem 0x0009d400-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xa9a6dfff] usable [0.00] BIOS-e820: [mem 0xa9a6e000-0xaa976fff] ACPI NVS [0.00] BIOS-e820: [mem 0xaa977000-0xaa999fff] usable [0.00] BIOS-e820: [mem 0xaa99a000-0xaa99efff] ACPI NVS [0.00] BIOS-e820: [mem 0xaa99f000-0xaf2befff] usable [0.00] BIOS-e820: [mem 0xaf2bf000-0xaf6befff] reserved [0.00] BIOS-e820: [mem 0xaf6bf000-0xaf7befff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf7bf000-0xaf7fefff] ACPI data [0.00] BIOS-e820: [mem 0xaf7ff000-0xaf7f] usable [0.00] BIOS-e820: [mem 0xaf80-0xafff] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfeb0-0xfeb03fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xffb0-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00044eff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.7 present. [0.00] DMI: TOSHIBA SATELLITE L855/Portable PC, BIOS 6.70 04/15/2013 [0.00] tsc: Fast TSC calibration using PIT [0.00] tsc: Detected 2394.782 MHz processor [0.002492] e820: update [mem 0x-0x0fff] usable ==> reserved [0.002494] e820: remove [mem 0x000a-0x000f] usable [0.002502] last_pfn = 0x44f000 max_arch_pfn = 0x4 [0.002507] MTRR default type: uncachable [0.002508] MTRR fixed ranges enabled: [0.002509] 0-9 write-back [0.002510] A-B uncachable [0.002511] C-E7FFF write-protect [0.002511] E8000-E write-combining [0.002512] F-F write-protect [0.002513] MTRR variable ranges enabled: [0.002514] 0 base 0 mask F8000 write-back [0.002515] 1 base 08000 mask FC000 write-back [0.002516] 2 base 0AF80 mask FFF80 uncachable [0.002517] 3 base 0B000 mask FF000 uncachable [0.002518] 4 base 0FF80 mask FFF80 write-protect [0.002519] 5 base 1 mask F write-back [0.002520] 6 base 2 mask E write-back [0.002521] 7 base 4 mask F8000 write-back [0.002521] 8 base 44F00 mask FFF00 uncachable [0.002522] 9 base 45000 mask FF000 uncachable [0.003338] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.003483] last_pfn = 0xaf800 max_arch_pfn = 0x4 [0.014624] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] mapped at [(ptrval)] [0.014964] Scanning 1 areas for low memory corruption [0.014966] Base memory trampoline at [(ptrval)] 97000 size 24576 [0.014972] BRK [0x171001000, 0x171001fff] PGTABLE [0.014974] BRK [0x171002000, 0x171002fff] PGTABLE [0.014975] BRK [0x171003000, 0x171003fff] PGTABLE [0.015022] BRK [0x171004000, 0x171004fff] PGTABLE [0.015024] BRK [0x171005000, 0x171005fff] PGTABLE [0.015144] BRK [0x171006000, 0x171006fff] PGTABLE [0.015224] BRK [0x171007000, 0x171007fff] PGTABLE [0.015237] BRK [0x171008000, 0x171008fff] PGTABLE [0.015281] BRK [0x171009000, 0x171009fff]
[Kernel-packages] [Bug 1794067] Re: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34
Can you next test 4.15.0-18: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/14779251 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794067 Title: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Hello, just found a bug in selinux. Whats going wrong: Copy a link with "-a" option while selinux is on. steps to reproduce: ~$ mkdir -p a/b ~$ ln -s b a/c ~$ cp -a a b cp: failed to restore the default file creation context: Invalid argument Results of my investigation: The "cp" of coreutils is calling "setfscreatecon (NULL)" to restore the default file creation context (coreutils-8.30/src/copy.c:1771) as it is stated in the selinux api (/libselinux/include/selinux/selinux.h:71). As we see in the result of strace below, the kernel returns an -1 on try to restore the default file creation context. So in my opinion is the bug has to be in the selinux_setprocattr method in the security/selinux/hooks.c file. Part of "strace cp -a a b" lgetxattr("a/c", "security.selinux", "system_u:object_r:user_home_dir_t:s0", 255) = 37 readlink("a/c", "b", 2) = 1 symlink("b", "b/a/c") = 0 open("/proc/self/task/2136/attr/fscreate", O_RDWR|O_CLOEXEC) = 3 write(3, NULL, 0) = -1 EINVAL (Invalid argument) close(3) = 0 open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0 read(3, "# Locale name alias data base.\n#"..., 4096) = 2995 read(3, "", 4096) = 0 close(3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
It's possible this is happening because I'm cross compiling. I'll build the packages in a PPA, so it is a native compile. The PPA will be located at: https://launchpad.net/~jsalisbury/+archive/ubuntu/1761379 It is currently building and should be done in an hour or two. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788754 Title: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788754] Re: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker
Testing complete. ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788754 Title: linux-azure: 4.15.0-1023.24~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795017] Re: linux-azure on cosmic minimal image boot speed
Myself and @kamalmostafa spoke and the issue is not obvious especially as linux-azure is installed in the base image too which does not exhibit the issue. Although not obvious @kamalmostafa did suspect the issue to lie somewhere with random number generation and a related package/kernel patch. One line of investigation is to check the package diff between the minimal image with initramfs-tools installed and the image without that installed. That diff is @ https://pastebin.canonical.com/p/7hJTSQHbyD/ Another possibility is to check the package diff between base and minimal. That diff is @ https://pastebin.canonical.com/p/B9m7GbsFhs/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1795017 Title: linux-azure on cosmic minimal image boot speed Status in linux-azure package in Ubuntu: New Bug description: Hi, We're planning to share a new Cosmic minimal image for Azure including the linux-azure custom kernel. I have found boot speed increase from ~55s in non minimal image to over 6mins for minimal image. I have gathered boot log, systemd logs and cloud-init logs for this instance @ https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/minimal/. You can see the same logs for the non minimal image @ https://private-fileshare.canonical.com/~philroche /azure-cosmic-20180927/base Most of the time seems to be spent in crng and "task swapper/0:1" (?) [5.774760] sd 3:0:0:0: [sdc] Attached SCSI disk [ 71.388989] random: crng init done [ 242.656057] INFO: task swapper/0:1 blocked for more than 120 seconds. [ 242.688434] Not tainted 4.15.0-1018-azure #18-Ubuntu Source: https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180927/minimal/iengal3seeSee-vm-imagedebug-boot.log Please let me know if you need any more information or would like me to launch an instance for testing. I understand that minimal images are intended to boot without initramfs but I did install initramfs-tools in another test image which did result in much better boot times. See https://private-fileshare.canonical.com/~philroche/azure- cosmic-20180928/ for logs. Minimal image boot time 48.784s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: linux (Ubuntu Bionic) Importance: Medium => High ** Changed in: linux (Ubuntu Cosmic) Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
** Bug watch added: Linux Kernel Bug Tracker #201379 https://bugzilla.kernel.org/show_bug.cgi?id=201379 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201379 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
This issue started with the upgrade to 18.10 beta. I was not having it before. I installed the V4.19-rc7 and still have the issue though it seems to be happening less frequently. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in linux package in Ubuntu: Confirmed Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
Sorry i couldn't figure out how to close the bug. The issue was on my end. On 10/11/2018 01:50 PM, Cristian Aravena Romero wrote: > @EoflaOE > > You could try the version [0]'Ubuntu Desktop > 18.04' > [0] https://www.ubuntu.com/#download > > Best regards, > -- > Cristian Aravena Romero (caravena) > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
I'd like to perform a "Reverse" bisect to figure out what commit fixes this bug. We need to identify the last kernel version that had the bug, and the first kernel version that fixed the bug. Can you test the following kernels and report back: v4.6 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ v4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/ V4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ You don't have to test every kernel, just up until the first kernel that does not have the bug. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345
Thanks for the update. Marking as "invalid". ** Changed in: ubuntu-power-systems Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775527 Title: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345 Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: == Comment: #0 - Chanh H. Nguyen - 2016-09-08 15:01:30 == We have installed 16.04.1 on our guest and running IO stress test against via virtual qlogic disk. After running around 8 hrs, this error popping up "xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these errors "xfs_log_force: error -5 returned" fill up all the log. Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error: block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32 Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9): xfs_do_force_shutdown(0x8) called from line 3433 of file /build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address = 0xd37951f4 Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error: block 0x703d54 ("xlog_iodone") error 5 numblks 64 Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9): xfs_do_force_shutdown(0x2) called from line 1197 of file /build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address = 0xd37a4c00 Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error Detected. Shutting down filesystem Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the filesystem and rectify the problem(s) follow with all of these error that quickly fill up dmesg log Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted filesystem without journal. Opts: (null) Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force: error -5 returned. Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force: error -5 returned. == Comment: #1 - Chanh H. Nguyen - 2016-09-08 15:02:27 == We recently re-created this bug on our new system "cressg2" which is using a different SAN on kernel -36. My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test, and it is hitting "xfs_log_force: error -5 returned" problem after it runs the tests for 15 hours. It is using our lab storage (SVC SAN storage configuation with access to DS8000 Volume) and switch, compare to tinyg3, so it is using different storage and fabric switch. root@cressg2:~# uname -a Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux [Wed Sep 7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:49 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:27:56 2016] XFS (vdb8): xfs_log_force: error -5 returned. [Wed Sep 7 10:28:18 2016] XFS (vdb8):
[Kernel-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
@EoflaOE You could try the version [0]'Ubuntu Desktop > 18.04' [0] https://www.ubuntu.com/#download Best regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797432 Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Headphone jack stopped working. Speakers do work. Nevermind issue was on my end not sure how to close bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio CurrentDesktop: Unity Date: Thu Oct 11 13:12:34 2018 InstallationDate: Installed on 2018-01-05 (279 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: james 2649 F...m pulseaudio /dev/snd/controlC0: james 2649 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797420] Re: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797420 Title: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04 Status in linux package in Ubuntu: Incomplete Bug description: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e0d9a13c-6776-4241-b61f-164ae076b371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: irda via_ircc UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6712 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: Uknown Chassis Manufacture dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: dmi.product.name: MS-6712 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
Thanks for the update. I'm also building a Launchpad PPA with these changes. That will allow anyone else that wants to test that way. I'll post a link when the PPA is ready. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == IBM is requesting these commits in bionic and cosmic. These commits also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The first patch, commit 2bf1071a8d50, was backported by IBM themself. Description of bug: GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. == Fixes == 2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support") bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily invalid.") f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW transition") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. IBM states the test kernel resolved the bug. -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
The PPA is available here: https://launchpad.net/~jsalisbury/+archive/ubuntu/1792195 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == IBM is requesting these commits in bionic and cosmic. These commits also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The first patch, commit 2bf1071a8d50, was backported by IBM themself. Description of bug: GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. == Fixes == 2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support") bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily invalid.") f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW transition") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. IBM states the test kernel resolved the bug. -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797364] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200090/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
Ok, running a patched kernel now. Let's see if I can still trigger the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb
[Kernel-packages] [Bug 1797420] 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/1797420 Title: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e0d9a13c-6776-4241-b61f-164ae076b371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: irda via_ircc UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6712 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: Uknown Chassis Manufacture dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: dmi.product.name: MS-6712 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797364] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200084/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1792002] Re: Wireless signal extremely weak or not detected
Any update regarding this pl?or shall I consider this as unresolved. I'm still facing the issue even with the recently released kernel v4.15.0.36.38. Am I missing any particular header file(s)? Pl help somebody -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792002 Title: Wireless signal extremely weak or not detected Status in linux package in Ubuntu: Incomplete Bug description: Hi Support, I'm Linux Mint newbie started using from LM v18. I'm using HP245 series laptop with AMD A6-7310 APU & Wifi driver Realtek RTL8723BE. Currently I've migrated from Linux 18 (Sylvia) to Linux 19 (Tara) abt a month ago. I'm facing a WiFi signal problem whenever I've tried to upgrade to Kernel v4.15.0.33 or v4.15.0.34. The Wifi signal strength is either very weak & disconnects frequently or cannot be detected from very small distances (3-5 mtr). I've never had this issue till kernel v4.15.0.32 and everything was working fine and currently I had to downgrade or revert back to 4.15.0.32 again in order to receive signal to write this mail. Kindly resolve this error ASAP as I want to upgrade to the latest version. Regards, Joseph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Comment bridged from LTC Bugzilla
--- Comment From grom...@br.ibm.com 2018-10-11 12:40 EDT--- (In reply to comment #18) > I built a v2 test kernel. All the .debs can be downloaded from: > > http://kernel.ubuntu.com/~jsalisbury/lp1761379/v2 > > Can you test this kernel and see if it resolves this bug? Hi Joseph, Thanks for providing v2. Unfortunately it looks like 'perf' is still missing in linux-tools- common package: root@gromero16:~/perf/~jsalisbury/lp1761379/v2# dpkg -c linux-tools-common_4.15.0-36.40~lp1761379v2_all.deb drwxr-xr-x root/root 0 2018-09-24 10:08 ./ drwxr-xr-x root/root 0 2018-09-24 10:08 ./usr/ drwxr-xr-x root/root 0 2018-09-24 10:08 ./usr/share/ drwxr-xr-x root/root 0 2018-09-24 10:08 ./usr/share/doc/ drwxr-xr-x root/root 0 2018-09-24 10:08 ./usr/share/doc/linux-tools-common/ -rw-r--r-- root/root140984 2018-09-24 10:08 ./usr/share/doc/linux-tools-common/changelog.Debian.gz -rw-r--r-- root/root 1292 2018-09-24 10:08 ./usr/share/doc/linux-tools-common/copyright root@gromero16:~/perf/~jsalisbury/lp1761379/v2# I do see it in an AMD64 .deb file but it's not suitable for PPC64 naturally: root@gromero16:~/perf/~jsalisbury/lp1761379/v2# dpkg -c ./linux-tools-4.15.0-36_4.15.0-36.40~lp1761379v2_amd64.deb | fgrep \/perf -rwxr-xr-x root/root 5549944 2018-10-11 08:09 ./usr/lib/linux-tools-4.15.0-36/perf I also still cant' find any '*jvmti*' in v2 packages. So could you check it again please? Thanks. Regards, Gustavo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797420] Re: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797420/+attachment/5200131/+files/version.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/1797420 Title: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04 Status in linux package in Ubuntu: New Bug description: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e0d9a13c-6776-4241-b61f-164ae076b371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: irda via_ircc UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6712 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: Uknown Chassis Manufacture dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: dmi.product.name: MS-6712 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797420] [NEW] rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04
Public bug reported: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e0d9a13c-6776-4241-b61f-164ae076b371 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: irda via_ircc UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6712 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 0123ABC dmi.chassis.type: 3 dmi.chassis.vendor: Uknown Chassis Manufacture dmi.chassis.version: Version 1.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6712:pvr1.0:rvnMSI:rnMS-6712:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: dmi.product.name: MS-6712 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 staging ** Attachment added: "PCI list" https://bugs.launchpad.net/bugs/1797420/+attachment/5200109/+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/1797420 Title: rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED issues - Ubuntu 18.04 Status in linux package in Ubuntu: New Bug description: In the Linux kernel version 4.15.0-36-generic with the D-Link DWA-121 mini USB WiFi using the rtl8192cu driver on Ubuntu 18.04, it appears that the driver is not controlling the blue LED that blinks when there is download/upload going on, so the LED keeps on. This will cause users of this dongle to open network statistics to see if there is download/upload going on rather than simply looking at the LED. It's time consuming. The driver works fine on Windows, so it's a driver issue. It didn't affect my AP performance. It's just the LED that doesn't blink. - Steps to reproduce: 1. Install Ubuntu 18.04 on a system that has D-Link DWA-121 mini USB WiFi dongle or try it live 2. Look at the statistics light (blue LED) on the dongle. It's not blinking, whether there is download/upload or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-36-generic. ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eofla 1001 F pulseaudio Card0.Amixer.info: Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0xe000, irq 22' Mixer name : 'Realtek ALC650F' Components : 'AC97a:414c4723' Controls : 62 Simple ctrls : 36 CurrentDesktop: LXDE Date: Thu Oct 11 19:15:25 2018 InstallationDate: Installed on 2018-09-28 (13 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725) MachineType: MSI MS-6712
[Kernel-packages] [Bug 1797364] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200089/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3 DistroRelease:
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: ubuntu-power-systems Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2018-10-11 12:27 EDT--- Just to clarify the previous comment - the bug is fixed with the v2 kernel. I did multiple runs without hitting the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == IBM is requesting these commits in bionic and cosmic. These commits also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The first patch, commit 2bf1071a8d50, was backported by IBM themself. Description of bug: GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. == Fixes == 2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support") bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily invalid.") f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW transition") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with these patches and tested by IBM. IBM states the test kernel resolved the bug. -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
SRU request submitted for Bionic and Cosmic: https://lists.ubuntu.com/archives/kernel-team/2018-October/095977.html ** Also affects: linux (Ubuntu Cosmic) Importance: Critical Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Description changed: + + == SRU Justification == + IBM is requesting these commits in bionic and cosmic. These commits + also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The + first patch, commit 2bf1071a8d50, was backported by IBM themself. + + Description of bug: + GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel + driver using vmalloc) and then writing trace records from user space threads + in parallel. While the SIGBUS happened, the access virtual memory address + is in the mapped range, no overflow on access. + + The root cause is that for PTEs created by a driver at mmap time (ie, that + aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() + to make them invalid even temporarily. A concurrent access while they are + invalid will be unable to service the page fault and will cause as SIGBUS. + + + == Fixes == + 2bf1071a8d50 ("powerpc/64s: Remove POWER9 DD1 support") + bd0dbb73e013 ("powerpc/mm/books3s: Add new pte bit to mark pte temporarily invalid.") + f08d08f3db55 ("powerpc/mm/radix: Only need the Nest MMU workaround for R -> RW transition") + + + == Regression Potential == + Low. Limited to powerpc. + + == Test Case == + A test kernel was built with these patches and tested by IBM. + IBM states the test kernel resolved the bug. + + -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == IBM is requesting these commits in bionic and cosmic. These commits also rely on commit 7acf50e4efa6, which was SRU'd in bug 1792102. The first patch, commit 2bf1071a8d50, was backported by IBM themself. Description of bug: GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on
[Kernel-packages] [Bug 1797327] Re: getrandom02 in ubuntu_ltp_syscalls failed with X-kvm
I suspect that the entropy pool ran out of bits -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1797327 Title: getrandom02 in ubuntu_ltp_syscalls failed with X-kvm Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: This test will time out with X-KVM kernel on a KVM node. <<>> tag=getrandom02 stime=1539245024 cmdline="getrandom02" contacts="" analysis=exit <<>> tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s getrandom02.c:72: PASS: getrandom returned 256 getrandom02.c:72: PASS: getrandom returned 6 getrandom02.c:72: PASS: getrandom returned 256 Test timeouted, sending SIGKILL! tst_test.c:1112: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1113: BROK: Test killed! (timeout?) Summary: passed 3 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42 ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155 Uname: Linux 4.4.0-1036-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 11 08:05:56 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1797327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797364] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200085/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1797364] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200086/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1797364] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200083/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio
[Kernel-packages] [Bug 1797364] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200078/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3 DistroRelease: Ubuntu
[Kernel-packages] [Bug 1797364] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200080/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1797364] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200082/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1797364] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200088/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3 DistroRelease:
[Kernel-packages] [Bug 1797364] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200079/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1797364] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200087/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3
[Kernel-packages] [Bug 1797364] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1797364/+attachment/5200081/+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/1797364 Title: Can't suspend X1 Carbon 6th (18.04) Status in linux package in Ubuntu: Incomplete Bug description: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio /dev/snd/controlC0: maciej 2993 F pulseaudio CurrentDesktop: i3 DistroRelease:
[Kernel-packages] [Bug 1797364] Re: Can't suspend X1 Carbon 6th (18.04)
apport information ** Tags added: apport-collected ** Description changed: Laptop: Lenovo X1 Carbon 6th generation, series 20KH006KPB Release: Ubuntu 18.04.1 Kernel: 4.15.0-36-generic (but also happens with newest 4.18 mainline series) Expected behavior: I can suspend and wake up my laptop by closing ad opening the lid. What actually happens: Lenovo has distributed a BIOS update recently, version 1.31, through LVFS. It installed successfully, but I believe that since the upgrade this started happening: I can suspend the laptop by closing the lid the first time after powering it ON, S3 sleep state activates, available since BIOS 1.30 (dmesg doesn't show anything weird aside from usual trackpoint/trackpad issue with this model). But then when I try to suspend it again, I close the lid and it never suspends. dmesg gives me some concerning output this time (lots of red): [ 748.266146] e1000e: enp0s31f6 NIC Link is Down [ 748.305925] wlp2s0: deauthenticating from 74:b5:7e:14:b3:c9 by local choice (Reason: 3=DEAUTH_LEAVING) [ 748.599000] PM: suspend entry (deep) [ 748.599001] PM: Syncing filesystems ... done. [ 748.607780] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 748.609834] OOM killer disabled. [ 748.609835] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.611275] Suspending console(s) (use no_console_suspend to debug) [ 748.613850] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.613851] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.613853] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.613854] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.613858] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.613859] PM: Device 0-002c failed to suspend: error -6 [ 748.631862] PM: Some devices failed to suspend, or early wake event detected [ 748.673399] OOM killer enabled. [ 748.673401] Restarting tasks ... [ 748.676264] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.676284] psmouse: probe of serio2 failed with error -1 [ 748.676297] done. [ 748.679931] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.694583] PM: suspend exit [ 748.694682] PM: suspend entry (s2idle) [ 748.694684] PM: Syncing filesystems ... done. [ 748.700742] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 748.704303] OOM killer disabled. [ 748.704304] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 748.705954] Suspending console(s) (use no_console_suspend to debug) [ 748.711552] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6. [ 748.711556] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6. [ 748.711559] rmi4_physical rmi4-00: Failed to suspend functions: -6 [ 748.711564] rmi4_smbus 0-002c: Failed to suspend device: -6 [ 748.711576] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6 [ 748.711579] PM: Device 0-002c failed to suspend: error -6 [ 748.727561] PM: Some devices failed to suspend, or early wake event detected [ 748.769017] OOM killer enabled. [ 748.769018] Restarting tasks ... done. [ 748.772216] rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to change enabled interrupts! [ 748.772237] psmouse: probe of serio2 failed with error -1 [ 748.775189] thermal thermal_zone6: failed to read out thermal zone (-61) [ 748.788429] PM: suspend exit [ 748.804548] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.991327] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready [ 748.993686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.226795] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 749.299774] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 752.736403] wlp2s0: authenticate with 74:b5:7e:14:b3:c9 [ 752.745545] wlp2s0: send auth to 74:b5:7e:14:b3:c9 (try 1/3) [ 752.753694] wlp2s0: authenticated [ 752.753909] wlp2s0: associate with 74:b5:7e:14:b3:c9 (try 1/3) [ 752.757849] wlp2s0: RX AssocResp from 74:b5:7e:14:b3:c9 (capab=0xc11 status=0 aid=2) [ 752.761197] wlp2s0: associated [ 752.965779] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: maciej 2993 F...m pulseaudio + /dev/snd/controlC0: maciej 2993 F pulseaudio + CurrentDesktop: i3 + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e + InstallationDate: Installed on 2018-07-21 (82 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID
[Kernel-packages] [Bug 1797379] Re: linux: 4.18.0-10.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: + kernel-phase:Uploaded + kernel-phase-changed:Thursday, 11. October 2018 15:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: kernel-phase:Uploaded kernel-phase-changed:Thursday, 11. October 2018 15:33 UTC + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797379 Title: linux: 4.18.0-10.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: kernel-phase:Uploaded kernel-phase-changed:Thursday, 11. October 2018 15:33 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793221] Re: hns3: Retrieve RoCE MSI-X config from firmware
** Description changed: [Impact] MSI-X configuration is hardcoded in the hns3 driver, but the actual configuration may change across revisions. Query firmware for the MSI-X offset/numbers instead. [Test Case] - Regression testing: Confirm that, on existing hardware, the same MSIs are allocated before and after the patch. + Regression testing: Confirm that, on existing hardware, the same number of MSIs are allocated before and after the patch. grep hns /proc/interrupts | grep MSI | cut -d: -f1 > msi.old grep hns /proc/interrupts | grep MSI | cut -d: -f1 > msi.new - diff -u msi.old msi.new + wc -l msi.old msi.new [Fix] 375dd5e43212 net: hns3: Refine the MSIX allocation for PF 07acf909ee33 net: hns3: Fix MSIX allocation issue for VF [Regression Risk] Restricted to a single driver, only used on HiSilicon SoCs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793221 Title: hns3: Retrieve RoCE MSI-X config from firmware Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] MSI-X configuration is hardcoded in the hns3 driver, but the actual configuration may change across revisions. Query firmware for the MSI-X offset/numbers instead. [Test Case] Regression testing: Confirm that, on existing hardware, the same number of MSIs are allocated before and after the patch. grep hns /proc/interrupts | grep MSI | cut -d: -f1 > msi.old grep hns /proc/interrupts | grep MSI | cut -d: -f1 > msi.new wc -l msi.old msi.new [Fix] 375dd5e43212 net: hns3: Refine the MSIX allocation for PF 07acf909ee33 net: hns3: Fix MSIX allocation issue for VF [Regression Risk] Restricted to a single driver, only used on HiSilicon SoCs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp