[Kernel-packages] [Bug 1832369] Re: [Thomson THN14B] Internal speaker does not work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832369 Title: [Thomson THN14B] Internal speaker does not work Status in linux package in Ubuntu: Expired Bug description: HI, I have a thomson THN14B with audio card rt5651 and bluetooth If i list a aplay -l to list all my sound card i get : Liste des Périphériques Matériels PLAYBACK carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 [] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) [] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal speaker sound. Have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandra 1154 F pulseaudio /dev/snd/pcmC1D0c: sandra 1154 F...m pulseaudio /dev/snd/pcmC1D0p: sandra 1154 F...m pulseaudio /dev/snd/controlC0: sandra 1154 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 11 17:21:59 2019 InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago) dmi.bios.date: 01/02/2018 dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: THN14B dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Thomson modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832419] Re: Acer Chromebook [banon] display freezes
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832419 Title: Acer Chromebook [banon] display freezes Status in linux package in Ubuntu: Expired Bug description: Freezes when connected to wifi. Running lsof -i and closing some of the processes results in black display, need to restart computer. i can use the computer for very short periods when connected to the internet, frequently the display freezes requiring restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Tue Jun 11 18:39:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: GOOGLE Banon ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-51-generic SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839293] Re: bionic/linux: 4.15.0-58.64 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Testing phase-changed: Friday, 09. August 2019 21:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839293 Title: bionic/linux: 4.15.0-58.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Testing phase-changed: Friday, 09. August 2019 21:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839293] Re: bionic/linux: 4.15.0-58.64 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/22fPD3Kf/131-bionic-linux- image-4150-58-generic-4150-5864 ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839293 Title: bionic/linux: 4.15.0-58.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Testing phase-changed: Friday, 09. August 2019 21:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836755] Re: hda/realtek: can't detect external mic on a Dell machine
** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-xenial ** Tags added: verification-done-bionic verification-done-disco verification-done-xenial -- 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/1836755 Title: hda/realtek: can't detect external mic on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: New Bug description: [Impact] The external can't be detected when plugging headset in the front audio jack. [Fix] apply the alc891 fixup to set headset-mic and headpphone-mic pins. [Test Case] apply this patch and boot with the kernel, plug the headset-mic and choose headset-mic from popup dialogue, the headset-mic can record sound very well. [Regression Risk] Low. this patch is specific to a dell machine by pin configuration definition. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
Just began dealing with this issue in Ubuntu 19.04. Basic fresh installation. Copying ~1 TB between Hard Disk A and Hard Disk B caused the entire system to stop responding for minutes at a time. While it was 'responding' the mouse movement on-screen stuttered badly and drifted. Keyboard input is completely ignored. The data transfer is between two SATA drives. Copying from a USB stick has produced the same effect, however the data was ~120 GB. Using both cp as well as the file manager produces this effect. I notice the delay in response time in the terminal during these copy jobs, when attempting to type anything, the delay in a response in the system is nearly a full minute. I WAS able to reproduce this on my laptop as well, running the same fresh installation but with 24 GB ram and 16 CPU threads, from SSD to SSD instead of HDD to HDD. AMD FX-6300 (6 cores) 8 GB DDR3 1600 ram GeForce GTX 1060 6GB 64-bit Ubuntu 19.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in linux package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in
Hello Kai-Heng Feng! The upgrade to the mainline kernel ver. 5.3rc3 fixed the problem, now it's working OOTB! Thank you everyone for your hints and support! ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-03-31 (13 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.2-050002-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32
I test it on Ubuntu 19.04, in booting font is OK, but tty still very small -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: == Justification == The console font size on a high resolution screen is only suitable for eagles, although we can choose a bigger font by running: sudo dpkg-reconfigure console-setup But that is not enough, the font size before video driver kicks in is still small. If we need to debug some early stage issues that will be a problem. == Fix == ac8b6f14 (Fonts: New Terminus large console font) Config for this TER16x32 and the compiled-in fonts support needs to be enabled to keep engineers away from ophthalmologists. * Disco It's already there. Just need to enable the configs. * Cosmic / Bionic Patch can be cherry-picked. * Xenial It needs an extra patch to make it a clean cherry-pick: * 7bcae826 (lib/fonts/Kconfig: keep non-Sparc fonts listed together * Trusty It needs two extra patches to make it a clean cherry-pick: * fonts: Add 6x10 font (33ac9dba) * lib/fonts/Kconfig: keep non-Sparc fonts listed together (7bcae826). And a config entry for the 6x10 font. Commit "fonts: Add 6x10 font" is just adding a new font. Commit "lib/fonts/Kconfig: keep non-Sparc fonts listed together" is just a patch for context rearrangement. I think these two are safe to be pulled-in. == Test == Test kernels: http://people.canonical.com/~phlin/kernel/lp-1819881-font/ Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in /etc/default/grub, and follow these steps. * Disco sudo update-grub; sudo reboot * Cosmic / Bionic Add "GRUB_GFXPAYLOAD_LINUX=3840x2160" to /etc/default/grub sudo update-grub; sudo reboot * Xenial sudo update-grub; sudo reboot * Trusty sudo update-grub; sudo reboot (I need the proprietary nvidia driver to boot for my SUT - Dell Precision M3800) The font before the video driver kicks in will get bigger. == Regression potential == Minimal, changes are limited to adding console fonts, turn on fonts related kernel configs. [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I am using one displayport 4k monitor, and one hdmi 1080p monitor. They keep waking each other up. When I used an adapter to make the 1080p monitor connect via a displayport > hdmi adapter, they both just output black when trying to sleep and cannot be woken up. They are still outputting black, they did not go to sleep. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.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.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+subscr
[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I am having the same issue on my rx570, I am on kernel 5.1.21 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.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.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839707] Re: System does not shutdown with any kernel >= v4.6.3
Could very likely be, or closely related to: https://bugzilla.kernel.org/show_bug.cgi?id=199349 If the issue is RCU (Read-Copy-Update) or Memory-Management related and specific to the AMD Turion X2 the most obvious suspect commits between v4.6.2..v4.6.3 are: $ gitlog v4.6.2..v4.6.3 -- mm/ a5f09a92b7ec 2016-06-24 10:22:04 -0700 N Gerald Schaefer mm: thp: broken page count after commit aa88b68c3b1d 50c596c23c08 2016-06-24 10:22:03 -0700 N Tejun Heo memcg: add RCU locking around css_for_each_descendant_pre() in memcg_offline_kmem() ** Bug watch added: Linux Kernel Bug Tracker #199349 https://bugzilla.kernel.org/show_bug.cgi?id=199349 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839707 Title: System does not shutdown with any kernel >= v4.6.3 Status in linux package in Ubuntu: Confirmed Bug description: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. In addition I should mention I have tried many workarounds suggested on forums and in IRC. This includes but not confined to running with:- noapic nolapic and both Windows and Linux acpi_osi ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
My server was pretty unstable until I've installed latest mainline
kernel 5.2.8-050208-generic and now it seems to work fine. The problems
started when I changed from kerneel linux-image-
unsigned-4.18.12-041812-generic to linux-image-generic-hwe-18.04
(5.0.0.23.80).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
detected buffer overflow in strcat
kernel BUG at <...>/lib/string.c:1052!
invalid opcode: [#1] SMP PTI
RIP: 0010:fortify_panic+0x13/0x1f
Call Trace:
smb21_set_oplock_level+0xde/0x190 [cifs]
smb3_set_oplock_level+0x22/0x90 [cifs]
smb2_set_fid+0x76/0xb0 [cifs]
cifs_new_fileinfo+0x268/0x3c0 [cifs]
? smb2_get_lease_key+0x40/0x40 [cifs]
? cifs_new_fileinfo+0x268/0x3c0 [cifs]
cifs_open+0x57c/0x8d0 [cifs]
do_dentry_open+0x1fe/0x320
[...]
* By analyzing the code of smb21_set_oplock_level(), we've noticed the
only way fortify function strcat() would get overflow was if the value
of cinode->oplock got corrupted in a another thread leading to a
buffer write bigger then buffer size. In this function, the 'message'
buffer writes are governed by cinode->oplock, so only a different
thread cleaning the oplock value would lead to 'message' overflow.
* By the same time we worked this analysis, a fix was proposed
upstream for this issue in the form of commit 6a54b2e002c9 ("cifs:
fix strcat buffer overflow and reduce raciness in
smb21_set_oplock_level()"), by the same reporter of this LP. The fix
is simple and directly addresses this problem, so we hereby request
its SRU into Bionic kernel - it's already present in linux stable
branches.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers and by
the aforementioned tests; also, the scope is restricted to cifs only
so the likelihood of regressions is considered low. The commit
introduces no functional changes and the only affected path was just
refactored in a way to prevent overflow and reduce race potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I also get this Trying to unpack rootfs image as initramfs... Initramfs unpacking failed: Decoding failed on a fully uptodate eoan, just after booting today, in 'journalctl -b'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Confirmed -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 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 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
Hi Kai-Heng Feng, So I downloaded all the files, then ran "sudo dpkg -i linux-*.deb" (i think that is how you install the test kernel?) When I tried to boot without IVRS or quiet splash, it got stuck on "Loading initial ramdisk" and never got past it. So I tried to go in recovery, still got the IOAPIC[32] not in IVRS table, then eventually kernel panic again because "timer doesnt work through interrupt-remapped io-apic" https://imgur.com/Th1mdXB If you have more test I can try to boot to see what happens On a side note, for everyone else: On ubuntu and mint I had freezing happening every few days, never could last a week without it freezing at least once. However, since booting off kernel 5.2.3, ive not had any freezing yet. So you may want to try that kernel if you have also experienced freezing systems. Note, when I first booted, i got a blank cursor at the login screen. Had to install drivers from amd, and then it worked after a reboot. Still need the "ivrs_ioapic[32]=00:14.0" though. More info here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838176 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 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 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 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 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C
Could you let me know when would this be fixed? I understand it needs to be prioritized and scheduled, developed, released, etc. My only laptop is using this distro and unfortunately I can't stand this screen flickering. I can try another distro and come back when this is resolved. Would this bug only affect Ubuntu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: h
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
I've just faced this crash
UptoDate
me@nuc:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
Aug 10 16:14:47 nuc kernel: [12755.073641] detected buffer overflow in strcat
Aug 10 16:14:47 nuc kernel: [12755.073660] [ cut here ]
Aug 10 16:14:47 nuc kernel: [12755.073662] kernel BUG at
/build/linux-hwe-zHO4ZF/linux-hwe-5.0.0/lib/string.c:1073!
Aug 10 16:14:47 nuc kernel: [12755.073669] invalid opcode: [#1] SMP PTI
Aug 10 16:14:47 nuc kernel: [12755.073673] CPU: 1 PID: 3135 Comm: deluged Not
tainted 5.0.0-23-generic #24~18.04.1-Ubuntu
Aug 10 16:14:47 nuc kernel: [12755.073675] Hardware name: /D54250WYK, BIOS
WYLPT10H.86A.0047.2018.0303.1725 03/03/2018
Aug 10 16:14:47 nuc kernel: [12755.073682] RIP: 0010:fortify_panic+0x13/0x22
Aug 10 16:14:47 nuc kernel: [12755.073685] Code: 4c 89 e2 e8 b1 98 00 00 42 c6
04 20 00 48 89 d8 5b 41 5c 5d c3 0f 0b 55 48 89 fe 48 c7 c7 20 38 fb 86 48 89
e5 e8 72 5c 6e ff <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 55 31 c9 48 89
fa 48
Aug 10 16:14:47 nuc kernel: [12755.073687] RSP: :b17381e779e0 EFLAGS:
00010282
Aug 10 16:14:47 nuc kernel: [12755.073690] RAX: 0022 RBX:
RCX:
Aug 10 16:14:47 nuc kernel: [12755.073692] RDX: RSI:
973e5b896448 RDI: 973e5b896448
Aug 10 16:14:47 nuc kernel: [12755.073694] RBP: b17381e779e0 R08:
033e R09: 8776f698
Aug 10 16:14:47 nuc kernel: [12755.073696] R10: b17381e77a90 R11:
b17381e77850 R12: 973dd6d15db0
Aug 10 16:14:47 nuc kernel: [12755.073698] R13: d33f5410 R14:
R15: 973dd0dac200
Aug 10 16:14:47 nuc kernel: [12755.073701] FS: 7ff3b0fd1700()
GS:973e5b88() knlGS:
Aug 10 16:14:47 nuc kernel: [12755.073703] CS: 0010 DS: ES: CR0:
80050033
Aug 10 16:14:47 nuc kernel: [12755.073705] CR2: 7ff3ad44f000 CR3:
00011abf0003 CR4: 001606e0
Aug 10 16:14:47 nuc kernel: [12755.073707] Call Trace:
Aug 10 16:14:47 nuc kernel: [12755.073746] smb21_set_oplock_level+0x147/0x1a0
[cifs]
Aug 10 16:14:47 nuc kernel: [12755.073778] smb3_set_oplock_level+0x22/0x90
[cifs]
Aug 10 16:14:47 nuc kernel: [12755.073807] smb2_set_fid+0x76/0xb0 [cifs]
Aug 10 16:14:47 nuc kernel: [12755.073834] cifs_new_fileinfo+0x259/0x390 [cifs]
Aug 10 16:14:47 nuc kernel: [12755.073862] ? smb2_close_file+0x20/0x20 [cifs]
Aug 10 16:14:47 nuc kernel: [12755.073887] ? cifs_new_fileinfo+0x259/0x390
[cifs]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
detected buffer overflow in strcat
kernel BUG at <...>/lib/string.c:1052!
invalid opcode: [#1] SMP PTI
RIP: 0010:fortify_panic+0x13/0x1f
Call Trace:
smb21_set_oplock_level+0xde/0x190 [cifs]
smb3_set_oplock_level+0x22/0x90 [cifs]
smb2_set_fid+0x76/0xb0 [cifs]
cifs_new_fileinfo+0x268/0x3c0 [cifs]
? smb2_get_lease_key+0x40/0x40 [cifs]
? cifs_new_fileinfo+0x268/0x3c0 [cifs]
cifs_open+0x57c/0x8d0 [cifs]
do_dentry_open+0x1fe/0x320
[...]
* By analyzing the code of smb21_set_oplock_level(), we've noticed the
only way fortify function strcat() would get overflow was if the value
of cinode->oplock got corrupted in a another thread leading to a
buffer write bigger then buffer size. In this function, the 'message'
buffer writes are governed by cinode->oplock, so only a different
thread cleaning the oplock value would lead to 'message' overflow.
* By the same time we worked this analysis, a fix was proposed
upstream for this issue in the form of commit 6a54b2e002c9 ("cifs:
fix strcat buffer overflow and reduce raciness in
smb21_set_oplock_level()"), by the same reporter of this LP. The fix
is simple and directly addresses this problem, so we hereby request
its SRU into Bionic kernel - it's already present in linux stable
branches.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noti
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
But according to logs of #5 and #16, the driver works fine. card 0: Audio [Intel HDMI/DP LPE Audio] card 1: bytchtes8316 [bytcht-es8316] 2 card(s) available. index: 0 name: index: 1 name: driver: I think the problem is the UCM and pulseaudio. I don't know why your pulseaudio can't generate the /tmp/a.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831945] Re: HDMI/DP audio: ELD not updated on hotplug event
Thanks Daniel, If you reproduce the problem on some machines, please tell us, then we can find that machine and try to reproduce this problem. So far, we can't reproduce this problem on all LENOVO I+N machines which we have. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831945 Title: HDMI/DP audio: ELD not updated on hotplug event Status in linux package in Ubuntu: Confirmed Bug description: When using HDMI or Displayport audio, the EDID-like Data (ELD) fails to update properly when hotplugging or hot-unplugging displays. This in turn prevents tools like the GNOME sound settings control panel from accurately presenting the system's current audio capabilities. How reproducible: Hot plug and hot unplug an audio-capable display and observe the state of the ELDs, either by directly reading the ELD files in /proc/asound/card*/eld* or by examining the available audio output devices in the GNOME sound settings control panel. Steps to Reproduce: 1. Log into a desktop session with no audio-capable displays plugged in 2. Plug in an audio-capable display 3. Open the GNOME sound settings control panel Actual results: The audio-capable display is not selectable as an output device. Expected results: The audio-capable display should be selectable as an output device. Additional info: This bug has been fixed upstream with commit 37a3a98ef601f89100e3bb657fb0e190b857028c. Applying this change alone to the bionic 4.18 HWE kernel is sufficient to allow the expected behavior to occur. It is likely to be sufficient to fix the same bug, assuming it exists, in Cosmic, but neither the presence of the bug nor the sufficiency of the patch were tested. The bug is likely not present in Disco, but this was not tested. This behavior was observed on a system with an NVIDIA GPU running the NVIDIA proprietary driver. The particular NVIDIA GPU on the system is not currently compatible with Nouveau. It is possible and likely that this problem is also reproducible on other systems which do have GPUs that are compatible with Nouveau, and even on systems with HDMI or Displayport connectors being driven by non-NVIDIA GPUs. When the ELD fails to update in response to a hotplug event, an update can be forced by accessing the underlying ALSA codec directly. For example, playing an audio stream directly via ALSA or even just reading from the /proc/asound/cardX/codec#Y file will cause the ELD to become updated. This is of course unnecessary if the patch which fixes the issue is applied, but it does offer a somewhat simple workaround for affected users until the patch can be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
It is not resolved for me in 5.3.* Linux thinkpad 5.3.0-050300rc2-generic #201907281631 SMP Sun Jul 28 20:34:00 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Only thing that seems to work for me is this: modprobe iwlwifi 11n_disable=1 bt_coex_active=0 Otherwise, machine locks up, I check dmesg and has the microcode errors for iwlwifi. Further, firmware also crashes with version 43 as well. Is this the same bug, should I open a separate ticket? [10422.844956] [ cut here ] [10422.845044] WARNING: CPU: 3 PID: 831 at drivers/net/wireless/intel/iwlwifi/mvm/../iwl-trans.h:1201 iwl_mvm_dump_lmac_error_log.cold+0xc/0x13 [iwlmvm] [10422.845048] Modules linked in: veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter overlay rfcomm xt_CHECKSUM iptable_mangle xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ccm bnep binfmt_misc nls_iso8859_1 uvcvideo edac_mce_amd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 kvm_amd ccp videobuf2_common kvm irqbypass snd_seq_midi videodev btusb snd_seq_midi_event mc btrtl btbcm iwlmvm btintel snd_hda_codec_conexant input_leds snd_hda_codec_generic bluetooth mac80211 snd_hda_codec_hdmi joydev snd_hda_intel thinkpad_acpi serio_raw wmi_bmof ecdh_generic snd_rawmidi nvram libarc4 ecc snd_hda_codec k10temp ledtrig_audio snd_hda_core iwlwifi snd_hwdep snd_seq snd_pcm snd_seq_device snd_timer cfg80211 snd ucsi_acpi typec_ucsi typec [10422.845103] soundcore mac_hid sch_fq_codel parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel amdgpu aes_x86_64 crypto_simd cryptd glue_helper amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse nvme fb_sys_fops sdhci_pci ahci cqhci r8169 i2c_piix4 libahci drm sdhci realtek nvme_core wmi video i2c_scmi [10422.845140] CPU: 3 PID: 831 Comm: irq/77-iwlwifi: Tainted: GW 5.3.0-050300rc2-generic #201907281631 [10422.845141] Hardware name: LENOVO 20KVCTO1WW/20KVCTO1WW, BIOS R0UET73W (1.53 ) 06/14/2019 [10422.845156] RIP: 0010:iwl_mvm_dump_lmac_error_log.cold+0xc/0x13 [iwlmvm] [10422.845159] Code: 13 04 b6 d2 0f 0b e9 40 1d fd ff 48 c7 c7 08 67 db c0 e8 00 04 b6 d2 0f 0b e9 ee 1d fd ff 48 c7 c7 f0 69 db c0 e8 ed 03 b6 d2 <0f> 0b e9 2e 27 fd ff 48 c7 c7 f0 69 db c0 e8 da 03 b6 d2 0f 0b 41 [10422.845161] RSP: 0018:bccf01697d10 EFLAGS: 00010246 [10422.845164] RAX: 0024 RBX: 9a07aa801e28 RCX: [10422.845165] RDX: RSI: 9a07ff0d7448 RDI: 9a07ff0d7448 [10422.845166] RBP: bccf01697dd0 R08: 9a07ff0d7448 R09: 0004 [10422.845168] R10: R11: 0001 R12: 0080dccc [10422.845169] R13: 9a07f2090018 R14: R15: 9a07f2099138 [10422.845171] FS: () GS:9a07ff0c() knlGS: [10422.845172] CS: 0010 DS: ES: CR0: 80050033 [10422.845174] CR2: 1820b049c018 CR3: 00022886c000 CR4: 003406e0 [10422.845175] Call Trace: [10422.845188] ? __dev_printk+0x5c/0x6f [10422.845191] ? _dev_err+0x6c/0x83 [10422.845197] ? stop_one_cpu+0x73/0xa0 [10422.845210] iwl_mvm_dump_nic_error_log+0x20/0x70 [iwlmvm] [10422.845221] iwl_mvm_nic_error+0x35/0x40 [iwlmvm] [10422.845232] iwl_pcie_irq_handle_error+0xb1/0x110 [iwlwifi] [10422.845243] iwl_pcie_irq_msix_handler+0x197/0x4b0 [iwlwifi] [10422.845249] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [10422.845251] irq_thread_fn+0x28/0x60 [10422.845253] irq_thread+0xda/0x170 [10422.845256] ? irq_forced_thread_fn+0x80/0x80 [10422.845260] kthread+0x104/0x140 [10422.845263] ? irq_thread_check_affinity+0xf0/0xf0 [10422.845265] ? kthread_park+0x80/0x80 [10422.845271] ret_from_fork+0x22/0x40 [10422.845274] ---[ end trace 403310f7f83d2261 ]--- [10422.845280] iwlwifi :04:00.0: HW error, resetting before reading [10422.852409] iwlwifi :04:00.0: Start IWL Error Log Dump: [10422.852418] iwlwifi :04:00.0: Status: 0x0080, count: 1870036983 [10422.852421] iwlwifi :04:00.0: Loaded firmware version: 43.95eb4e97.0 [10422.852424] iwlwifi :04:00.0: 0x06620275 | ADVANCED_SYSASSERT [10422.852425] iwlwifi :04:00.0: 0xF3F7F6FB | trm_hw_status0 [10422.852427] iwlwifi :04:00.0: 0x91448074 | trm_hw_status1 [10422.852428] iwlwifi :04:00.0: 0xF1FBFBFB | branchlink2 [10422.852430] iwlwifi :04:00.0: 0x0F050020 | interruptlink1 [10422.852431] iwlwifi :04:00.0: 0x95EC3F94 | interruptlink2 [10422.852433] iwlwifi :04:00.0: 0x15C59088 | data1 [10422.852434] iwlwifi :04:00.0: 0xEF64A397 | data2 [10422.852435] iwlwifi :04:00.0: 0xC7982780 | data3 [104
[Kernel-packages] [Bug 1839707] Re: System does not shutdown with any kernel >= v4.6.3
** Summary changed: - System does not shutdown since upgrade from 16.04LTS + System does not shutdown with any kernel >= v4.6.3 ** Description changed: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. + + In addition I should mention I have tried many workarounds suggested on forums and in IRC. + This includes but not confined to running with:- noapic nolapic and both Windows and Linux acpi_osi ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: - linux-restricted-modules-5.0.0-21-generic N/A - linux-backports-modules-5.0.0-21-generic N/A - linux-firmware1.178.3 + linux-restricted-modules-5.0.0-21-generic N/A + linux-backports-modules-5.0.0-21-generic N/A + linux-firmware1.178.3 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839707 Title: System does not shutdown with any kernel >= v4.6.3 Status in linux package in Ubuntu: Confirmed Bug description: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. In addition I should mention I have tried many workarounds suggested on forums and in IRC. This includes but not confined to running with:- noapic nolapic and both Windows and Linux acpi_osi ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specifie
[Kernel-packages] [Bug 1839707] 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/1839707 Title: System does not shutdown since upgrade from 16.04LTS Status in linux package in Ubuntu: Confirmed Bug description: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838993] Re: Suspend immediately resumes on Ubuntu 18.04.2
update: i had some time and did a fresh installation of Xubuntu 18.04.3 on an USB SSD. Suspend works with Kernel 5.0, first i suspected the nvidia driver but it still works after installation of the nvidia drivers. So for me it is either a setting which i'm not aware of that is different or the main difference between these 2 installation: my Laptop runs zfs root, the USB installation is simple ext4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838993 Title: Suspend immediately resumes on Ubuntu 18.04.2 Status in linux package in Ubuntu: Confirmed Bug description: Recently my Lenovo ThinkPad W540 laptop has been unable to suspend correctly. It immediately wakes up after going through all the usual steps of turning off the screens, USB devices etc. I'm using the UI to suspend by left-clicking and holding the power off button until it turns into a pause button, and then I left-click that button. The laptop is docked with two monitors connected and the lid is open (although the laptop screen is not used) when I attempt to suspend it. This used to work until recently. BIOS has not been touched or upgraded. Log excerpt: ... Aug 5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156787] PM: suspend entry (deep) Aug 5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156789] PM: Syncing filesystems ... done. Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.015094] rfkill: input handler enabled Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.320163] Freezing user space processes ... (elapsed 0.003 seconds) done. Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] OOM killer disabled. Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.325130] Suspending console(s) (use no_console_suspend to debug) Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469224] sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469297] sd 5:0:0:0: [sdb] Synchronizing SCSI cache Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469449] sd 5:0:0:0: [sdb] Stopping disk Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.470686] sd 0:0:0:0: [sda] Stopping disk Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.669512] e1000e: EEE TX LPI TIMER: 0011 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24054.969605] ACPI: EC: interrupt blocked Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.009441] ACPI: Preparing to enter system sleep state S3 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013106] ACPI: EC: event blocked Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] ACPI: EC: EC stopped Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] PM: Saving platform NVS memory Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013124] Disabling non-boot CPUs ... Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.029590] IRQ 30: no longer affine to CPU1 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.030620] smpboot: CPU 1 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.054769] smpboot: CPU 2 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077811] IRQ 16: no longer affine to CPU3 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077819] IRQ 29: no longer affine to CPU3 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.078828] smpboot: CPU 3 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.102970] smpboot: CPU 4 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125889] IRQ 23: no longer affine to CPU5 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125901] IRQ 32: no longer affine to CPU5 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.126914] smpboot: CPU 5 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.154299] IRQ 27: no longer affine to CPU6 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.155323] smpboot: CPU 6 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.181669] IRQ 26: no longer affine to CPU7 Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.182697] smpboot: CPU 7 is now offline Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186538] ACPI: Low-level resume complete Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186589] ACPI: EC: EC started Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186590] PM: Restoring platform NVS memory Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189175] Enabling non-boot CPUs ... Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189259] x86: Booting SMP configuration: Aug 5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189260] smpboot: Booting Node 0 Processor 1 APIC 0x1 Aug 5 16:53:23 tais
[Kernel-packages] [Bug 1839707] [NEW] System does not shutdown since upgrade from 16.04LTS
Public bug reported: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839707 Title: System does not shutdown since upgrade from 16.04LTS Status in linux package in Ubuntu: New Bug description: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
