[Kernel-packages] [Bug 1683277] Re: Mute key LED does not work on HP notebooks
A person necessarily lend a hand to make severely posts I would state. This is the very first time I frequented your website page and thus far? I surprised with the analysis you made to create this. we provide teh support related to it then you can visit the site https://www.hptechnicalsupportphonenumbersusa.com/hp-customer-care/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683277 Title: Mute key LED does not work on HP notebooks Status in linux package in Ubuntu: Confirmed Bug description: Description of problem: The F6/mute key on the keyboard of HP notebooks often has a built in LED indicator to show if the sound is muted. The LED state is never toggled. It will just retain its state, even though the audio is succesfully muted/unmuted. Tested with HP Envy 15 from 2015. HP Stream 11 from 2015 and HP Stream 11 from 2016. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Press mute key on HP laptop Actual results: Mute state in software toggles, LED in mute key does not. Expected results: Mute state in software and LED in mute key toggle. Additional info: This happens on kernel 4.8, 4.9 and 4.10. I have not tested any other versions. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stevenh1659 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 17 11:02:20 2017 HibernationDevice: RESUME=UUID=2d246125-abf7-4945-9542-45b25fb8fcb2 InstallationDate: Installed on 2016-09-13 (215 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81CC dmi.board.vendor: HP dmi.board.version: KBC Version 60.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/13/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790042] [NEW] Display Port isn't recognized on docking station
Public bug reported: After a fresh install of lubuntu 18.04 with nvidia-driver-390 the external screen which is connected via display port to the docking station of my thinkpad w530 isn't recognized anymore. For example arandr doesn't offer me any DP screen. Maybe I should say that I don't use any display manager but use startx to login directly to an xmonad session. What can I do do help to fix the problem? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Aug 31 07:08:49 2018 InstallationDate: Installed on 2018-08-23 (7 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790042 Title: Display Port isn't recognized on docking station Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After a fresh install of lubuntu 18.04 with nvidia-driver-390 the external screen which is connected via display port to the docking station of my thinkpad w530 isn't recognized anymore. For example arandr doesn't offer me any DP screen. Maybe I should say that I don't use any display manager but use startx to login directly to an xmonad session. What can I do do help to fix the problem? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Aug 31 07:08:49 2018 InstallationDate: Installed on 2018-08-23 (7 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker
** Tags added: regression-testing-passed -- 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/1788771 Title: linux-kvm: 4.4.0-1033.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow 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 Xenial: New 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: 1788766 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/1788771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788771] Re: linux-kvm: 4.4.0-1033.39 -proposed tracker
4.4.0-1033.39 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kvm_unit_tests - 18 failed on groucho ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) quotactl01 failed (bug 1790028) ubuntu_lxc - python3 API failed (bug 1764618) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1788771 Title: linux-kvm: 4.4.0-1033.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow 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 Xenial: New 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: 1788766 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/1788771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790028] Re: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp
Issue found on X-KVM kernel. 4.4.0-1033.39 - kvm -- 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/1790028 Title: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: This issue did not happen on generic Bionic kernel. tag=quotactl01 stime=1535578406 cmdline="quotactl01" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:83: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group Summary: passed 4 failed 12 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1790028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790028] Re: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp
Issue found on X-KVM kernel. ** Tags added: bionic xenial ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- 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/1790028 Title: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: This issue did not happen on generic Bionic kernel. tag=quotactl01 stime=1535578406 cmdline="quotactl01" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:83: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group Summary: passed 4 failed 12 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1790028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
Huawei hisilicon team thought it might be caused by hibmc_drm which are upstream and included in v4.10 kernel for their ARM64 server. It is right. After disable this module by: modprobe.blacklist=hibmc_drm In the grub whiling booting iso. The install screen blur was disappeared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790029] 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/1790029 Title: Static white noise and slight popping in headphones after suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever I resume from suspend, there is a very slight high pitched white noise in my headphones when I plug it in that was not present when I first boot the computer. Sounds still play fine on top of the white noise, but it persists. Various solutions online, such as messing with alsa-tools and alsamixer and powersave and hda-verb don't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claiye 2660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 22:12:51 2018 InstallationDate: Installed on 2018-08-27 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0457:10cc Silicon Integrated Systems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b3941e7c-43a6-4455-8a79-ad5bf33c75d7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.305:bd04/19/2017:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW 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/1790029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788752] Re: linux-gcp: 4.15.0-1019.20 -proposed tracker
4.15.0-1019.20 - gcp Regression test CMPL, RTB. Issue to note in gcp: ubuntu_kvm_unit_tests - failed due to no KVM support ubuntu_ltp - test disabled ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 1786729) quotactl01 failed (bug 1790028) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) inotify09 timeouted on slow machine Skipped / blacklisted: * libhugetlbfs * ubuntu_nbd_smoke_test * ubuntu_seccomp ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1788752 Title: linux-gcp: 4.15.0-1019.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: 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: New 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/1788752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790029] [NEW] Static white noise and slight popping in headphones after suspend
Public bug reported: Whenever I resume from suspend, there is a very slight high pitched white noise in my headphones when I plug it in that was not present when I first boot the computer. Sounds still play fine on top of the white noise, but it persists. Various solutions online, such as messing with alsa-tools and alsamixer and powersave and hda-verb don't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claiye 2660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 22:12:51 2018 InstallationDate: Installed on 2018-08-27 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0457:10cc Silicon Integrated Systems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b3941e7c-43a6-4455-8a79-ad5bf33c75d7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.305:bd04/19/2017:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790029 Title: Static white noise and slight popping in headphones after suspend Status in linux package in Ubuntu: New Bug description: Whenever I resume from suspend, there is a very slight high pitched white noise in my headphones when I plug it in that was not present when I first boot the computer. Sounds still play fine on top of the white noise, but it persists. Various solutions online, such as messing with alsa-tools and alsamixer and powersave and hda-verb don't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claiye 2660 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 22:12:51 2018 InstallationDate: Installed on 2018-08-27 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0457:10cc Silicon Integrated Systems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b3941e7c-43a6-4455-8a79-ad5bf33c75d7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW
[Kernel-packages] [Bug 1790028] [NEW] quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp
Public bug reported: This issue did not happen on generic Bionic kernel. tag=quotactl01 stime=1535578406 cmdline="quotactl01" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:83: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group Summary: passed 4 failed 12 skipped 0 warnings 0 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- 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/1790028 Title: quotactl01 in ubuntu_ltp_syscalls test failed on B-gcp Status in linux-gcp package in Ubuntu: New Bug description: This issue did not happen on generic Bionic kernel. tag=quotactl01 stime=1535578406 cmdline="quotactl01" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:83: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s quotactl01.c:195: FAIL: quotactl failed to turn on quota for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get disk quota limit for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for user: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for user: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for user quotactl01.c:206: PASS: quotactl succeeded to turn off quota for user quotactl01.c:195: FAIL: quotactl failed to turn on quota for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set disk quota limit for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to set information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get information about quotafile for group: ESRCH quotactl01.c:195: FAIL: quotactl failed to get quota format for group: ESRCH quotactl01.c:206: PASS: quotactl succeeded to update quota usages for group quotactl01.c:206: PASS: quotactl succeeded to turn off quota for group Summary: passed 4 failed 12 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1790028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788730] Re: TP-LINK TG-3468 network card not recognized correctly
Xenial will be fixed, but that will take some time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788730 Title: TP-LINK TG-3468 network card not recognized correctly Status in linux package in Ubuntu: In Progress Bug description: A few days ago purchased a couple of TP-LINK TG-3468 network cards (reviewed by Phoronix here: https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both brand new, not reused. After installed them to a pc, to my surprise, one of them was correctly identified and the other was incorrectly identified as "NCube Device 8168 (rev 06)". After DuckDuckGoing for a while I found this kernel bud report for FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e -network-card.57734/ IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I wanted to report this so it can be fixed, please let me know wich logs/data should I provide. When ran lspci -nv this is shown for the correct nic: 03:00.0 0200: 10ec:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 27 I/O ports at e800 [size=256] Memory at febff000 (64-bit, non-prefetchable) [size=4K] Memory at fdffc000 (64-bit, prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 Kernel modules: r8169 And this for the incorrect one: 01:00.0 0200: 10ff:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c800 [size=256] Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K] Memory at fdefc000 (64-bit, prefetchable) [size=16K] Capabilities: 1) lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 2) In regard to the package I think this is related to the kernel itself? 3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the r8169 driver should be used. 4) The network card was erroneously detected as a different one and the driver was not loaded by the kernel. Best regards. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-133-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791 InstallationDate: Installed on 2017-12-06 (260 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 RelatedPackageVersions: linux-restricted-modules-4.4.0-133-generic N/A linux-backports-modules-4.4.0-133-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-133-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-CM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Applied the patch from -proposed: root@Ubuntu1804:~# echo "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted main multiverse universe" | tee -a /etc/apt/sources.list root@Ubuntu1804:~# apt-get update root@Ubuntu1804:~# apt-get dist-upgrade root@Ubuntu1804:~# shutdown -r 0 Verified that the -proposed contains fix: root@Ubuntu1804:~# objdump -d /lib/modules/$(uname -r)/kernel/drivers/nvme/host/nvme.ko | grep -A 50 __nvme_submit_cmd\>: | grep fence adf:0f ae f8sfence ae6:0f ae f0mfence (second mfence is the one added by patch) Verified that the patch solves the issue: ./orion -run advanced -num_large 0 -size_small 8 -type rand -simulate concat -write 40 -duration 120 -matrix row -testname gcp_test (no hang after 36 hours) I assume that the same patch will be added to Xenial and Cosmic. ** 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/1788222 Title: Bugfix for handling of shadow doorbell buffer Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress 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 1789589] Re: USB-SATA resets when UAS is used
Dear all, Tested with upstream kernel, same result. Kernel version: Linux version 4.19.0-041900rc1-generic (kernel@kathleen) (gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1)) kernel-bug-exists-upstream ** 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/1789589 Title: USB-SATA resets when UAS is used Status in linux package in Ubuntu: Confirmed Bug description: Dear developers, I have a Icybox 4 HDD enclosure with a JMicrom JMS567 SATA to USB converter. When the device is under load and more than 1 hardrive is acessed, the USB enclosure frequently restarts. This leaves often a corrup filesystem. I tried to switch off UAS by creating a file in /etc/modprobe.d/blacklist_uas.conf with the following content: options usb-storage quirks=152d:0567:u This disables UAS, and I did not exerinecs restarts of the box. But of course thios laves only USB speeds on the USB3 connector, which is quite slow. I think this suggest this is a kernel bug and not a hardware issues. I aasume the problem is in the linux-image-4.15.0-33-generic package. Similar has been reported: https://www.spinics.net/lists/linux-usb/msg157550.html Any help would be greatly appreciated. Best regards Michael lsusb -vvv -s 003:004 Bus 003 Device 004: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp. idProduct 0x0567 JMS567 SATA 6Gb/s bridge bcdDevice2.05 iManufacturer 10 iProduct 11 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 res3stockm@brix:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
It's worth saying that the ASPM patch + 1500 kernel parameter worked for me for over a month without giving me one single error. After update to 18.04 now I see the error every 2 or 3 days. Actually, in the middle of the update process to 18.04 it gave the error right on the initramfs update, which is where it always gives the error. This is sad, it was working perfectly except inside the VMs but it was very stable :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop:
[Kernel-packages] [Bug 1790006] [NEW] Update firmware udebs for 4.18
Public bug reported: Update the linux firmware udeb file lists in cosmic for the 4.18 kernel in cosmic-proposed. ** Affects: linux-firmware (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Tags: block-proposed -- 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/1790006 Title: Update firmware udebs for 4.18 Status in linux-firmware package in Ubuntu: In Progress Bug description: Update the linux firmware udeb file lists in cosmic for the 4.18 kernel in cosmic-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1790006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789987] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: bionic ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: kernel-sru-derivative-of-1789984 ** Summary changed: - linux-aws: -proposed tracker + Ignore this bug -- 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/1789987 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789989] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: bionic ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: kernel-sru-derivative-of-1789984 ** Summary changed: - linux-gcp: -proposed tracker + Ignore this bug -- 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/1789989 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789988] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: bionic ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: kernel-sru-derivative-of-1789984 ** Summary changed: - linux-azure: -proposed tracker + Ignore this bug -- 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/1789988 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789986] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: bionic ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: kernel-sru-derivative-of-1789984 ** Summary changed: - linux-oem: -proposed tracker + Ignore this bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1789986 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-oem package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789990] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: bionic ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: kernel-sru-derivative-of-1789984 ** Summary changed: - linux-kvm: -proposed tracker + Ignore this bug -- 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/1789990 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789992] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-backport-of-1789984 ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: trusty ** Summary changed: - linux-azure: -proposed tracker + Ignore this bug -- 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/1789992 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789993] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-backport-of-1789984 ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: xenial ** Summary changed: - linux-azure: -proposed tracker + Ignore this bug -- 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/1789993 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789996] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-backport-of-1789984 ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: xenial ** Summary changed: - linux-gcp: -proposed tracker + Ignore this bug -- 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/1789996 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid 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 -- kernel-stable-master-bug: 1789984 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789996/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789984] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Tags removed: bionic ** Tags removed: kernel-release-tracking-bug ** Tags removed: kernel-release-tracking-bug-live ** Tags removed: kernel-sru-cycle-2018.08.20-2 ** Tags removed: kernel-sru-master-kernel ** Summary changed: - linux: -proposed tracker + Ignore 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/1789984 Title: Ignore this bug Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid 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 1789992 (linux-azure), bug 1789993 (linux-azure), bug 1789994 (linux-azure-edge), bug 1789996 (linux-gcp), bug 1789997 (linux-hwe), bug 178 (linux-hwe-edge) derivatives: bug 1789985 (linux-raspi2), bug 1789986 (linux-oem), bug 1789987 (linux-aws), bug 1789988 (linux-azure), bug 1789989 (linux-gcp), bug 1789990 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713448] Re: Adobe Reader doesn't print on OKI C911
Hello Udippel, Thank you for submitting this bug and reporting a problem with cups. You made this bug report some time ago and Ubuntu has been updated since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you let us know? Thank you again for helping make Ubuntu better. G [Ubuntu Bug Squad volunteer triager] ** Changed in: cups (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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789984] Re: linux: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + backports: bug 1789992 (linux-azure), bug 1789993 (linux-azure), bug 1789994 (linux-azure-edge), bug 1789996 (linux-gcp), bug 1789997 (linux-hwe), bug 178 (linux-hwe-edge) + derivatives: bug 1789985 (linux-raspi2), bug 1789986 (linux-oem), bug 1789987 (linux-aws), bug 1789988 (linux-azure), bug 1789989 (linux-gcp), bug 1789990 (linux-kvm) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789984 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable 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 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 1789992 (linux-azure), bug 1789993 (linux-azure), bug 1789994 (linux-azure-edge), bug 1789996 (linux-gcp), bug 1789997 (linux-hwe), bug 178 (linux-hwe-edge) derivatives: bug 1789985 (linux-raspi2), bug 1789986 (linux-oem), bug 1789987 (linux-aws), bug 1789988 (linux-azure), bug 1789989 (linux-gcp), bug 1789990 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789996] [NEW] linux-gcp: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1789984 kernel-sru-cycle-2018.08.20-2 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing
[Kernel-packages] [Bug 1789988] [NEW] linux-azure: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.08.20-2 kernel-sru-derivative-of-1789984 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects:
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1804 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789990] [NEW] linux-kvm: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.08.20-2 kernel-sru-derivative-of-1789984 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) =>
[Kernel-packages] [Bug 1789989] [NEW] linux-gcp: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.08.20-2 kernel-sru-derivative-of-1789984 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing
[Kernel-packages] [Bug 1789992] [NEW] linux-azure: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1789984 kernel-sru-cycle-2018.08.20-2 trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: trusty ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1789993] [NEW] linux-azure: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1789984 kernel-sru-cycle-2018.08.20-2 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects:
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
--- Comment From jhop...@us.ibm.com 2018-08-30 10:29 EDT--- Thanks, I've asked for some testing assistance from our KVM team but will note here some of the details from the original report of this problem.. repro steps are just a simple local host migration. ..they later noted that increasing the speed was a workaround: (qemu) migrate_set_speed 1G so you would want to test w/ default speed to confirm the issue is resolved (qemu) migrate -d tcp:localhost: using " cosmic qemu version 1:2.12+dfsg-3 " from Bug 169712 / LP 1781526 (which enables qemu to use 2MB THP backing for powerpc), plus the test kernel build from this bug. Note without the kernel fix discussed in this bug, a migration problem might still happen even without that qemu THP patch if you got lucky enough to have a 2MB alignment by chance. ** Tags added: architecture-ppc64le bugnameltc-170805 severity-critical targetmilestone-inin--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789986] [NEW] linux-oem: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.08.20-2 kernel-sru-derivative-of-1789984 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) **
[Kernel-packages] [Bug 1789984] [NEW] linux: -proposed tracker
Public bug reported: 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 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.08.20-2 kernel-sru-master-kernel ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical
[Kernel-packages] [Bug 1789987] [NEW] linux-aws: -proposed tracker
Public bug reported: 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 -- kernel-stable-master-bug: 1789984 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.08.20-2 kernel-sru-derivative-of-1789984 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true -- 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/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New 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: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New 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: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789459] Re: linux: 4.18.0-7.8 -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 ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug is for tracking the 4.18.0-7.8 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 + + kernel-phase-changed:Thursday, 30. August 2018 19:34 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.18.0-7.8 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 kernel-phase-changed:Thursday, 30. August 2018 19:34 UTC kernel-phase:Uploaded + + -- 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/1789459 Title: linux: 4.18.0-7.8 -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: Fix Committed 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 4.18.0-7.8 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 kernel-phase-changed:Thursday, 30. August 2018 19:34 UTC kernel-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719795]
Can you also attach contents of /sys/bus/i2c/devices/*? It would be nice to know all devices connected to I2C buses. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789756] Re: Swap not being used, RAM not being released, CPU use at 100%
No. Closing VirtualBox means that the memory usage should be released. If the memory is still tied up after the program has closed with no processes running, then the kernel is at fault as it is the one controlling memory. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789756 Title: Swap not being used, RAM not being released, CPU use at 100% Status in linux package in Ubuntu: Confirmed Bug description: Memory usage continues to climb to 100%, even as applications are shut down. Swap file is not being used. CPU usage climbs to %100 even as applications are shut down. After reboot, system will operate normally for a number of hours, until a virtual machine (Virtual Box) is run. At this point memory and CPU usage will climb until %100. Exiting programs and closing the VM does not resolve the issue. More information in this thread, started by me: https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cortimi1688 F pulseaudio /dev/snd/controlC1: cortimi1688 F pulseaudio /dev/snd/controlC0: cortimi1688 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Aug 29 17:39:45 2018 InstallationDate: Installed on 2018-08-23 (6 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: MSI MS-7817 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 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/1789756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742106] Re: NMI watchdog: BUG: soft lockup - CPU#9 stuck for 22s! [linux:23890]
I'm getting what appears to be the same error after gaming for a couple hours. About 8 of 16 cores softlock. My Dmesg mentions my amdgpu as well. Ubuntu 18.04 4.15.0-33-generic #36-Ubuntu SMP Someone with a similar error found it was their power supply. I'm going to try a mainline kernel and see if it helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742106 Title: NMI watchdog: BUG: soft lockup - CPU#9 stuck for 22s! [linux:23890] Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04.1 LTS with the 4.4.0-104-generic kernel, and running a user-mode-linux heavy workload. Every now and then, the system locks up and is subsequently reset by the hardware watchdog. I have verified that the lockups go away if UML is not enabled. I have tried a variety of UML guest kernels, including 3.13.0-1um-0ubuntu1 (from Ubuntu repos), 3.16-1um-0.1+b2 (Debian) and 4.9-1um-1+b3 (Debian) and am seeing lockups across all of these. The lockups go away, however, when a 3.13 host kernel is used. I am able to generate a crash and collect crash dumps during lockups by sending an NMI (kernel.unknown_nmi_panic = 1) Below are dmesg logs collected on crash during one such lockup. I can attach the crash dump as well if this will be helpful. [14532.482373] CPU: 9 PID: 23890 Comm: linux Not tainted 4.4.0-104-generic #127~14.04.1-Ubuntu [14532.482375] Hardware name: Supermicro PIO-228TR-HT-NODE/X10DRT-H, BIOS 2.0 03/30/2016 [14532.482377] task: 880efc143800 ti: 880168ef8000 task.ti: 880168ef8000 [14532.482379] RIP: 0010:[] [] native_queued_spin_lock_slowpath+0x117/0x170 [14532.482385] RSP: 0018:880168efbeb0 EFLAGS: 0202 [14532.482387] RAX: RBX: 81e0b080 RCX: 880f46e57900 [14532.482388] RDX: 00040101 RSI: 0028 RDI: 81e0b084 [14532.482390] RBP: 880168efbeb0 R08: 0101 R09: 0001 [14532.482391] R10: 60afa4e0 R11: 0206 R12: 81e0b084 [14532.482393] R13: 8801e63d6200 R14: R15: 60afa4e0 [14532.482395] FS: 7f8c0e8cf740() GS:880f46e4() knlGS: [14532.482396] CS: 0010 DS: ES: CR0: 80050033 [14532.482398] CR2: 40741a80 CR3: 000197e57000 CR4: 001406e0 [14532.482400] Stack: [14532.482401] 880168efbec0 81184364 880168efbee0 810c7f96 [14532.482404] 8801e63d6200 880168efbef0 8180f293 [14532.482406] 880168efbf10 8108842e 000d 9fb24ac0 [14532.482409] Call Trace: [14532.482414] [] queued_spin_lock_slowpath+0xb/0xf [14532.482416] [] queued_read_lock_slowpath+0x76/0x80 [14532.482420] [] _raw_read_lock+0x23/0x30 [14532.482424] [] ptrace_check_attach+0x1e/0x140 [14532.482426] [] SyS_ptrace+0x8e/0x110 [14532.482429] [] entry_SYSCALL_64_fastpath+0x16/0x75 [14532.482431] Code: 30 48 98 48 81 c2 00 79 01 00 48 03 14 c5 c0 a0 f3 81 48 89 0a 8b 41 08 85 c0 75 0d f3 90 8b 41 08 85 c0 74 f7 eb 02 f3 90 8b 17 <66> 85 d2 75 f7 39 f2 66 90 75 0f 89 d0 be 01 00 00 00 f0 0f b1 [14532.482459] Sending NMI to other CPUs: [14532.484745] NMI backtrace for cpu 0 [14532.484747] CPU: 0 PID: 11657 Comm: cockroach Not tainted 4.4.0-104-generic #127~14.04.1-Ubuntu [14532.484748] Hardware name: Supermicro PIO-228TR-HT-NODE/X10DRT-H, BIOS 2.0 03/30/2016 [14532.484749] task: 880efc175400 ti: 880dbfbf4000 task.ti: 880dbfbf4000 [14532.484751] RIP: 0010:[] [] native_queued_spin_lock_slowpath+0x10a/0x170 [14532.484752] RSP: 0018:880dbfbf7d58 EFLAGS: 0046 [14532.484753] RAX: RBX: 81e0b080 RCX: 880f46c17900 [14532.484754] RDX: 880f46d17900 RSI: 0004 RDI: 81e0b084 [14532.484756] RBP: 880dbfbf7d58 R08: 0101 R09: [14532.484757] R10: R11: 0246 R12: 81e0b084 [14532.484758] R13: 0007 R14: 00020002 R15: 880ec8f27f80 [14532.484759] FS: 7fb8aefff700() GS:880f46c0() knlGS: [14532.484761] CS: 0010 DS: ES: CR0: 80050033 [14532.484762] CR2: 7f9e82520a08 CR3: 000de63d2000 CR4: 001406f0 [14532.484763] Stack: [14532.484764] 880dbfbf7d68 81184364 880dbfbf7d88 810c7f96 [14532.484765] 880ef9c22278 0246 880dbfbf7d98 8180f293 [14532.484767] 880dbfbf7de0 81214c82 000181ec7c40 [14532.484768] Call Trace: [14532.484769] [] queued_spin_lock_slowpath+0xb/0xf [14532.484770] [] queued_read_lock_slowpath+0x76/0x80 [14532.484771] [] _raw_read_lock+0x23/0x30
[Kernel-packages] [Bug 1789756] Re: Swap not being used, RAM not being released, CPU use at 100%
« system will operate normally for a number of hours, until a virtual machine (Virtual Box) is run » then maybe some settings to do in VirtualBox ? Or a bug there ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789756 Title: Swap not being used, RAM not being released, CPU use at 100% Status in linux package in Ubuntu: Confirmed Bug description: Memory usage continues to climb to 100%, even as applications are shut down. Swap file is not being used. CPU usage climbs to %100 even as applications are shut down. After reboot, system will operate normally for a number of hours, until a virtual machine (Virtual Box) is run. At this point memory and CPU usage will climb until %100. Exiting programs and closing the VM does not resolve the issue. More information in this thread, started by me: https://discourse.ubuntubudgie.org/t/high-ram-use-no-swap-use/940/9 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cortimi1688 F pulseaudio /dev/snd/controlC1: cortimi1688 F pulseaudio /dev/snd/controlC0: cortimi1688 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Aug 29 17:39:45 2018 InstallationDate: Installed on 2018-08-23 (6 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: MSI MS-7817 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=10f46365-0845-48bb-a427-fe155f6085c0 ro quiet splash 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 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/1789756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
Before starting the bisect, just one last kernel to confirm: v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ If v4.14 Final is GOOD, I'll start a bisect between v4.14 and v4.15-rc1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
The last TB firmware was released 2018-04, and it is up to date (also according to fwupdmgr). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Thank for the info! This is something Dell should know. Other than BIOS, is the Thunderbolt firmware up-to-date? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I had to downgrade the BIOS back to 1.10.1 (fwupdmgr installed 1.11) as under the new firmware suspend to RAM caused the system to completely power off (i.e. boot from scratch when powering on). I'll try to update again when the new update is released on Dell's website (the current version on the website is 1.10.1, so I can't even report an bug about the firmware update). But I doubt this issue will be resolved by a firmware update - as mentioned in my previous comment, this bug has survived numerous firmware update: the original bug report was using BIOS 1.7 and it still happens in 1.10.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1787742] Re: TP-Link Archer T1U 5GHz WiFi adapter not compatible
@jsalisbury, okay, I just tried it on the latest RC1 build as of 08/30/2018, and the T1U Archer wifi chip still doesn't activate. Please see the hardinfo report attached. ** Attachment added: "hardinfo report - 08/30/2018" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787742/+attachment/5182752/+files/hardinfo_report.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787742 Title: TP-Link Archer T1U 5GHz WiFi adapter not compatible Status in linux package in Ubuntu: Incomplete Bug description: My TP-Link Archer T1U 5GHz USB WiFi adapter/dongle is not being recognized by the system settings and WiFi setup wizards, likely due to a compatibility issue with the Linux kernel. The device is functional in Windows and recognized by my motherboard, but unfortunately it is a mere waste of a USB port with Ubuntu and other Linux distributions. - Terminal output when running 'lsusb' cmd: jeb@A880G:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 03f0:d407 Hewlett-Packard Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 008: ID 0461:4d75 Primax Electronics, Ltd Rocketfish RF-FLBTAD Bluetooth Adapter Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass) Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass) Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 009: ID 2357:0105 Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb1608 F pulseaudio /dev/snd/controlC1: jeb1608 F pulseaudio /dev/snd/controlC0: jeb1608 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 12:20:18 2018 InstallationDate: Installed on 2018-08-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789951] Re: package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode
** Tags removed: need-duplicate-check -- 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/1789951 Title: package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 Status in linux-firmware package in Ubuntu: New Bug description: Could not install https://github.com/q3aql/amdgpu-firmware- update/releases/download/v3.0/linux-firmware_20180828-1_all.deb ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 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.2 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 30 22:20:28 2018 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_20180828-1_all.deb ... Unpacking linux-firmware (20180828-1) over (1.173.1) ... dpkg: error processing archive /home/sohrab/Downloads/linux-firmware_20180828-1_all.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 DuplicateSignature: package:linux-firmware:1.173.1 Unpacking linux-firmware (20180828-1) over (1.173.1) ... dpkg: error processing archive /home/sohrab/Downloads/linux-firmware_20180828-1_all.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 ErrorMessage: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 InstallationDate: Installed on 2018-08-28 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1789951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789951] [NEW] package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcod
Public bug reported: Could not install https://github.com/q3aql/amdgpu-firmware- update/releases/download/v3.0/linux-firmware_20180828-1_all.deb ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 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.2 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 30 22:20:28 2018 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_20180828-1_all.deb ... Unpacking linux-firmware (20180828-1) over (1.173.1) ... dpkg: error processing archive /home/sohrab/Downloads/linux-firmware_20180828-1_all.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 DuplicateSignature: package:linux-firmware:1.173.1 Unpacking linux-firmware (20180828-1) over (1.173.1) ... dpkg: error processing archive /home/sohrab/Downloads/linux-firmware_20180828-1_all.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 ErrorMessage: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 InstallationDate: Installed on 2018-08-28 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- 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/1789951 Title: package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 Status in linux-firmware package in Ubuntu: New Bug description: Could not install https://github.com/q3aql/amdgpu-firmware- update/releases/download/v3.0/linux-firmware_20180828-1_all.deb ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 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.2 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 30 22:20:28 2018 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_20180828-1_all.deb ... Unpacking linux-firmware (20180828-1) over (1.173.1) ... dpkg: error processing archive /home/sohrab/Downloads/linux-firmware_20180828-1_all.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 DuplicateSignature: package:linux-firmware:1.173.1 Unpacking linux-firmware (20180828-1) over (1.173.1) ... dpkg: error processing archive /home/sohrab/Downloads/linux-firmware_20180828-1_all.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 ErrorMessage: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 InstallationDate: Installed on 2018-08-28 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: trying to overwrite '/lib/firmware/amd-ucode/microcode_amd.bin', which is also in package amd64-microcode 3.20180524.1~ubuntu0.18.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1789951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783152] Re: Enable basic support for Solarflare 8000 series NIC
Sponsored for Trusty. The 4.4.0-134 is indeed containing the required commits mentioned above : $ git log ... 67f5d9c sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 4a76ed3 sfc: make TSO version a per-queue parameter $ git describe --contains 67f5d9c Ubuntu-lts-4.4.0-134.160_14.04.1~320 $ git describe --contains 4a76ed3 Ubuntu-lts-4.4.0-134.160_14.04.1~321 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Status in debian-installer source package in Trusty: In Progress Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-18.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784331] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-18.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784331 Title: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. Is planned as part of kernel 4.19. Therefore a backport to kernel 4.18 will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783086] Re: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part
snapd will need that too, though it doesn't even support kexec yet, which breaks systemctl kexec already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1783086 Title: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part Status in Ubuntu on IBM z Systems: Fix Committed Status in kexec-tools package in Ubuntu: Fix Committed Bug description: FeatureFreeze Exception (FFE): == Reason, rationale and benefits: --- The feature is based on the combination of two tickets: - 1783088 this ticket for the kernel part was just created for completeness reasons this part of the functionality automatically came with kernel 4.17 hence this LP ticket is 'Fix Released' - 1783086 this is the 'user space' part of the functionality that should be addressed by the FFE There was a little confusion if this belongs to the FeatureFreeze or KernelFreeze. Since it's a package maintained by the kernel team the misconception came up that it is not affected by the Feature, but by the Kernel Freeze, hence it was not processed in time and information was missing. Without this patch the (new) "--kexec-file-syscall" option for s390x cannot be used with cosmic. And the customer/partner needs to wait for the next d* release (means for several month). This FFE now asks if the single commit (below) can be added to the kexec-tools (Ubuntu) of cosmic: Description: commit d4a948c268272cf37c71be820fb02bf40e56292b Author: Philipp Rudo Date: Wed May 16 14:27:18 2018 +0200 kexec/s390: Add support for kexec_file_load Since kernel 4.17-rc2 s390 supports the kexec_file_load system call. Add the new system call to kexec-tools and provide the -s (--kexec-file-syscall) option for s390 to support this new feature. Impact / Risk: -- Since the function / option is new and for s390(x) the risk is pretty low. There are no APIs expected to break or existing functions that are expected to fail while introducing this. Package dependencies will not change, nor the install/upgrade behaviour after this got added. Testing of the code, test builds and verification was already done by IBM. (see comment # 4) _ Provide a capability to load signed kernels. I.e. to boot signed kernels - from a Linux based boot loader or initial boot image - as required for secure/trusted boot mechanisms - for kdump kernels Function consist of 2 contributions - kernel 4.17 (available) - kexec-tools (currently not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1783086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700672] Re: bumblebee / primusrun does not work with NVIDIA 375.66
Another issue as well in Ubuntu 18.04 and NVIDIA 390.00 They managed a way to solve it. https://askubuntu.com/questions/1029169/bumblebee-doesnt-work-on- ubuntu-18-04/1042950#1042950 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1700672 Title: bumblebee / primusrun does not work with NVIDIA 375.66 Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-375 package in Ubuntu: New Bug description: In Ubuntu 16.04.2, after upgrading nvidia-375 to 375.66-0ubuntu0.16.04.1, bumblebee stopped working. Attempting to launch anything with primusrun results in errors. Upstream bug report seems to be pointing at a flaw in /usr/lib/nvidia-375-prime/ld.so.conf , that's why I'm assigning to nvidia-375 and not bumblebee: https://github.com/Bumblebee-Project/Bumblebee/issues/879 From syslog: Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 20.414721] [WARN]Unable to disable discrete card.[ 2606.504423] [ERROR][XORG] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504433] [WARN][XORG] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere. Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504435] [ERROR][XORG] (EE) Failed to load /usr/lib/nvidia-375/xorg/libglx.so: libnvidia-tls.so.375.66: cannot open shared object file: No such file or directory Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504438] [ERROR][XORG] (EE) Failed to load module "glx" (loader failed, 7) Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504441] [WARN][XORG] (WW) Warning, couldn't open module mouse Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504443] [ERROR][XORG] (EE) Failed to load module "mouse" (module does not exist, 0) Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504448] [ERROR][XORG] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504451] [ERROR][XORG] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504453] [ERROR][XORG] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504455] [ERROR][XORG] (EE) NVIDIA(0): you continue to encounter problems, Please try Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504458] [ERROR][XORG] (EE) NVIDIA(0): reinstalling the NVIDIA driver. Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504460] [WARN][XORG] (WW) NVIDIA(0): Unable to get display device for DPI computation. Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504464] [WARN][XORG] (WW) Warning, couldn't open module mouse Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504465] [ERROR][XORG] (EE) Failed to load module "mouse" (module does not exist, 0) Jun 27 01:08:54 ubuntu1604 bumblebeed[892]: [ 2606.504470] [ERROR][XORG] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1700672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783152] Re: Enable basic support for Solarflare 8000 series NIC
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Status in debian-installer source package in Trusty: In Progress Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789638] Re: azure 4.15 kernel: reading sysfs file causing oops
This has been submitted to 4.19 and stable:
For unsupported device types, the vmbus channel ringbuffer is never
initialized, and therefore reading the sysfs files will return garbage
or cause a kernel OOPS.
Fixes: c2e5df616e1a ("vmbus: add per-channel sysfs info")
** Patch added:
"0001-hv_vmbus-dont-return-values-for-uninitialized-channels.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789638/+attachment/5182726/+files/0001-hv_vmbus-dont-return-values-for-uninitialized-channels.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789638
Title:
azure 4.15 kernel: reading sysfs file causing oops
Status in linux package in Ubuntu:
Incomplete
Bug description:
Kernel: 4.15.0-1021-azure, in Xenial VM on Azure.
How to reproduce:
git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make
./stress-ng --sysfs 0 -t 120
One gets the following:
[ 22.451885] BUG: unable to handle kernel NULL pointer dereference at
0004
[ 22.455286] IP: read_avail_show+0x1c/0x40
[ 22.455286] PGD 80042d59e067 P4D 80042d59e067 PUD 42eb8c067 PMD 0
[ 22.455286] Oops: [#1] SMP PTI
[ 22.455286] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner
xt_conntrack nf_conntrack iptable_security ip_tables x_tables serio_raw joydev
hv_balloon ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear
hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel
aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb hid_hyperv pata_acpi
cfbfillrect hyperv_keyboard cfbimgblt hid cfbcopyarea hv_netvsc hv_utils
[ 22.455286] CPU: 1 PID: 1670 Comm: cat Not tainted 4.15.0-1021-azure
#21~16.04.1-Ubuntu
[ 22.455286] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 22.455286] RIP: 0010:read_avail_show+0x1c/0x40
[ 22.455286] RSP: 0018:afa4c4eafdb0 EFLAGS: 00010286
[ 22.455286] RAX: RBX: 9db36c93e880 RCX:
9db36f136908
[ 22.860062] RDX: RSI: 9db364548000 RDI:
9db364548000
[ 22.888042] RBP: afa4c4eafdb0 R08: 9db364548000 R09:
9db36c049840
[ 22.920041] R10: 9db364548000 R11: R12:
92ae9440
[ 22.948058] R13: 9db36c22d200 R14: 0001 R15:
9db36c93e880
[ 22.972043] FS: 7f67eeec6700() GS:9db37fd0()
knlGS:
[ 23.004046] CS: 0010 DS: ES: CR0: 80050033
[ 23.024016] CR2: 0004 CR3: 00042c37a003 CR4:
001606e0
[ 23.048014] Call Trace:
[ 23.060019] vmbus_chan_attr_show+0x21/0x30
[ 23.076018] sysfs_kf_seq_show+0xa2/0x130
[ 23.088030] kernfs_seq_show+0x27/0x30
[ 23.100020] seq_read+0xb7/0x480
[ 23.112014] kernfs_fop_read+0x111/0x190
[ 23.128017] ? security_file_permission+0xa1/0xc0
[ 23.144013] __vfs_read+0x1b/0x40
[ 23.156019] vfs_read+0x93/0x130
[ 23.168013] SyS_read+0x55/0xc0
[ 23.180021] do_syscall_64+0x73/0x130
[ 23.192014] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 23.212022] RIP: 0033:0x7f67ee9d8260
[ 23.224016] RSP: 002b:7fffdc193ff8 EFLAGS: 0246 ORIG_RAX:
[ 23.252022] RAX: ffda RBX: 0002 RCX:
7f67ee9d8260
[ 23.276019] RDX: 0002 RSI: 7f67eed0c000 RDI:
0003
[ 23.300020] RBP: 0002 R08: R09:
[ 23.328025] R10: 037b R11: 0246 R12:
7f67eed0c000
[ 23.352036] R13: 0003 R14: R15:
0002
[ 23.376678] Code: fb 3a 17 00 48 98 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00
00 55 48 8b 87 38 01 00 00 49 89 f0 8b 97 48 01 00 00 4c 89 c7 48 89 e5 <8b> 48
04 8b 00 29 ca 89 c6 29 ce 01 c2 39 c1 0f 46 d6 48 c7 c6
[ 23.444022] RIP: read_avail_show+0x1c/0x40 RSP: afa4c4eafdb0
[ 23.468021] CR2: 0004
[ 23.481135] ---[ end trace 348a4b7d5a6747d1 ]---
Cornered this down to just reading:
cat
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/99221fa0
-24ad-11e2-be98-001aa01bbf6e/channels/4/read_avail
There are various /sysfs VMBUS files that trigger this, see a fix on
comment #5 below that addresses all the ones I could find.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789638/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788730] Re: TP-LINK TG-3468 network card not recognized correctly
Is it possible to implement a fix available for xenial ubuntu official repositories? These kernels (4.15, 4.18 and 4.19) were tested just in bionic, xenial crashed and dependencies were not satisfied (I can provide further details if needed). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788730 Title: TP-LINK TG-3468 network card not recognized correctly Status in linux package in Ubuntu: In Progress Bug description: A few days ago purchased a couple of TP-LINK TG-3468 network cards (reviewed by Phoronix here: https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both brand new, not reused. After installed them to a pc, to my surprise, one of them was correctly identified and the other was incorrectly identified as "NCube Device 8168 (rev 06)". After DuckDuckGoing for a while I found this kernel bud report for FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e -network-card.57734/ IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I wanted to report this so it can be fixed, please let me know wich logs/data should I provide. When ran lspci -nv this is shown for the correct nic: 03:00.0 0200: 10ec:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 27 I/O ports at e800 [size=256] Memory at febff000 (64-bit, non-prefetchable) [size=4K] Memory at fdffc000 (64-bit, prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 Kernel modules: r8169 And this for the incorrect one: 01:00.0 0200: 10ff:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c800 [size=256] Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K] Memory at fdefc000 (64-bit, prefetchable) [size=16K] Capabilities: 1) lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 2) In regard to the package I think this is related to the kernel itself? 3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the r8169 driver should be used. 4) The network card was erroneously detected as a different one and the driver was not loaded by the kernel. Best regards. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-133-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791 InstallationDate: Installed on 2017-12-06 (260 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 RelatedPackageVersions: linux-restricted-modules-4.4.0-133-generic N/A linux-backports-modules-4.4.0-133-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-133-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-CM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788730/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1789946] 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/1789946 Title: DHCP server and client not working since kernel 4.15.0-32 Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu server 18.04 on HP Proliant BL460c Gen8 server blades. I set up DHCP server for PXE boot. It was working, but since kernel update with version 4.15.0-32, PXE boot no longer works. DHCP server logs show "5 bad udp checksums in 5 packets" in a row. DHCP client is also not working on the machine due to similar errors. I switched back to kernel version 4.15-0-29 and it works again. I suspect the newer kernel might have introduced a bug about the network adapter driver. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 08:56 seq crw-rw 1 root audio 116, 33 Aug 30 08:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 30 09:08:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant BL460c Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0a9aa0b0-9a67-11e8-a1dc-fc15b41d0ee0 ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: HP dmi.bios.version: I31 dmi.chassis.type: 28 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrI31:bd12/20/2013:svnHP:pnProLiantBL460cGen8:pvr:cvnHP:ct28:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant BL460c Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783086] Re: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part
systemd-shutdown does use kexec tool, but it calls it with 'kexec --load' & 'kexec -e', it does not use 'kexec -s'. Then again changing systemd shutdown, might be pre-mature, as we really don't have things to use with 'kexec -s' yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1783086 Title: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part Status in Ubuntu on IBM z Systems: Fix Committed Status in kexec-tools package in Ubuntu: Fix Committed Bug description: FeatureFreeze Exception (FFE): == Reason, rationale and benefits: --- The feature is based on the combination of two tickets: - 1783088 this ticket for the kernel part was just created for completeness reasons this part of the functionality automatically came with kernel 4.17 hence this LP ticket is 'Fix Released' - 1783086 this is the 'user space' part of the functionality that should be addressed by the FFE There was a little confusion if this belongs to the FeatureFreeze or KernelFreeze. Since it's a package maintained by the kernel team the misconception came up that it is not affected by the Feature, but by the Kernel Freeze, hence it was not processed in time and information was missing. Without this patch the (new) "--kexec-file-syscall" option for s390x cannot be used with cosmic. And the customer/partner needs to wait for the next d* release (means for several month). This FFE now asks if the single commit (below) can be added to the kexec-tools (Ubuntu) of cosmic: Description: commit d4a948c268272cf37c71be820fb02bf40e56292b Author: Philipp Rudo Date: Wed May 16 14:27:18 2018 +0200 kexec/s390: Add support for kexec_file_load Since kernel 4.17-rc2 s390 supports the kexec_file_load system call. Add the new system call to kexec-tools and provide the -s (--kexec-file-syscall) option for s390 to support this new feature. Impact / Risk: -- Since the function / option is new and for s390(x) the risk is pretty low. There are no APIs expected to break or existing functions that are expected to fail while introducing this. Package dependencies will not change, nor the install/upgrade behaviour after this got added. Testing of the code, test builds and verification was already done by IBM. (see comment # 4) _ Provide a capability to load signed kernels. I.e. to boot signed kernels - from a Linux based boot loader or initial boot image - as required for secure/trusted boot mechanisms - for kdump kernels Function consist of 2 contributions - kernel 4.17 (available) - kexec-tools (currently not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1783086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789946] [NEW] DHCP server and client not working since kernel 4.15.0-32
Public bug reported: I installed Ubuntu server 18.04 on HP Proliant BL460c Gen8 server blades. I set up DHCP server for PXE boot. It was working, but since kernel update with version 4.15.0-32, PXE boot no longer works. DHCP server logs show "5 bad udp checksums in 5 packets" in a row. DHCP client is also not working on the machine due to similar errors. I switched back to kernel version 4.15-0-29 and it works again. I suspect the newer kernel might have introduced a bug about the network adapter driver. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 08:56 seq crw-rw 1 root audio 116, 33 Aug 30 08:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 30 09:08:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant BL460c Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0a9aa0b0-9a67-11e8-a1dc-fc15b41d0ee0 ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: HP dmi.bios.version: I31 dmi.chassis.type: 28 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrI31:bd12/20/2013:svnHP:pnProLiantBL460cGen8:pvr:cvnHP:ct28:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant BL460c Gen8 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789946 Title: DHCP server and client not working since kernel 4.15.0-32 Status in linux package in Ubuntu: New Bug description: I installed Ubuntu server 18.04 on HP Proliant BL460c Gen8 server blades. I set up DHCP server for PXE boot. It was working, but since kernel update with version 4.15.0-32, PXE boot no longer works. DHCP server logs show "5 bad udp checksums in 5 packets" in a row. DHCP client is also not working on the machine due to similar errors. I switched back to kernel version 4.15-0-29 and it works again. I suspect the newer kernel might have introduced a bug about the network adapter driver. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 08:56 seq crw-rw 1 root audio 116, 33 Aug 30 08:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 30 09:08:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant BL460c Gen8 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0a9aa0b0-9a67-11e8-a1dc-fc15b41d0ee0 ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2013 dmi.bios.vendor: HP dmi.bios.version: I31 dmi.chassis.type: 28 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrI31:bd12/20/2013:svnHP:pnProLiantBL460cGen8:pvr:cvnHP:ct28:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant BL460c Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to:
[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Apparently there's a firmware update (I was running 1.10, which is about a month old - I've updated the firmware several times during the life time of this bug). I'll update and wait for it to happen again. BTW - the behavior is usually that after this disconnect happens once, I can reset the USB controller (using sysfs API to unbind and re-bind xhci_hcd), but then it will get the problem again and again, several times an hour (its not very predictable, sometimes I get 2 in a row and sometimes half an hour can pass before it breaks again). I thought this can be temperature related, so I pushed the computer to low power mode after the first event of the day, and reset the bus, but it happened again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1783152] Re: Enable basic support for Solarflare 8000 series NIC
** Changed in: debian-installer (Ubuntu Trusty) Status: New => In Progress ** Changed in: debian-installer (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: debian-installer (Ubuntu Trusty) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Status in debian-installer source package in Trusty: In Progress Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788432] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2018-08-30 11:27 EDT--- Ah ok. So you run an 18.04 guest under an 16.04 host? Does the problem goes away with a newer QEMU? (e.g. from the cloud archive) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx_s390 [ 25.170835] CPU: 0 PID: 5590 Comm: stress-ng-sysfs Tainted: P OE 4.17.0-8-generic #9-Ubuntu [ 25.170837] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 25.170839] Krnl PSW :
[Kernel-packages] [Bug 1619815] Re: [Asus N752VX] Resuming after suspend restarts laptop (when on battery)
Luís Correia, you don't have the same problem as this report is not scoped to 18.04, or any Dell machine. Hence, if you want your problem addressed, use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619815 Title: [Asus N752VX] Resuming after suspend restarts laptop (when on battery) Status in linux package in Ubuntu: Incomplete Bug description: When suspending via closing lid or sudo pm-suspend, doesn't always suspend and when resuming the laptop restarts. Suspend resume works fine when the laptop is plugged in, the problem always appears when on battery. The laptop is asus N752VX ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikola 3842 F pulseaudio CurrentDesktop: KDE Date: Sat Sep 3 01:56:38 2016 HibernationDevice: RESUME=UUID=9c2c64a9-c98c-4d02-ae32-ace578c39024 InstallationDate: Installed on 2016-07-01 (63 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. N752VX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=3a04fbec-8e67-4764-8754-1d4ee730e82c ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N752VX.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N752VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN752VX.204:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N752VX 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/1619815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784331] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-30 09:47 EDT--- I don't see a reason , do not make this request public... All git-commits are currently available with kernel 4.19 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784331 Title: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. Is planned as part of kernel 4.19. Therefore a backport to kernel 4.18 will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787742] Re: TP-Link Archer T1U 5GHz WiFi adapter not compatible
@jsalisbury, which Upstream Kernel would you like me to attempt? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787742 Title: TP-Link Archer T1U 5GHz WiFi adapter not compatible Status in linux package in Ubuntu: Incomplete Bug description: My TP-Link Archer T1U 5GHz USB WiFi adapter/dongle is not being recognized by the system settings and WiFi setup wizards, likely due to a compatibility issue with the Linux kernel. The device is functional in Windows and recognized by my motherboard, but unfortunately it is a mere waste of a USB port with Ubuntu and other Linux distributions. - Terminal output when running 'lsusb' cmd: jeb@A880G:~$ lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 03f0:d407 Hewlett-Packard Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 008: ID 0461:4d75 Primax Electronics, Ltd Rocketfish RF-FLBTAD Bluetooth Adapter Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass) Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass) Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 009: ID 2357:0105 Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb1608 F pulseaudio /dev/snd/controlC1: jeb1608 F pulseaudio /dev/snd/controlC0: jeb1608 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 12:20:18 2018 InstallationDate: Installed on 2018-08-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787898] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-30 10:58 EDT---
Salesforce Ticket reference :
https://support.canonical.com/ua/s/case/500D01ngszbIAA/enable-configsclpofb-in-the-4150-kernel-config-file-for-the-1804-lst
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787898
Title:
[18.10 FEAT] Add kernel config option "CONFIG_SCLP_OFB"
Status in Ubuntu on IBM z Systems:
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
Impact: To boot an IBM Secure Service Container Appliance in an s390
LPAR. we need to be able to send the Open for Business (OFB) message
to signal that the appliance is up and running.
Fix: Set CONFIG_SCLP_OFB=y.
Regression Potential: The option enables only a few pieces of
architecture-specific code, so the potential impact is limited.
---
For successfully booting an IBM Secure Service Container Appliance in an s390
LPAR, we need to be able to send the OFB (Open for Business) message to the
Support Element to signal when the Appliance is fully up and running.
Basic support for OFB was added to the kernel with the following commit
https://github.com/projectacrn/acrn-kernel/commit/c6f70d3b8a32fdec60d3f78cb59423f056f16688
The kernel config option CONFIG_SCLP_OFB need to be set
This update is mandatory for 18.04 , but need to be requested first
for 18.10
$ git grep SCLP_OFB
debian.master/config/annotations:CONFIG_SCLP_OFB
policy<{'s390x': 'n'}>
debian.master/config/config.common.ubuntu:# CONFIG_SCLP_OFB is not set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1787898/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Ok, please make sure both BIOS and TBT are up-to-date. You can update them by doing the following: $ fwupdmgr refresh $ fwupdmgr update $ sudo reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1789924] [NEW] Missing Intel GPU pci-id's
Public bug reported: There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Summary changed: - Intel Whiskey lake (WHL) & Amber Lake (AML) support + Missing Intel GPU pci-id's ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
Since this is the first hit on Google, I'd like to elaborate on cberner's solution: you should choose the "A2DP Sink" profile in the "Output" tab of the Sound settings. The "A2DP Source" profile in the "Input" tab doesn't seem to work. -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783152] Re: Enable basic support for Solarflare 8000 series NIC
This is the patch for trusty debian-installer to pick up this new xenial hwe kernel. It's been tested by the customer with the SF 8000 series NICs on amd64 bare metal (back when using test packages from their private PPA), so the netboot install works on that NIC model. I built it on PPA for the supported architectures on trusty (amd64/i386, arm64/armhf, ppc64el/powerpc) [1], and used the built netboot images for testing. I tested for no regressions / without that NIC adapter, in the following platforms, plain and LVM partitioning, per discussion with folks from our server iso automated testing and server/arm teams. - amd64 bare-metal & kvm guest - arm64 qemu guest (see [2]) - ppc64el qemu guest (see [3]) On testing, the installer boots with the new kernel, installs it to the system, and the installed system boots correctly with it. [1] https://launchpad.net/~mfo/+archive/ubuntu/sf188840di/ [2] https://wiki.ubuntu.com/ARM64/QEMU [3] https://buggy.link/2018/01/31/ppc64le-on-x86_64-qemu-full-system-emulation.html ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** No longer affects: debian-installer (Ubuntu Xenial) ** Patch added: "d-i_trusty_sf188840.debdiff" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+attachment/5182677/+files/d-i_trusty_sf188840.debdiff ** Changed in: debian-installer (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/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: New Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+subscriptions --
[Kernel-packages] [Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
Host information: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial uname -a Linux s2lp5 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 09:18:59 UTC 2018 s390x s390x s390x GNU/Linux qemu: 2.5+dfsg-5ubuntu10.30 this was created using uvt: #!/bin/bash # # Quick and dirty script to create temporary guests which are reachable # from the kernel VPN via uvt-kvm. After creation one has to login once # via "virsh console " to figure out the ip address. :/ BASEDIR=$(dirname $0) if [ "$1" = "" ]; then echo "$(basename $0) " exit 1 fi VMNAME="$1" shift uvt-kvm create --cpu 2 --memory 2048 --disk 20 --password ubuntu \ --template $BASEDIR/uvt-template.xml $VMNAME arch=s390x "$@" uvt-template.xml: hvm 1 destroy restart preserve /usr/bin/qemu-system-s390x Hope that's enough info -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in:
[Kernel-packages] [Bug 1774366] Re: Fix MCE handling for user access of poisoned device-dax mapping
** 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/1774366
Title:
Fix MCE handling for user access of poisoned device-dax mapping
Status in intel:
Triaged
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
Description:
Customer reports:
—
We've tried the ndctl error injection. Now the error injection is
successful. But we have a couple of questions related with the
poisoned block.
Here are some tests/steps that I did:
1. I mmap the first 10GB of /dev/dax13.0 to virtual address space and
inject an error at offset 1GB (block offset should be 1GB/512bytes =
2097152) which seems fine:
[root@scaqae09celadm13 wning]# ndctl inject-error --uninject --block=2097152
--count=1 namespace13.0
Warning: Un-injecting previously injected errors here will
not cause the kernel to 'forget' its badblock entries. Those
have to be cleared through the normal process of writing
the affected blocks
{
"dev":"namespace13.0",
"mode":"dax",
"size":518967525376,
"uuid":"0738c8bd-3b3f-4989-9d0e-0e9c6006c810",
"chardev":"dax13.0",
"numa_node":0,
"badblock_count":1,
"badblocks":[
{ "offset":2097152, "length":1, "dimms":[ "nmem1" ] }
]
}
2. In my test program, I just try to read every address of the first
10GB. At the first time, when I read the offset 1GB, I got the SIGBUS
error, but in the sinfo struct of signal handler, the failed address
is NULL and signal code is 128 which seems incorrect. But then if we
run again, the unit test gets stuck here:
rt_sigaction(SIGBUS,
{0x400dd2, [], SA_RESTORER|SA_SIGINFO, 0x7fb5cf839270}
, NULL, 8) = 0
And here is the output of log messages:
Apr 3 14:39:23 scaqae09celadm13 kernel: mce: Uncorrected hardware memory
error in user-access at 952b20
Apr 3 14:51:11 scaqae09celadm13 kernel: mce: Uncorrected hardware memory
error in user-access at 94eb30
Apr 3 14:51:11 scaqae09celadm13 kernel: mce_notify_irq: 48 callbacks
suppressed
Apr 3 14:51:11 scaqae09celadm13 kernel: mce: [Hardware Error]: Machine check
events logged
Apr 3 14:51:11 scaqae09celadm13 kernel: Memory failure: 0x94eb300: reserved
kernel page still referenced by 1 users
Apr 3 14:51:11 scaqae09celadm13 kernel: Memory failure: 0x94eb300: recovery
action for reserved kernel page: Failed
Apr 3 14:51:11 scaqae09celadm13 kernel: mce: Memory error not recovered
The program I use is (simple do memcpy and directly read from the
target address):
for (i = 0; i < DAX_MAPPING_SIZE; i++) // DAX_MAPPING_SIZE is 10G
{ total += peek(buf + i); }
char peek(void *addr)
{ char temp[128]; memcpy(temp, addr, 1); return *(char *)addr; }
May I ask do we missed steps in triggering the SIGBUS error?
Target Kernel: 4.19
Target Release: 18.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774366/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783086] Re: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part
** Changed in: ubuntu-z-systems Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1783086 Title: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part Status in Ubuntu on IBM z Systems: Fix Committed Status in kexec-tools package in Ubuntu: Fix Committed Bug description: FeatureFreeze Exception (FFE): == Reason, rationale and benefits: --- The feature is based on the combination of two tickets: - 1783088 this ticket for the kernel part was just created for completeness reasons this part of the functionality automatically came with kernel 4.17 hence this LP ticket is 'Fix Released' - 1783086 this is the 'user space' part of the functionality that should be addressed by the FFE There was a little confusion if this belongs to the FeatureFreeze or KernelFreeze. Since it's a package maintained by the kernel team the misconception came up that it is not affected by the Feature, but by the Kernel Freeze, hence it was not processed in time and information was missing. Without this patch the (new) "--kexec-file-syscall" option for s390x cannot be used with cosmic. And the customer/partner needs to wait for the next d* release (means for several month). This FFE now asks if the single commit (below) can be added to the kexec-tools (Ubuntu) of cosmic: Description: commit d4a948c268272cf37c71be820fb02bf40e56292b Author: Philipp Rudo Date: Wed May 16 14:27:18 2018 +0200 kexec/s390: Add support for kexec_file_load Since kernel 4.17-rc2 s390 supports the kexec_file_load system call. Add the new system call to kexec-tools and provide the -s (--kexec-file-syscall) option for s390 to support this new feature. Impact / Risk: -- Since the function / option is new and for s390(x) the risk is pretty low. There are no APIs expected to break or existing functions that are expected to fail while introducing this. Package dependencies will not change, nor the install/upgrade behaviour after this got added. Testing of the code, test builds and verification was already done by IBM. (see comment # 4) _ Provide a capability to load signed kernels. I.e. to boot signed kernels - from a Linux based boot loader or initial boot image - as required for secure/trusted boot mechanisms - for kdump kernels Function consist of 2 contributions - kernel 4.17 (available) - kexec-tools (currently not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1783086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784331] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784331 Title: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. Is planned as part of kernel 4.19. Therefore a backport to kernel 4.18 will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Just got the issue again with latest Bionic kernel (Precision 5520 + TB16): [253938.395439] xhci_hcd :0e:00.0: ERROR unknown event type 15 [253943.344375] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [253943.344704] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [253943.344865] xhci_hcd :0e:00.0: HC died; cleaning up [253943.344953] usb 3-1: USB disconnect, device number 2 [253943.344955] usb 3-1.1: USB disconnect, device number 3 [253943.344957] usb 3-1.1.1: USB disconnect, device number 6 [253943.344960] usb 3-1.1.1.1: USB disconnect, device number 8 [253943.344963] usb 3-1.1.1.1.4: USB disconnect, device number 10 [253943.345081] usb 4-1: USB disconnect, device number 2 [253943.345083] usb 4-1.1: USB disconnect, device number 3 [253943.345086] usb 4-1.1.1: USB disconnect, device number 5 [253943.346372] usb 4-1.2: USB disconnect, device number 4 [253943.489086] usb 3-1.1.1.3: USB disconnect, device number 13 [253943.556882] usb 3-1.1.1.5: USB disconnect, device number 12 [253943.557415] usb 3-1.1.2: USB disconnect, device number 11 [253943.557687] usb 3-1.1.5: USB disconnect, device number 7 [253943.558220] usb 3-1.3: USB disconnect, device number 4 [253943.558465] usb 3-1.5: USB disconnect, device number 5 uname: Linux vesho 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller
[Kernel-packages] [Bug 1786878] Re: [Regression] kernel crashdump fails on arm64
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1786878 Title: [Regression] kernel crashdump fails on arm64 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] With artful, crashdump worked on the Cavium CRBs, Cavium-based Gigabyte boards and the Qualcomm Amberwing board, but it no longer works with v4.15. While possibly not a regression, crashdump also does not currently work with the HiSilicon D05 board, but does with the proposed fixes. [Test Case] sudo apt install linux-crashdump sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] Fixes are currently staged in linux-next: 09ffcb0d718a0 arm64: acpi: fix alignment fault in accessing ACPI 20d12cf990618 efi/arm: map UEFI memory map even w/o runtime services enabled 3ea86495aef2f efi/arm: preserve early mapping of UEFI memory map longer for BGRT 5bcd44083a082 drivers: acpi: add dependency of EFI for arm64 50d7ba36b916d arm64: export memblock_reserve()d regions via /proc/iomem [Regression Risk] Patches are all ARM specific. Tested on 4 ARM platforms - those listed above, as well as the HiSilicon D06. These patches are not sufficient to make kdump on the HiSilicon D06 work - but that's not a regression. However, no kdump-unrelated regressions were noticed on the D06. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -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 ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** 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 -- kernel-stable-master-bug: 1788744 phase: Packaging proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 30. August 2018 14:02 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 -- swm properties -- kernel-stable-master-bug: 1788744 - phase: Packaging + phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 30. August 2018 14:02 UTC -- 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/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New 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: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New 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 -- kernel-stable-master-bug: 1788744 phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785780] Re: TB 16 issue on Dell Lattitude 7490 with large amount of data
** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => 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/1785780 Title: TB 16 issue on Dell Lattitude 7490 with large amount of data Status in Dell Sputnik: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: ===SRU Justification=== [Impact] Packets are silently corrupted on Dell TB16's ethernet. [Fix] Disable RX aggregation on new Dell TB16 dock. [Test] User confirms the patch fixes the issue. [Regression Potential] Low. The workaround already works, we just add a new USB serial to let new TB16 dock also uses this workaround. ===Original Bug Report=== Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) We can confirm this issue on this kernel. Creating new issue as stated in this bug (#1729674) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1955 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd06/07/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1785780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774366] Re: Fix MCE handling for user access of poisoned device-dax mapping
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => 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/1774366
Title:
Fix MCE handling for user access of poisoned device-dax mapping
Status in intel:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
Description:
Customer reports:
—
We've tried the ndctl error injection. Now the error injection is
successful. But we have a couple of questions related with the
poisoned block.
Here are some tests/steps that I did:
1. I mmap the first 10GB of /dev/dax13.0 to virtual address space and
inject an error at offset 1GB (block offset should be 1GB/512bytes =
2097152) which seems fine:
[root@scaqae09celadm13 wning]# ndctl inject-error --uninject --block=2097152
--count=1 namespace13.0
Warning: Un-injecting previously injected errors here will
not cause the kernel to 'forget' its badblock entries. Those
have to be cleared through the normal process of writing
the affected blocks
{
"dev":"namespace13.0",
"mode":"dax",
"size":518967525376,
"uuid":"0738c8bd-3b3f-4989-9d0e-0e9c6006c810",
"chardev":"dax13.0",
"numa_node":0,
"badblock_count":1,
"badblocks":[
{ "offset":2097152, "length":1, "dimms":[ "nmem1" ] }
]
}
2. In my test program, I just try to read every address of the first
10GB. At the first time, when I read the offset 1GB, I got the SIGBUS
error, but in the sinfo struct of signal handler, the failed address
is NULL and signal code is 128 which seems incorrect. But then if we
run again, the unit test gets stuck here:
rt_sigaction(SIGBUS,
{0x400dd2, [], SA_RESTORER|SA_SIGINFO, 0x7fb5cf839270}
, NULL, 8) = 0
And here is the output of log messages:
Apr 3 14:39:23 scaqae09celadm13 kernel: mce: Uncorrected hardware memory
error in user-access at 952b20
Apr 3 14:51:11 scaqae09celadm13 kernel: mce: Uncorrected hardware memory
error in user-access at 94eb30
Apr 3 14:51:11 scaqae09celadm13 kernel: mce_notify_irq: 48 callbacks
suppressed
Apr 3 14:51:11 scaqae09celadm13 kernel: mce: [Hardware Error]: Machine check
events logged
Apr 3 14:51:11 scaqae09celadm13 kernel: Memory failure: 0x94eb300: reserved
kernel page still referenced by 1 users
Apr 3 14:51:11 scaqae09celadm13 kernel: Memory failure: 0x94eb300: recovery
action for reserved kernel page: Failed
Apr 3 14:51:11 scaqae09celadm13 kernel: mce: Memory error not recovered
The program I use is (simple do memcpy and directly read from the
target address):
for (i = 0; i < DAX_MAPPING_SIZE; i++) // DAX_MAPPING_SIZE is 10G
{ total += peek(buf + i); }
char peek(void *addr)
{ char temp[128]; memcpy(temp, addr, 1); return *(char *)addr; }
May I ask do we missed steps in triggering the SIGBUS error?
Target Kernel: 4.19
Target Release: 18.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774366/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New 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: New Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New 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 -- kernel-stable-master-bug: 1788744 phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789358] Re: Support Power Management for Thunderbolt Controller
** 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/1789358 Title: Support Power Management for Thunderbolt Controller Status in HWE Next: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Bug description: ===SRU Justification=== [Impact] New TBT controllers may use Native PCIe Enumeration (i.e. just like other normal PCIe device listed under lspci) instead of ACPI hotplug. Since TBT controller stops getting unplugged from PCIe bus, it draws additional power. [Fix] Support runtime power management for TBT controllers, so it can be put to D3 to save powers. [Test] I tested and verified this patch series can make Lenovo T480's TBT controller enters PCI D3 at runtime. I also verified this series on XPS 9370 which uses ACPI hotplug, no regression observed. [Regression Potential] Low. Almost all TBT controllers in the wild still uses ACPI hotplug, this series won't affect those users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1789358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787695] Re: : unable to handle kernel paging request at ffff9f2ed2aa5844
Like I said, I was unable to test 4.18. However, on mainline 4.15.18 I also get a screen lockup, although without a similar trace. Not sure if that counts, so feel free to correct tagging. ** 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/1787695 Title: : unable to handle kernel paging request at 9f2ed2aa5844 Status in linux package in Ubuntu: Confirmed Bug description: Since going from 4.13 to 4.15, I'm getting crashes where the system completely locks up and display freezes. Below is what syslog had after my most recent. I'm on Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18, the system is a Ryzen 1600 on AsRock AB350M with latest UEFI, RX 480 using open drivers. (I would have used ubuntu-bug, but it says "not an official package" even with ubuntu-bug linux. Also, lspci -vnvn says Input/output error so I could not include that.) Aug 18 08:39:19 freyja kernel: [20514.280608] BUG: unable to handle kernel paging request at 9f2ed2aa5844 Aug 18 08:39:19 freyja kernel: [20514.280621] IP: SyS_read+0x16/0xc0 Aug 18 08:39:19 freyja kernel: [20514.280623] PGD 81e875067 P4D 81e875067 PUD 0 Aug 18 08:39:19 freyja kernel: [20514.280630] Oops: 0002 [#1] SMP NOPTI Aug 18 08:39:19 freyja kernel: [20514.280633] Modules linked in: xt_CHECKSUM iptable_mangle nls_iso8859_1 ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype ebtable_filter xt_conntrack ebtables br_netfilter bridge stp llc aufs ip6table_filter ip6_tables xt_TCPMSS acpi_call(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) iptable_filter ip_tables x_tables sch_fq_codel binfmt_misc nct6775 btrfs zstd_compress lm78 hwmon_vid snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_seq_midi snd_seq_midi_event snd_hda_intel snd_rawmidi snd_hda_codec edac_mce_amd snd_hda_core snd_hwdep crct10dif_pclmul crc32_pclmul joydev ghash_clmulni_intel snd_pcm ccp snd_seq pcbc snd_seq_device Aug 18 08:39:19 freyja kernel: [20514.280692] snd_timer snd aesni_intel soundcore aes_x86_64 input_leds crypto_simd glue_helper cryptd serio_raw wmi_bmof i2c_piix4 k10temp shpchp mac_hid kvm irqbypass parport_pc ppdev lp parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 hid_generic usbhid hid amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt uas fb_sys_fops drm nvme r8169 usb_storage ahci nvme_core mii libahci wmi gpio_amdpt gpio_generic Aug 18 08:39:19 freyja kernel: [20514.280737] CPU: 1 PID: 4527 Comm: Chrome_IOThread Tainted: GW OE4.15.0-32-generic #35~16.04.1-Ubuntu Aug 18 08:39:19 freyja kernel: [20514.280739] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P4.90 07/06/2018 Aug 18 08:39:19 freyja kernel: [20514.280743] RIP: 0010:SyS_read+0x16/0xc0 Aug 18 08:39:19 freyja kernel: [20514.280746] RSP: 0018:9f2e8a453f08 EFLAGS: 00010246 Aug 18 08:39:19 freyja kernel: [20514.280749] RAX: 8c078eb0 RBX: 9f2e8a453f58 RCX: 7f040245d9e0 Aug 18 08:39:19 freyja kernel: [20514.280751] RDX: 0001 RSI: 7f040245d9d7 RDI: 0010 Aug 18 08:39:19 freyja kernel: [20514.280754] RBP: 9f2e8a453f28 R08: 7f03f8001a30 R09: 0001 Aug 18 08:39:19 freyja kernel: [20514.280756] R10: R11: R12: Aug 18 08:39:19 freyja kernel: [20514.280758] R13: 7f040245d9d7 R14: 0001 R15: Aug 18 08:39:19 freyja kernel: [20514.280761] FS: 7f040245e700() GS:8a775ec4() knlGS: Aug 18 08:39:19 freyja kernel: [20514.280763] CS: 0010 DS: ES: CR0: 80050033 Aug 18 08:39:19 freyja kernel: [20514.280766] CR2: 9f2ed2aa5844 CR3: 0007a29a2000 CR4: 003406e0 Aug 18 08:39:19 freyja kernel: [20514.280768] Call Trace: Aug 18 08:39:19 freyja kernel: [20514.280775] do_syscall_64+0x73/0x130 Aug 18 08:39:19 freyja kernel: [20514.280781] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Aug 18 08:39:19 freyja kernel: [20514.280784] RIP: 0033:0x7f0412e6b51d Aug 18 08:39:19 freyja kernel: [20514.280786] RSP: 002b:7f040245d9c0 EFLAGS: 0293 ORIG_RAX: Aug 18 08:39:19 freyja kernel: [20514.280789] RAX: ffda RBX: 0010 RCX: 7f0412e6b51d Aug 18 08:39:19 freyja kernel: [20514.280791] RDX: 0001 RSI: 7f040245d9d7 RDI: 0010 Aug 18 08:39:19 freyja kernel: [20514.280793] RBP: 7f040245d9f0 R08:
[Kernel-packages] [Bug 1789772] Re: tlbie master timeout checkstop (using NVidia/GPU)
** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789772 Title: tlbie master timeout checkstop (using NVidia/GPU) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: A hung state machine in the chip's NMU logic can trigger a fatal condition that will be flagged by hardware through a checkstop. Hence, customers that have a Power 9 Whitherspoon (equipped with GPUs) will experience a crash on their server when using NVIDIA's toolkit. The server will crash with the following hardware failing message: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0 In this case, a `NCUFIR[10] tlbie master timeout` has been observed by only starting the NVIDIA ATS driver. This issue is being triggered because the NMU logic is getting stuck when a page is upgraded from RO -> RW without a following tlbie. This is addressed with the following patches: bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype 044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from radix.h to pgtable-radix.c f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1789772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://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 1787742] Re: TP-Link Archer T1U 5GHz WiFi adapter not compatible
Hey Joseph, Sorry for the late response. I'll try this today and get back to you. On Tue, Aug 21, 2018, 5:26 PM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.18 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.18.3 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1787742 > > Title: > TP-Link Archer T1U 5GHz WiFi adapter not compatible > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > My TP-Link Archer T1U 5GHz USB WiFi adapter/dongle is not being > recognized by the system settings and WiFi setup wizards, likely due to a > compatibility issue with the Linux kernel. > The device is functional in Windows and recognized by my motherboard, > but unfortunately it is a mere waste of a USB port with Ubuntu and other > Linux distributions. > > - > Terminal output when running 'lsusb' cmd: > jeb@A880G:~$ lsusb > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 006 Device 002: ID 03f0:d407 Hewlett-Packard > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 005 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser > Mouse] > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader > Bus 001 Device 008: ID 0461:4d75 Primax Electronics, Ltd Rocketfish > RF-FLBTAD Bluetooth Adapter > Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface > Subclass) > Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface > Subclass) > Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub > (part of BCM2046 Bluetooth) > Bus 001 Device 009: ID 2357:0105 > Bus 001 Device 003: ID 148f:5370 Ralink Technology, Corp. RT5370 > Wireless Adapter > Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > - > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-32-generic 4.15.0-32.35 > ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 > Uname: Linux 4.15.0-32-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC2: jeb1608 F pulseaudio >/dev/snd/controlC1: jeb1608 F pulseaudio >/dev/snd/controlC0: jeb1608 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sat Aug 18 12:20:18 2018 > InstallationDate: Installed on 2018-08-17 (1 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: BIOSTAR Group A880G+ > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 nouveaufb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic > root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 > RelatedPackageVersions: >linux-restricted-modules-4.15.0-32-generic N/A >linux-backports-modules-4.15.0-32-generic N/A >linux-firmware 1.173.1 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 080016 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A880G+ > dmi.board.vendor: BIOSTAR Group > dmi.chassis.asset.tag: None > dmi.chassis.type: 3 > dmi.chassis.vendor: BIOSTAR Group > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A880G+ > dmi.sys.vendor: BIOSTAR Group > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787742/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
The number of processes (in systemd, tasks). The command below works for me. Now, should we change the default on our test systems? Running under systemd-run does not look like a good option. # systemd-run -p TasksMax=100 ./testcases/bin/msgstress03 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in systemd source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783086] Re: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part
** Changed in: kexec-tools (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1783086 Title: [18.10 FEAT] Enable kexec_file_load system call - kexec-tools part Status in Ubuntu on IBM z Systems: Confirmed Status in kexec-tools package in Ubuntu: Fix Committed Bug description: FeatureFreeze Exception (FFE): == Reason, rationale and benefits: --- The feature is based on the combination of two tickets: - 1783088 this ticket for the kernel part was just created for completeness reasons this part of the functionality automatically came with kernel 4.17 hence this LP ticket is 'Fix Released' - 1783086 this is the 'user space' part of the functionality that should be addressed by the FFE There was a little confusion if this belongs to the FeatureFreeze or KernelFreeze. Since it's a package maintained by the kernel team the misconception came up that it is not affected by the Feature, but by the Kernel Freeze, hence it was not processed in time and information was missing. Without this patch the (new) "--kexec-file-syscall" option for s390x cannot be used with cosmic. And the customer/partner needs to wait for the next d* release (means for several month). This FFE now asks if the single commit (below) can be added to the kexec-tools (Ubuntu) of cosmic: Description: commit d4a948c268272cf37c71be820fb02bf40e56292b Author: Philipp Rudo Date: Wed May 16 14:27:18 2018 +0200 kexec/s390: Add support for kexec_file_load Since kernel 4.17-rc2 s390 supports the kexec_file_load system call. Add the new system call to kexec-tools and provide the -s (--kexec-file-syscall) option for s390 to support this new feature. Impact / Risk: -- Since the function / option is new and for s390(x) the risk is pretty low. There are no APIs expected to break or existing functions that are expected to fail while introducing this. Package dependencies will not change, nor the install/upgrade behaviour after this got added. Testing of the code, test builds and verification was already done by IBM. (see comment # 4) _ Provide a capability to load signed kernels. I.e. to boot signed kernels - from a Linux based boot loader or initial boot image - as required for secure/trusted boot mechanisms - for kdump kernels Function consist of 2 contributions - kernel 4.17 (available) - kexec-tools (currently not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1783086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789436] Re: pmtu.sh fails on 4.18 kernel
Submitted proper fix upstream. Waiting for reviews. http://patchwork.ozlabs.org/project/netdev/list/?series=63268 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789436 Title: pmtu.sh fails on 4.18 kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: pmtu.sh is a network selftest that was introduced on 4.17. It is currently failing on 4.18. After revert of ccd740cbc6 "vti6: Add pmtu handling to vti6_xmit.", it passes. The fail is in the nature of holding netdevices refcounts, so some network operations start hanging, including the loading and removal of network modules. [ 159.936543] unregister_netdevice: waiting for veth_b to become free. Usage count = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789772] Re: tlbie master timeout checkstop (using NVidia/GPU)
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789772 Title: tlbie master timeout checkstop (using NVidia/GPU) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: A hung state machine in the chip's NMU logic can trigger a fatal condition that will be flagged by hardware through a checkstop. Hence, customers that have a Power 9 Whitherspoon (equipped with GPUs) will experience a crash on their server when using NVIDIA's toolkit. The server will crash with the following hardware failing message: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0 In this case, a `NCUFIR[10] tlbie master timeout` has been observed by only starting the NVIDIA ATS driver. This issue is being triggered because the NMU logic is getting stuck when a page is upgraded from RO -> RW without a following tlbie. This is addressed with the following patches: bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype 044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from radix.h to pgtable-radix.c f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1789772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1619815] Re: [Asus N752VX] Resuming after suspend restarts laptop (when on battery)
Dell XPS 13 9350 upgraded from 16.04 to 18.04 had the same problem. Used solution provided by Alex on post #10 and it's fine now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619815 Title: [Asus N752VX] Resuming after suspend restarts laptop (when on battery) Status in linux package in Ubuntu: Incomplete Bug description: When suspending via closing lid or sudo pm-suspend, doesn't always suspend and when resuming the laptop restarts. Suspend resume works fine when the laptop is plugged in, the problem always appears when on battery. The laptop is asus N752VX ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikola 3842 F pulseaudio CurrentDesktop: KDE Date: Sat Sep 3 01:56:38 2016 HibernationDevice: RESUME=UUID=9c2c64a9-c98c-4d02-ae32-ace578c39024 InstallationDate: Installed on 2016-07-01 (63 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. N752VX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=3a04fbec-8e67-4764-8754-1d4ee730e82c ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N752VX.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N752VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN752VX.204:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N752VX 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/1619815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag
Thanks for testing. I'll submit an SRU request for this commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789653 Title: regression with EXT4 file systems and meta_bg flag Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hello, In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all partitions in ext4 with flag meta_bg : kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap for group 0 overlaps block group descriptors kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted! Go back with the kernel 4.4.0-133-generic and all partitions mount correctly. It looks like this: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd The patch is available in 4.4.147 (https://lwn.net/Articles/762083/) --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap InstallationDate: Installed on 2017-04-28 (488 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 RelatedPackageVersions: linux-restricted-modules-4.4.0-134-generic N/A linux-backports-modules-4.4.0-134-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/31/2013 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap InstallationDate: Installed on 2017-04-28 (488 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 RelatedPackageVersions: linux-restricted-modules-4.4.0-134-generic N/A linux-backports-modules-4.4.0-134-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial Uname: Linux 4.4.0-134-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: août 29 21:01:28 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT= MAC=01:00:5e:00:00:01:a0:1b:29:89:4f:1a:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 août 29 21:02:08 Template1604LTS kernel: [UFW BLOCK] IN=admin OUT=
[Kernel-packages] [Bug 1788730] Re: TP-LINK TG-3468 network card not recognized correctly
Good news! I didn't have tried again "folder 2" files, went straight to 4.19rc1, and it worked fine! Nic is detected and operational as it should be. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788730 Title: TP-LINK TG-3468 network card not recognized correctly Status in linux package in Ubuntu: In Progress Bug description: A few days ago purchased a couple of TP-LINK TG-3468 network cards (reviewed by Phoronix here: https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both brand new, not reused. After installed them to a pc, to my surprise, one of them was correctly identified and the other was incorrectly identified as "NCube Device 8168 (rev 06)". After DuckDuckGoing for a while I found this kernel bud report for FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e -network-card.57734/ IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I wanted to report this so it can be fixed, please let me know wich logs/data should I provide. When ran lspci -nv this is shown for the correct nic: 03:00.0 0200: 10ec:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 27 I/O ports at e800 [size=256] Memory at febff000 (64-bit, non-prefetchable) [size=4K] Memory at fdffc000 (64-bit, prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 Kernel modules: r8169 And this for the incorrect one: 01:00.0 0200: 10ff:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c800 [size=256] Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K] Memory at fdefc000 (64-bit, prefetchable) [size=16K] Capabilities: 1) lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 2) In regard to the package I think this is related to the kernel itself? 3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the r8169 driver should be used. 4) The network card was erroneously detected as a different one and the driver was not loaded by the kernel. Best regards. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-133-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791 InstallationDate: Installed on 2017-12-06 (260 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 RelatedPackageVersions: linux-restricted-modules-4.4.0-133-generic N/A linux-backports-modules-4.4.0-133-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-133-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-CM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1788432] Comment bridged from LTC Bugzilla
--- Comment From pa...@de.ibm.com 2018-08-30 08:06 EDT--- I've tried to reproduce the issue but failed miserably. I installed a fresh Ubuntu 18.04.1 made a cqow image essentially copying the filesystem for the guest. That means I was running the 4.15.0-29-generic kernel (reported as affected) both as host and guest. After an hour of running with 50 hogs (as root) I hit OOM but not the reported bug: # uname -r 4.15.0-29-generic # ~/git/stress-ng/stress-ng --sysfs 50 -t 5h stress-ng: info: [1148] dispatching hogs: 50 sysfs [ 3993.143284] Out of memory: Kill process 587 (networkd-dispat) score 3 or sacrifice child [ 3993.143295] Killed process 587 (networkd-dispat) total-vm:99944kB, anon-rss:7792kB, file-rss:2512kB, shmem-rss:0kB [ 4012.251714] Out of memory: Kill process 619 (libvirtd) score 3 or sacrifice child [ 4012.251742] Killed process 619 (libvirtd) total-vm:1349072kB, anon-rss:6980kB, file-rss:2728kB, shmem-rss:0kB Can you provide some more information about your setup (e.g. qemu version, domain xml or qemu command line, etc.)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797]
[Kernel-packages] [Bug 1788751] Re: linux-azure: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- 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/1788751 Title: linux-azure: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: New 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/1788751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
Hi,
I think the fix is removing the "return" and letting the code fall through in
sata_down_spd_limit().
Please give me some time to review the latest log, and I will need to
reconfigure a couple of local
systems and re-test with that change. 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/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
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:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
the second backup hard drive is a Western Digital WD5003AZEX. I
installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
the issue is with the second hard drive, when installing the WD HDD
wouldn't even come as an option to install, and after boot the WD HDD
still wouldn't come up, this is the dmesg with the stock kernel (4.15)
https://paste.ubuntu.com/p/kpxh94v2SK/
ata6 is the WD HDD that refuses to work. The messages:
[ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
[ 302.107658] ata6: hard resetting link
[ 307.860291] ata6: link is slow to respond, please be patient (ready=0)
[ 312.120898] ata6: COMRESET failed (errno=-16)
[ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
[ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu
[ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.445140] kworker/u8:5D0 201 2 0x8000
[ 363.445155] Workqueue: events_unbound async_run_entry_fn
[ 363.445157] Call Trace:
[ 363.445171] __schedule+0x291/0x8a0
[ 363.445177] schedule+0x2c/0x80
[ 363.445182] ata_port_wait_eh+0x7c/0xf0
[ 363.445186] ? wait_woken+0x80/0x80
[ 363.445189] ata_port_probe+0x28/0x40
[ 363.445192] async_port_probe+0x2e/0x52
[ 363.445196] async_run_entry_fn+0x3c/0x150
[ 363.445199] process_one_work+0x1de/0x410
[ 363.445203] worker_thread+0x32/0x410
[ 363.445207] kthread+0x121/0x140
[ 363.445210] ? process_one_work+0x410/0x410
[ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70
[ 363.445218] ret_from_fork+0x22/0x40
Repeat constantly. Also when I try to turn off the computer, the
computer seem to freeze, the lights of the keyboard and mouse turn off
and the computer just stay on.
I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
Kernel Update Utility. And with this kernel version, or any previous
version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
with linux 4.14 and the WD HDD finally coming up at the end:
https://paste.ubuntu.com/p/Gd3cGFbjTJ/
Also tried with with linux 4.17 but the WD HDD would also refuse to
work on this version. Here's another dmesg with this version:
https://paste.ubuntu.com/p/PmNn96vZZv/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: testtest756 F pulseaudio
/dev/snd/controlC1: testtest756 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,10ec,00100101
HDA:10de0002,10de0101,0010'
Controls : 56
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,38422651,00100100'
Controls : 21
Simple ctrls : 3
CurrentDesktop: LXDE
Date: Thu Jul 26 17:10:58 2018
HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
InstallationDate: Installed on 2018-07-26 (0 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: 113 1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2008
dmi.bios.vendor: Phoenix Technologies, LTD
[Kernel-packages] [Bug 1788744] Re: linux: 4.15.0-34.37 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788744 Title: linux: 4.15.0-34.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-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: New 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 1788754 (linux-azure), bug 1788755 (linux-azure), bug 1788757 (linux-azure-edge), bug 1788758 (linux-gcp), bug 1788760 (linux-hwe), bug 1788761 (linux-hwe-edge) derivatives: bug 1788747 (linux-raspi2), bug 1788748 (linux-oem), bug 1788750 (linux-aws), bug 1788751 (linux-azure), bug 1788752 (linux-gcp), bug 1788753 (linux-kvm) -- 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/1788744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
