[Kernel-packages] [Bug 1701247] [NEW] package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1701135 *** https://bugs.launchpad.net/bugs/1701135 Public bug reported: issues started from failed install of google-earth- stable_current_amd64.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mick 1887 F pulseaudio /dev/snd/controlC0: mick 1887 F pulseaudio Date: Thu Jun 29 20:29:10 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8cd168e8-560f-45d6-9891-4b84d75bea51 InstallationDate: Installed on 2016-06-20 (373 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer Inc. K53TK ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=87c1650a-7ab7-486f-8fe6-9608bd989fc6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TK dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr205:bd02/15/2012:svnASUSTeKComputerInc.:pnK53TK:pvr1.0:rvnASUSTeKComputerInc.:rnK53TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701247 Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: issues started from failed install of google-earth- stable_current_amd64.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mick 1887 F pulseaudio /dev/snd/controlC0: mick 1887 F pulseaudio Date: Thu Jun 29 20:29:10 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=8cd168e8-560f-45d6-9891-4b84d75bea51 InstallationDate: Installed on 2016-06-20 (373 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer Inc. K53TK ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=87c1650a-7ab7-486f-8fe6-9608bd989fc6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53TK dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr205:bd02/15/2012:svnASUSTeKComputerInc.:pnK53TK:pvr1.0:rvnASUSTeKComputerInc.:rnK53TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53TK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to
[Kernel-packages] [Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
Update to my previous comment - I've extensively tested different configurations (mostly kernel parameters) on my Legion 5 15ach6. I did manage to get the brightness to change when using just the dedicated GPU (selected as such within the BIOS,) using the parameter nvidia.NVreg_RegistryDwords=EnableBrightnessControl=1 and this causes the nvidia gpu to show up in /sys/class/backlight/ alongside the amd one, but both of the /sys/class/backlight/*/brightness files do nothing. In hybrid mode and in integrated only mode (using optimus-manager to do it) acpi_backlight=video/vendor/native/none all do nothing, i tested each individually with amdgpu.backlight=1 and amdgpu.backlight=0, and did not get any hint of a way to control backlight, only the AMD iGPU showed up in /sys/class/backlight/, and changing the brightness value did nothing. Something else of note was that I noticed that when using just the dedicated NVIDIA card, xrandr showed DP-1 as the active montior, while when I was using the AMD iGPU, it was showing as eDP. Does anyone know if the MUX switch needs something from the kernel or nvidia driver to work properly? Is there any way for us to be able to check the position of the switch? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD Status in linux package in Ubuntu: Confirmed Bug description: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : h
[Kernel-packages] [Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
** Also affects: linux (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD
Hey, look what I found! https://gitlab.freedesktop.org/drm/amd/-/issues/1671 there is also https://gitlab.freedesktop.org/drm/amd/-/issues/1438 which is the bug report for the previous legion laptops, that one seems to center around the 4000 series APUs, whereas this time it's centered around the 5000 series. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1671 https://gitlab.freedesktop.org/drm/amd/-/issues/1671 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1438 https://gitlab.freedesktop.org/drm/amd/-/issues/1438 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944094] Re: Can't adjust screen backlight on Legion Slim 7 AMD
This seems to also effect the Legion 5 15ach6 (AMD) There are two versions of the legion 5, the 2020 version and the 2021 version. It seems that this issue is fixed on the 2020 version by adding the kernel parameter amdgpu.backlight=0 but I can confirm that this does not fix the issue on the 2021 version, so its likely that the 2021 laptop is suffering from whatever this issue is. I'm guessing that the MUX switch is involved in one way or another, as it means that the NVIDIA dGPU does not have to pass frames through the AMD iGPU, it connects to the display separately, and I'm not sure which GPU actually has control over the brightness control. I wonder if the brightness isn't tied to either GPU, maybe its a separate system entirely? ** Summary changed: - Can't adjust screen backlight on Legion Slim 7 AMD + Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD Status in linux package in Ubuntu: Confirmed Bug description: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451085] Re: Ivy Bridge laptop overheats with intel_pstate enabled
I (still) don't have Windows and the BIOS update is (still) Windows only. If I had it, I'd do it. I don't even have a restore disk because Samsung don't provide one. I'd have to buy a copy of Windows from them ($30 admin fee IIRC) to go through the BIOS update process. Suggesting that I buy the competitors product feels counter-productive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451085 Title: Ivy Bridge laptop overheats with intel_pstate enabled Status in linux package in Ubuntu: Incomplete Bug description: Running 'cpupower frequency-info' shows all my cores running at 2.8GHz constantly, despite being mostly idle. My laptop was using the intel_pstate module for CPU frequency governing. I tried switching between powersave and performance governors but they both showed the same issue. WORKAROUND: Add intel_pstate=disabled to my kernel command line. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1646 F pulseaudio CurrentDesktop: Unity Date: Sat May 2 13:26:14 2015 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (948 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) Lsusb: Bus 003 Device 004: ID 2232:1024 Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=disable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (8 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484919] [NEW] Kernel oops associated with BIRD/netlink
Public bug reported: Scale testing our product, which uses the BIRD BGP daemon, on Google's GCE cloud, we see frequent (40% of hosts) Kernel Oopses and reboots on kernel 3.19.0-25-generic #26~14.04.1-Ubuntu with BIRD running. This is the standard GCE-provided Ubuntu image. If we replace the image with a stock Ubuntu one (kernel 3.13.0-61-generic #100-Ubuntu), installed from ISO, then we do not see the issue. If we stop BIRD then we no longer see the issue. I suspect that this is an issue with the way BIRD is using netlink, triggering a kernel bug. It seems to happen more at scale, when BIRD is doing more with netlink and we have thousands of routes in place. Here's a sample kernel oops: [ 266.033276] BUG: unable to handle kernel paging request at 0019003c [ 266.035142] IP: [] __kmalloc_node_track_caller+0xfb/0x2c0 [ 266.036009] PGD b9e5e067 PUD 0 [ 266.036009] Oops: [#1] SMP [ 266.036009] Modules linked in: bridge stp llc dummy xt_mac xt_mark nf_conntrack_ipv6 nf_defrag_ipv6 xt_comment xt_set ip_set_hash_ip ip_set nfnetlink ebtable_nat ebtables xt_nat ipip tunnel4 ip_tunnel ipt_REJECT nf_reject_ipv4 xt_conntrack xt_CHECKSUM xt_tcpudp iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip6table_filter ip6_tables iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt ppdev dm_multipath scsi_dh 8250_fintek parport_pc i2c_piix4 mac_hid serio_raw parport crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi [ 266.036009] CPU: 2 PID: 3456 Comm: bird Tainted: G C 3.19.0-25-generic #26~14.04.1-Ubuntu [ 266.036009] Hardware name: Google Google, BIOS Google 01/01/2011 [ 266.036009] task: 8801210775c0 ti: 880036a08000 task.ti: 880036a08000 [ 266.036009] RIP: 0010:[] [] __kmalloc_node_track_caller+0xfb/0x2c0 [ 266.036009] RSP: 0018:880036a0b7f8 EFLAGS: 00010246 [ 266.036009] RAX: RBX: 000102d0 RCX: 0008b0f6 [ 266.036009] RDX: 0008b0f5 RSI: RDI: 000171c0 [ 266.036009] RBP: 880036a0b848 R08: 8801263171c0 R09: 880121c01600 [ 266.036009] R10: R11: 880121c01600 R12: 000102d0 [ 266.036009] R13: 0180 R14: R15: 0019003c [ 266.036009] FS: 7fd470753740() GS:88012630() knlGS: [ 266.036009] CS: 0010 DS: ES: CR0: 80050033 [ 266.036009] CR2: 0019003c CR3: bb207000 CR4: 001406e0 [ 266.036009] Stack: [ 266.036009] 00010180 00c3 880121c01600 816992ea [ 266.036009] 0001 8800b1486a00 00d0 [ 266.036009] 0180 880036a0b898 81697261 [ 266.036009] Call Trace: [ 266.036009] [] ? pskb_expand_head+0x6a/0x260 [ 266.036009] [] __kmalloc_reserve.isra.27+0x31/0x90 [ 266.036009] [] pskb_expand_head+0x6a/0x260 [ 266.036009] [] netlink_trim+0xa3/0xe0 [ 266.036009] [] netlink_unicast+0x3e/0x200 [ 266.036009] [] nlmsg_notify+0x93/0xb0 [ 266.036009] [] rtnl_notify+0x2e/0x40 [ 266.036009] [] rtmsg_fib+0x115/0x160 [ 266.036009] [] ? trie_rebalance+0x10d/0x130 [ 266.036009] [] fib_table_insert+0x1da/0x8e0 [ 266.036009] [] inet_rtm_newroute+0x48/0x60 [ 266.036009] [] rtnetlink_rcv_msg+0x95/0x250 [ 266.036009] [] ? rhashtable_lookup_compare+0x36/0x70 [ 266.036009] [] ? __netlink_lookup+0x3e/0x50 [ 266.036009] [] ? rtnetlink_rcv+0x40/0x40 [ 266.036009] [] netlink_rcv_skb+0xc1/0xe0 [ 266.036009] [] rtnetlink_rcv+0x2c/0x40 [ 266.036009] [] netlink_unicast+0xf6/0x200 [ 266.036009] [] netlink_sendmsg+0x30c/0x680 [ 266.036009] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 266.036009] [] do_sock_sendmsg+0x8c/0x100 [ 266.036009] [] ? __fdget+0x13/0x20 [ 266.036009] [] SYSC_sendto+0x157/0x200 [ 266.036009] [] ? __sys_recvmsg+0x42/0x80 [ 266.036009] [] SyS_sendto+0xe/0x10 [ 266.036009] [] system_call_fastpath+0x16/0x1b [ 266.036009] Code: fb 41 8b 53 18 0f 1f 44 00 00 48 83 c4 28 48 89 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 40 00 49 63 41 20 48 8d 4a 01 49 8b 39 <49> 8b 1c 07 4c 89 f8 65 48 0f c7 0f 0f 94 c0 84 c0 0f 84 53 ff [ 266.036009] RIP [] __kmalloc_node_track_caller+0xfb/0x2c0 [ 266.036009] RSP [ 266.036009] CR2: 0019003c [ 266.131166] ---[ end trace 246ae06038901786 ]--- Running our product on CoreOS, we see similar, but less frequent crashes. Their kernel is 4.1-based: https://github.com/coreos/bugs/issues/435 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta
[Kernel-packages] [Bug 1451085] [NEW] Ivy Bridge laptop overheats with intel_pstate enabled
Public bug reported: Noticed my laptop getting hot over the last month or so. Investigating, I ran 'cpupower frequency-info' and found that all my cores were running at 2.8GHz pretty-much constantly despite being mostly idle. My laptop was using the intel_pstate module for CPU frequency governing. I tried switching between powersave and performance governors but they both showed the same issue. Adding intel_pstate=disabled to my kernel command line switched over to using the acpi-cpufreq module and the ondemand governor. With that enabled, my CPU is back down to 800MHz-1.1GHz at idle, as expected and it immediately stopped overheating. Bug 1188647 covered disabling intel_pstate a while ago while it was considered buggy but now it's enabled again, it seems to be causing problems for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1646 F pulseaudio CurrentDesktop: Unity Date: Sat May 2 13:26:14 2015 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (948 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) Lsusb: Bus 003 Device 004: ID 2232:1024 Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=disable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (8 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451085 Title: Ivy Bridge laptop overheats with intel_pstate enabled Status in linux package in Ubuntu: New Bug description: Noticed my laptop getting hot over the last month or so. Investigating, I ran 'cpupower frequency-info' and found that all my cores were running at 2.8GHz pretty-much constantly despite being mostly idle. My laptop was using the intel_pstate module for CPU frequency governing. I tried switching between powersave and performance governors but they both showed the same issue. Adding intel_pstate=disabled to my kernel command line switched over to using the acpi-cpufreq module and the ondemand governor. With that enabled, my CPU is back down to 800MHz-1.1GHz at idle, as expected and it immediately stopped overheating. Bug 1188647 covered disabling intel_pstate a while ago while it was considered buggy but now it's enabled again, it seems to be causing problems for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1646 F pulseaudio CurrentDesktop: Unity Date: Sat May 2 13:26:14 2015 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (948 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) Lsusb: Bus 003 Device 004: ID 2232:1024 Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundatio
[Kernel-packages] [Bug 1451085] Re: Ivy Bridge laptop overheats with intel_pstate enabled
It's the Samsung NP900X4C-A03US -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451085 Title: Ivy Bridge laptop overheats with intel_pstate enabled Status in linux package in Ubuntu: Incomplete Bug description: Running 'cpupower frequency-info' shows all my cores running at 2.8GHz constantly, despite being mostly idle. My laptop was using the intel_pstate module for CPU frequency governing. I tried switching between powersave and performance governors but they both showed the same issue. WORKAROUND: Add intel_pstate=disabled to my kernel command line. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1646 F pulseaudio CurrentDesktop: Unity Date: Sat May 2 13:26:14 2015 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (948 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) Lsusb: Bus 003 Device 004: ID 2232:1024 Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=disable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-24 (8 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1614618] Re: hv-fcopy-daemon.service system failed start
I am seeing this as well in a Hyper-V 2012R2 environment, but with more reasonable boot times. $ systemd-analyze Startup finished in 14.479s (kernel) + 3.101s (userspace) = 17.580s $ cat /proc/version Linux version 4.4.0-36-generic (buildd@lcy01-01) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 $ systemctl status hv-fcopy-daemon.service --no-pager --full ● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2016-08-30 15:51:41 PDT; 32min ago Process: 3105 ExecStart=/usr/sbin/hv_fcopy_daemon -n (code=exited, status=1/FAILURE) Main PID: 3105 (code=exited, status=1/FAILURE) Aug 30 15:51:41 xenial01 systemd[1]: Started Hyper-V File Copy Protocol Daemon. Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. $ sudo grep -E -i "hv.fcopy" /var/log/syslog Aug 30 15:51:41 xenial01 HV_FCOPY: starting; pid is:3105 Aug 30 15:51:41 xenial01 HV_FCOPY: open /dev/vmbus/hv_fcopy failed; error: 2 No such file or directory Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. Aug 30 15:51:41 xenial01 systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1614618 Title: hv-fcopy-daemon.service system failed start Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: I booted a yakkety system on azure, and saw $ systemctl status hv-fcopy-daemon.service --no-pager --full ● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2016-08-18 16:01:51 UTC; 32min ago Main PID: 2291 (code=exited, status=1/FAILURE) Aug 18 16:01:51 ubuntu systemd[1]: Started Hyper-V File Copy Protocol Daemon. Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. Aug 18 16:01:51 ubuntu systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. Also, random information but surprising none the less: $ systemd-analyze Startup finished in 5min 14.289s (kernel) + 1min 43.164s (userspace) = 6min 57.454s $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @1min 43.124s └─multi-user.target @1min 43.124s └─ephemeral-disk-warning.service @1min 42.888s +235ms └─cloud-final.service @1min 39.480s +3.407s └─cloud-config.service @1min 2.517s +36.961s └─network-online.target @1min 2.464s └─cloud-init.service @35.453s +26.967s └─networking.service @32.799s +2.622s └─network-pre.target @32.766s └─cloud-init-local.service @12.044s +20.690s └─local-fs.target @12.030s └─mnt.mount @1min 29.655s └─dev-sdb1.device @1min 8.310s ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-cloud-tools-common 4.4.0-34.53 ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 18 16:01 seq crw-rw 1 root audio 116, 33 Aug 18 16:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 18 16:31:54 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=314ea127-227e-4b64-b5b4-d70ab0fb7eb7 ro console=tty1 console=t
[Kernel-packages] [Bug 1738534] [NEW] Processor turbo dsiabled/throttled after suspend
Public bug reported: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c1185 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:
[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
Just tried another scenario. If I do the full power cycle while on battery power, then it boots up with turbo disabled and frequency locked. This command then seems to work (cpupower then reports turbo is active/supported): sudo x86_energy_perf_policy --turbo-enable 1 But this command has no effect: sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz (Where, int he previous scenario, it did work.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo dsiabled/throttled after suspend Status in linux package in Ubuntu: New Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_
[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
As a workaround, I created a post-resume script that runs the above commands at /lib/systemd/system-sleep/throttle-workaround. It works in the first scenario, but not if the full power cycle was done on battery power. #!/bin/sh # Action script to prevent CPU throttling after resume. set -e PATH=/sbin:/usr/sbin:/bin:/usr/bin case "${1}" in post) x86_energy_perf_policy --turbo-enable 1 cpufreq-set -r --max=3.0GHz ;; esac -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo dsiabled/throttled after suspend Status in linux package in Ubuntu: Confirmed Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SA
[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend
It may have been as early as the upgrade to 16.04. I remember having some performance/overheating issues at that time so I disabled intel_pstate for a while; but I never fully diagnosed the issue. The 17.10 install was a fresh install though, I wiped the system. I'll try the new kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738534 Title: Processor turbo dsiabled/throttled after suspend Status in linux package in Ubuntu: Incomplete Bug description: After suspending/resuming my laptop on battery power, I noticed choppy video playback. I've narrowed it down to the CPU being locked to lower frequencies after suspend/resume (only on battery). Plugging the laptop back in does not restore the normal performance, nor does suspend/resume after plugging it back in. The performance doesn't drop until after the suspend/resume, I'm not sure if it is _supposed_ to throttle when on battery, but either way the behaviour is wrong. Doing a full shutdown and restart restores the performance to normal. Prior to a suspend/resume cycle, cpupower reports: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.26 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has no effect) and turbo is disabled: $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 1.80 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 950 MHz (asserted by call to kernel) boost state support: Supported: no Active: no 2800 MHz max turbo 4 active cores 2800 MHz max turbo 3 active cores 2800 MHz max turbo 2 active cores 3000 MHz max turbo 1 active cores Trying to re-enable turbo mode by setting the no_turbo intel_pstate /sys/ entry back to 0 is rejected: $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo 0 tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted However, these two commands *do* work around the problem, forcing turbo mode back on and then restoring the normal frequency range: sudo x86_energy_perf_policy --turbo-enable 1 sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz I also see this error in dmesg after some resumes (but the above problem sometimes happens without this error message): Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by BIOS or unavailable on processor ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 16 11:18:12 2017 InstallationDate: Installed on 2017-12-14 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 001 Device 004: ID 2232:1024 Silicon Motion Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-19-generic root=UUID=7352de8c-0017-44e1-81fb-0145ad9c118
[Kernel-packages] [Bug 1745282] Re: Freezes XPS 13
Confirmed that 4.15.0-041500-lowlatency fixes the problem on an XPS 13 9360. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745282 Title: Freezes XPS 13 Status in linux package in Ubuntu: Incomplete Bug description: This kernel boots on the XPS 13 but in less than a minute it hard freezes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahron 2235 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 24 22:41:26 2018 InstallationDate: Installed on 2018-01-04 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.name: 0PVG6D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1643165] Re: Wifi drops out regularly after upgrade to 16.04
Running 4.9.0-040900rc6, just had a drop out. Noticed that dmesg had this output: First this line, which seemed to coincide with the dropout: [ 3627.072802] wlan0: AP 00:07:26:aa:e0:45 changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz) Then, after a minute, this and it came back: [ 3707.386740] wlan0: authenticate with 00:07:26:aa:e0:45 [ 3707.394906] wlan0: send auth to 00:07:26:aa:e0:45 (try 1/3) [ 3707.397243] wlan0: authenticated [ 3707.397828] wlan0: associate with 00:07:26:aa:e0:45 (try 1/3) [ 3707.406078] wlan0: RX AssocResp from 00:07:26:aa:e0:45 (capab=0x431 status=0 aid=1) [ 3707.413670] wlan0: associated [ 3707.447412] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 00:07:26:aa:e0:45 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643165 Title: Wifi drops out regularly after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll drop out for 20s every few minutes then come back. network manager still thinks that it is connected, but websites will fail to load/time out. Reconnecting to the AP (by clicking on it in network-manager) seems to re-establish the connection. I typically sit 6ft from the access point so the signal is strong and much stronger than any nearby APs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 2212 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 19 10:39:23 2016 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1654754] [NEW] Wifi stopped working; ath10k_pci firmware crash in dmesg log
Public bug reported: Wifi worked fine for a while then stopped working. dmesg log has a correlated firmware crash for the Wifi adapter's driver. Disabling and reenabling Wifi in the network manager widget seemed to make it work for a while again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.161.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 7 15:42:55 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-20 (18 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to yakkety on 2017-01-03 (3 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log Status in linux-firmware package in Ubuntu: New Bug description: Wifi worked fine for a while then stopped working. dmesg log has a correlated firmware crash for the Wifi adapter's driver. Disabling and reenabling Wifi in the network manager widget seemed to make it work for a while again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.161.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 7 15:42:55 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-20 (18 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to yakkety on 2017-01-03 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1654754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1654754] Re: Wifi stopped working; ath10k_pci firmware crash in dmesg log
Here's the dmesg crash report: [ 3683.563419] wlp58s0: AP 00:07:26:aa:e0:45 changed bandwidth, new config is 2472 MHz, width 2 (2462/0 MHz) [ 3708.293559] ath10k_pci :3a:00.0: failed to stop wmi scan: -11 [ 3708.293565] ath10k_pci :3a:00.0: failed to stop scan: -11 [ 3708.293568] ath10k_pci :3a:00.0: failed to start hw scan: -110 [ 3712.407418] ath10k_pci :3a:00.0: failed to start hw scan: -11 [ 3713.437730] ath10k_pci :3a:00.0: firmware crashed! (uuid f68629ee-b9ac-4afa-a8ab-78f9b8dbc58d) [ 3713.437757] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [ 3713.437764] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 3713.439421] ath10k_pci :3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 3713.440186] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 3713.440195] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 3713.442262] ath10k_pci :3a:00.0: firmware register dump: [ 3713.442273] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 0x009860FA 0x00955B31 [ 3713.442280] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 0x0004 0x0040E8A0 [ 3713.442287] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 0x000B 0x0040 [ 3713.442293] ath10k_pci :3a:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [ 3713.442299] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x0091080D 0x 0x0091080D [ 3713.442305] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x 0x0041E0DC [ 3713.442311] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 0xC09860FA [ 3713.442317] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 0x0018 0x004313B8 [ 3713.442323] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 0x00429548 [ 3713.442329] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x 0x0001 [ 3713.442335] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10 [ 3713.442341] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x0001 [ 3713.442351] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 0x0010 0x004041D0 [ 3713.442357] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 0x0040 0x [ 3713.442363] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 0x 0x00400600 [ 3713.442467] ath10k_pci :3a:00.0: failed to start hw scan: -108 [ 3713.525461] ieee80211 phy0: Hardware restart was requested [ 3715.944232] ath10k_pci :3a:00.0: device successfully recovered [ 3743.622083] wlp58s0: deauthenticated from 00:07:26:aa:e0:45 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA) [ 3743.664676] wlp58s0: authenticate with 00:07:26:aa:e0:45 [ 3743.706559] wlp58s0: send auth to 00:07:26:aa:e0:45 (try 1/3) [ 3743.708669] wlp58s0: authenticated [ 3743.715614] wlp58s0: associate with 00:07:26:aa:e0:45 (try 1/3) [ 3743.720081] wlp58s0: RX AssocResp from 00:07:26:aa:e0:45 (capab=0x431 status=0 aid=3) [ 3743.723689] wlp58s0: associated [ 3743.732696] ath: EEPROM regdomain: 0x833a [ 3743.732699] ath: EEPROM indicates we should expect a country code [ 3743.732702] ath: doing EEPROM country->regdmn map search [ 3743.732705] ath: country maps to regdmn code: 0x37 [ 3743.732707] ath: Country alpha2 being used: GB [ 3743.732709] ath: Regpair used: 0x37 [ 3743.732712] ath: regdomain 0x833a dynamically updated by country IE -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log Status in linux-firmware package in Ubuntu: New Bug description: Wifi worked fine for a while then stopped working. dmesg log has a correlated firmware crash for the Wifi adapter's driver. Disabling and reenabling Wifi in the network manager widget seemed to make it work for a while again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.161.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 7 15:42:55 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-20 (18 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to yakkety on 2017-01-03 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-
[Kernel-packages] [Bug 1654754] Re: Wifi stopped working; ath10k_pci firmware crash in dmesg log
Looks similar to Bug #1627474, not sure if trace is identical though -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1654754 Title: Wifi stopped working; ath10k_pci firmware crash in dmesg log Status in linux-firmware package in Ubuntu: New Bug description: Wifi worked fine for a while then stopped working. dmesg log has a correlated firmware crash for the Wifi adapter's driver. Disabling and reenabling Wifi in the network manager widget seemed to make it work for a while again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.161.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 7 15:42:55 2017 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-20 (18 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to yakkety on 2017-01-03 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1654754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1643165] [NEW] Wifi drops out regularly after upgrade to 16.04
Public bug reported: Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll drop out for 20s every few minutes then come back. network manager still thinks that it is connected, but websites will fail to load/time out. Reconnecting to the AP (by clicking on it in network-manager) seems to re-establish the connection. I typically sit 6ft from the access point so the signal is strong and much stronger than any nearby APs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 2212 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 19 10:39:23 2016 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643165 Title: Wifi drops out regularly after upgrade to 16.04 Status in linux package in Ubuntu: New Bug description: Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll drop out for 20s every few minutes then come back. network manager still thinks that it is connected, but websites will fail to load/time out. Reconnecting to the AP (by clicking on it in network-manager) seems to re-establish the connection. I typically sit 6ft from the access point so the signal is strong and much stronger than any nearby APs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 2212 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 19 10:39:23 2016 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG EL
[Kernel-packages] [Bug 1643165] Re: Wifi drops out regularly after upgrade to 16.04
Ah, after disabling 40MHz bands on my router, the problem seems to have gone away; seems the bug is triggered by the router switching between 20 and 40MHz. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643165 Title: Wifi drops out regularly after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll drop out for 20s every few minutes then come back. network manager still thinks that it is connected, but websites will fail to load/time out. Reconnecting to the AP (by clicking on it in network-manager) seems to re-establish the connection. I typically sit 6ft from the access point so the signal is strong and much stronger than any nearby APs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 2212 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 19 10:39:23 2016 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213172] Re: "You need to load the kernel first" when trying select any option from grub list when using EFI
*** This bug is a duplicate of bug 1213119 *** https://bugs.launchpad.net/bugs/1213119 ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213172 Title: "You need to load the kernel first" when trying select any option from grub list when using EFI Status in “linux” package in Ubuntu: Incomplete Bug description: will use url to add linux as affects to this bug report https://bugs.launchpad.net/ubiquity/+bug/1213119 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3446 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.331 Date: Fri Aug 16 17:26:40 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. GA-A75-UD4H MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8c dmi.board.name: GA-A75-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8c:bd12/07/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Re: [Dell XPS 13 L322X] Brightness control broken on Raring 13.04 after kernel upgrade
I've flashed the BIOS update via FreeDOS live cd and I'm currently on version A10, release date 08/28/2013. At first, it did not look as if it had done anything to fix the problem. Brightness control was still not working. However, I noticed a recent comment (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/954661/comments/108) that suggested changing the option of Load Legacy Option Rom to Enabled from the BIOS setup menu. I also removed all options from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub so it was an empty string. Now it appears that with kernel 3.8.0-33-generic I have brightness control working again. I'm not entirely sure if it was indeed the BIOS update or the /etc/default/grub + BIOS setup menu change that ended up correction the situation, but I'll see if I can pinpoint which one did the trick. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: [Dell XPS 13 L322X] Brightness control broken on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Incomplete Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1094534] Re: USB 3.0 ports don't work after suspend, xhci_hcd errors in kernel log
Sure, it's NP900X4C-A03US ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1094534 Title: USB 3.0 ports don't work after suspend, xhci_hcd errors in kernel log Status in “linux” package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: My laptop has one USB 2.0 port and a couple of USB 3.0 ports. The USB 3.0 ports only work after a fresh shutdown/restart, not after I suspend/resume. There are a couple of different USB controllers listed in lspci: $ sudo lspci -nn | grep USB 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) 03:00.0 USB controller [0c03]: Renesas Technology Corp. Device [1912:0015] (rev 02) lsusb lists a 3.0 root hub along wit the 2.0 one. $ sudo lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07da Intel Corp. Bus 001 Device 004: ID 2232:1024 I see the following errors in dmesg output (and nothing when I plug/unplug a device): $ dmesg | grep xhci [ 3916.808221] xhci_hcd :03:00.0: WARN: xHC restore state timeout [ 3916.808236] xhci_hcd :03:00.0: PCI post-resume error -110! [ 3916.808237] xhci_hcd :03:00.0: HC died; cleaning up [ 3916.808240] xhci_hcd :03:00.0: HC died; cleaning up ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1915 F pulseaudio Date: Sat Dec 29 11:54:48 2012 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (94 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-21-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/shaun not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1094534] Re: [Samsung NP900X4C-A03US] USB 3.0 ports don't work after suspend, xhci_hcd errors in kernel log
By the way, setting that USB wakeup setting in the BIOS seems to have some effect for me. The port no longer dies after suspend but instead it just doesn't work very well (random disconnections, file transfers from my digital camera fail). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1094534 Title: [Samsung NP900X4C-A03US] USB 3.0 ports don't work after suspend, xhci_hcd errors in kernel log Status in “linux” package in Ubuntu: Incomplete Status in Arch Linux: New Bug description: My laptop has one USB 2.0 port and a couple of USB 3.0 ports. The USB 3.0 ports only work after a fresh shutdown/restart, not after I suspend/resume. There are a couple of different USB controllers listed in lspci: $ sudo lspci -nn | grep USB 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) 03:00.0 USB controller [0c03]: Renesas Technology Corp. Device [1912:0015] (rev 02) lsusb lists a 3.0 root hub along wit the 2.0 one. $ sudo lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07da Intel Corp. Bus 001 Device 004: ID 2232:1024 I see the following errors in dmesg output (and nothing when I plug/unplug a device): $ dmesg | grep xhci [ 3916.808221] xhci_hcd :03:00.0: WARN: xHC restore state timeout [ 3916.808236] xhci_hcd :03:00.0: PCI post-resume error -110! [ 3916.808237] xhci_hcd :03:00.0: HC died; cleaning up [ 3916.808240] xhci_hcd :03:00.0: HC died; cleaning up ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1915 F pulseaudio Date: Sat Dec 29 11:54:48 2012 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (94 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-21-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/shaun not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1094534] Re: [Samsung NP900X4C-A03US] USB 3.0 ports don't work after suspend, xhci_hcd errors in kernel log
Sorry, I can't update the BIOS, the updater is Windows-only and I don't have Windows installed :-( $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date P03AAC 07/12/2012 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1094534 Title: [Samsung NP900X4C-A03US] USB 3.0 ports don't work after suspend, xhci_hcd errors in kernel log Status in “linux” package in Ubuntu: Incomplete Status in Arch Linux: New Bug description: My laptop has one USB 2.0 port and a couple of USB 3.0 ports. The USB 3.0 ports only work after a fresh shutdown/restart, not after I suspend/resume. There are a couple of different USB controllers listed in lspci: $ sudo lspci -nn | grep USB 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) 03:00.0 USB controller [0c03]: Renesas Technology Corp. Device [1912:0015] (rev 02) lsusb lists a 3.0 root hub along wit the 2.0 one. $ sudo lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07da Intel Corp. Bus 001 Device 004: ID 2232:1024 I see the following errors in dmesg output (and nothing when I plug/unplug a device): $ dmesg | grep xhci [ 3916.808221] xhci_hcd :03:00.0: WARN: xHC restore state timeout [ 3916.808236] xhci_hcd :03:00.0: PCI post-resume error -110! [ 3916.808237] xhci_hcd :03:00.0: HC died; cleaning up [ 3916.808240] xhci_hcd :03:00.0: HC died; cleaning up ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 1915 F pulseaudio Date: Sat Dec 29 11:54:48 2012 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (94 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-21-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/shaun not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 993164] Re: error file not found you need to load the kernel first failed to boot both default and fallback entries
This error is reproducable on my hardware >=12.04.2 with EFI mode on. Am posting this from 13.04 amd 64 desktop live session because of this error and others possibly associated with it. Using ga a75 ud4h mobo with latest firmware which uses EFI 1.1 rev 2 specification firmware. rEFInd sees this as ver UEFI 2.1. Using msinfo32 and windows upgrade assistant confirm this firmware/hardware is not Secure Boot capable. Searching Ask Ubuntu this bug may have regressed/resurfaced since 12.04.2/12.10. (http://askubuntu.com/search?tab=votes&q=you%20need%20to%20load%20kernel%20first). One similar question there http://askubuntu.com/q/206950/102029 links to this wiki http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/ which i have found helpful in getting confidence to post my first bug comment here. The article talks of first stage and second stage boot loaders as well as shim. Realise shim is Secure Boot related so is not the issue on this hardware but do not understand first stage and second stage boot loaders. Do know rEFInd sees BIOS/legacy bootloaders on media as "fallback loaders". I am guessing this is second stage bootloader. Which means if first stage loader is the signed.efi image then there is no usable .efi image to use on my hardware. How to EFI install Ubuntu on a system that is EFI capable but is not Secure Boot capable? Understand 11.04 11.10 want to make 16bit EFI partition if installing to a completely unallocated space drive which would mean fixing before trying to boot to - source http://www.rodsbooks.com/gb-hybrid-efi/ which is a different story. I can not boot any Ubuntu installer using EFI mode on this hardware. I asked this http://askubuntu.com/questions/208405/how-to-efi-install-ubuntu which links to thread over on Ubuntu Forums to try and find a working solution or a conclusion that explains why not! 13.04 installed using legacy settings although EFI was on which indicates the expected sequence described in http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/ However i can not replicate this and have never booted any Ubuntu installer using EFI mode on this hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/993164 Title: error file not found you need to load the kernel first failed to boot both default and fallback entries Status in “linux” package in Ubuntu: Confirmed Bug description: after upgrading to this kernel, the VM under ESXi 5.0 fails to boot the new kernel You have to boot from a live cd and uninstall the kernel to fix. Reverting to 2.6.32-40 solves the issue so this is a regression 2.6.32-41 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-41-server (not installed) Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-server x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory Date: Wed May 2 10:59:35 2012 InstallationMedia: Ubuntu-Server 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-40-server root=UUID=715b5cff-4255-40e6-ae71-e5cd7c7dc913 ro ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux dmi.bios.date: 01/07/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd01/07/2011:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1072378] Re: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready
This affects precise,quantal , and raring. Have not tried saucy yet. Is there a way to confirm the first stage installer are capable of running on an EFI system that is not secure boot capable? Is shim required on non SecureBoot system? I suspect if shim/ first stage installer are not able to run using .efi image and are only looking for signed.efi criteria not finding either so should drop to legacy/bios installer automatically but fall back installer is not running either. is only speculation because do not know the intended meaning of first and second stage installer- ref:http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/ ga a75 ud4h mobo being used. When booting precise,quantal or raring with EFI on get to situation as described http://askubuntu.com/q/208405/102029 and several other related questions. Searching ask ubuntu http://askubuntu.com/search?q=need+to+load+kernel+first+ confirms a recnt increase in these queries on differing hardware so this is almost a certain bug. Doing ls -l after dropping to command prompt when getting UEFI grub screen ref https://help.ubuntu.com/community/UEFI#Identifying_if_the_computer_boots_the_HDD_in_EFI_mode confirms cd0,apple1 and cd0apple2 images are detected and might go some way to explaining why they are not usable on an amd 64 platform. running lsefisystab here also indicates EFI ver 1.1. rev 2 rEFInd sees this firmware as UEFI 2.1 which goes to completely confirm this is not Secure Boot capable system. Confirm Christopher M. Penalver's workaround does work but i do not see this as afull solution due to the lack of being to use efibootmgr when booting live session- which has to be with EFI off due to installer bug. No efi = no efibootmgr. If dual booting with windows using this workaround will mean having to simply create grub_bios partition, install grub-efi and possibly rename windows bootfmgr to trick firmware to booting grub-efi. Using boot-repair seems to be the accepted and easiest way of doing this but has hugely varying success rates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1072378 Title: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready Status in “linux” package in Ubuntu: Incomplete Bug description: It crashes to the installation of grub (ASUS 1015BX, look screenshot) Here the hardware tested: http://kmuto.jp/debian/hcl/ASUS/1015BX+C-60 --- ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3223 F pulseaudio /dev/snd/controlC0: ubuntu 3223 F pulseaudio CasperVersion: 1.328 DistroRelease: Ubuntu 12.10 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUSTeK Computer INC. 1015BXO Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi.signed file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal Uname: Linux 3.5.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1015BXO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015BXO dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2719 F pulseaudio /dev/snd/controlC0: ubuntu 2719 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130814) MachineType: ASUSTeK Computer INC. 1015BXO MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE
[Kernel-packages] [Bug 1072378] Re: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready
Taking Secure Boot out of equation indicates this is almost certainly a grub 2 deficiency or bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1072378 Title: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready Status in “linux” package in Ubuntu: Incomplete Bug description: It crashes to the installation of grub (ASUS 1015BX, look screenshot) Here the hardware tested: http://kmuto.jp/debian/hcl/ASUS/1015BX+C-60 --- ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3223 F pulseaudio /dev/snd/controlC0: ubuntu 3223 F pulseaudio CasperVersion: 1.328 DistroRelease: Ubuntu 12.10 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUSTeK Computer INC. 1015BXO Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi.signed file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal Uname: Linux 3.5.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1015BXO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015BXO dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2719 F pulseaudio /dev/snd/controlC0: ubuntu 2719 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130814) MachineType: ASUSTeK Computer INC. 1015BXO MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-1-generic N/A linux-backports-modules-3.11.0-1-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1015BXO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015BXO dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213172] [NEW] "You need to load the kernel first" when trying select any option from grub list when using EFI
Public bug reported: will use url to add linux as affects to this bug report https://bugs.launchpad.net/ubiquity/+bug/1213119 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3446 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.331 Date: Fri Aug 16 17:26:40 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. GA-A75-UD4H MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8c dmi.board.name: GA-A75-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8c:bd12/07/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213172 Title: "You need to load the kernel first" when trying select any option from grub list when using EFI Status in “linux” package in Ubuntu: New Bug description: will use url to add linux as affects to this bug report https://bugs.launchpad.net/ubiquity/+bug/1213119 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3446 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.331 Date: Fri Aug 16 17:26:40 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. GA-A75-UD4H MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8c dmi.board.name: GA-A75-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8c:bd12/07/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213172] Re: "You need to load the kernel first" when trying select any option from grub list when using EFI
Uploaded this report with intaention of adding as affected to https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1213119 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213172 Title: "You need to load the kernel first" when trying select any option from grub list when using EFI Status in “linux” package in Ubuntu: New Bug description: will use url to add linux as affects to this bug report https://bugs.launchpad.net/ubiquity/+bug/1213119 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3446 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.331 Date: Fri Aug 16 17:26:40 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. GA-A75-UD4H MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8c dmi.board.name: GA-A75-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8c:bd12/07/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025467] Re: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc
This affects raring -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1025467 Title: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc Status in “linux” package in Ubuntu: In Progress Status in “procps” package in Ubuntu: Fix Released Bug description: In fixing Bug #194676 all of the sysrq functionality was disabled. Some options are of low security impact but aid debugabilty of systems. It would be good to reenable what we can. See the original bug for suggested values in use by other distros. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: procps 1:3.3.3-2ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Mon Jul 16 23:13:10 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: procps UpgradeStatus: Upgraded to quantal on 2012-01-04 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025467] Re: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc
Booting Ubuntu Desktop amd64 liveDVD (3.8.0-19-generic) in BIOS mode searching "computer" using file manager to find sysreq settings is now found in /etc/systl.d and named 10-magic-sysrq.conf. Looking in my Ubuntu partitionb which was last bootable using 3.8.0.28 kernel; also confirms sysrq as being disabled by default Can not find why this has been disabled as default so would like to take opportunity to ask; Why is sysrq disabled as default on liveDVD? Reading the original bug report refers to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194676 confirms there may be secuity issues related to this. Is it possible to ask for some reasoning to this? I thought linux had reputation of being secure and virus free!? Is not a better idea to have sysrq enabled to allow the well known and used RSEIUB(O) if sytem hangs or freezes? At least providing the protection of minimising having to recover sytem files or data due to corrupting hard drive and the need for fsck to kick in or be started manually from recovery.? Am asking these questions after watching 17 08 2013 episode of the BBC programme ["Click"](http://www.bbc.co.uk/iplayer/episode/b0392vqy/Click_17_08_2013/) and the "cyberwarfare" article really caught my attention. FAWC ** Attachment added: "13.04 3.8.0.19 10-magic-sysrq.conf" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1025467/+attachment/3777203/+files/10-magic-sysrq.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1025467 Title: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc Status in “linux” package in Ubuntu: In Progress Status in “procps” package in Ubuntu: Fix Released Bug description: In fixing Bug #194676 all of the sysrq functionality was disabled. Some options are of low security impact but aid debugabilty of systems. It would be good to reenable what we can. See the original bug for suggested values in use by other distros. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: procps 1:3.3.3-2ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Mon Jul 16 23:13:10 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: procps UpgradeStatus: Upgraded to quantal on 2012-01-04 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025467] Re: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc
If sysrq is disabled by default and users are saying it works for them (Ask Ubuntu) ie http://askubuntu.com/questions/53263/shut-down-computer- from-keyboard/53266#53266 Perhaps this is evidence of why full disablement of sysrq is applied by default? ie If user did not set sysrq on; Who did? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1025467 Title: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc Status in “linux” package in Ubuntu: In Progress Status in “procps” package in Ubuntu: Fix Released Bug description: In fixing Bug #194676 all of the sysrq functionality was disabled. Some options are of low security impact but aid debugabilty of systems. It would be good to reenable what we can. See the original bug for suggested values in use by other distros. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: procps 1:3.3.3-2ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Mon Jul 16 23:13:10 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: procps UpgradeStatus: Upgraded to quantal on 2012-01-04 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025467] Re: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc
Sorry wrong link- intended to post http://askubuntu.com/questions/11002 /alt-sysrq-reisub-doesnt-reboot-my-laptop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1025467 Title: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc Status in “linux” package in Ubuntu: In Progress Status in “procps” package in Ubuntu: Fix Released Bug description: In fixing Bug #194676 all of the sysrq functionality was disabled. Some options are of low security impact but aid debugabilty of systems. It would be good to reenable what we can. See the original bug for suggested values in use by other distros. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: procps 1:3.3.3-2ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Mon Jul 16 23:13:10 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: procps UpgradeStatus: Upgraded to quantal on 2012-01-04 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025467] Re: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc
Apologies once again. Now understand S U B are only sysrq commands allowed by default by the use of bitmask 176 which for it is easy to change or adapt relevant settings to any other commands as needed or desired. This for me is applicable to 12.10 and 13.04 desktop amd64. Suprisingly very little information regarding sysrq in Official Ubuntu Documentation. Have posted an answer with much useful information regarding the use and configuration of sysrq in the link posted in last comment. The majority of the answer is copied from another ditrubitions wiki which is based on the Linux Kernel Documentation regarding sysrq. The conclusion to the answer in linked Ask Ubuntu question above is to leave the default settings as is unless there is obvious need to do otherwise. Just use SUB instead of RSEIUB! Tryng sysrq commands in tty will give text output which helps understand and prove there never was a complete disabling of sysrq. Have taken back my affected vote as a little research has proven i am unaffected. Another example of how Ask Ubuntu is a brilliant learning tool and just one of the many brilliant resources available through using Ubuntu! Links provided by mniess in other answer to the same question are key in understanding and appreciating why the need for different bitmask has come about and this is not a new concept. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1025467 Title: sysrq is now completely disabled, it would be nice to maintain the ability to reboot etc Status in “linux” package in Ubuntu: In Progress Status in “procps” package in Ubuntu: Fix Released Bug description: In fixing Bug #194676 all of the sysrq functionality was disabled. Some options are of low security impact but aid debugabilty of systems. It would be good to reenable what we can. See the original bug for suggested values in use by other distros. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: procps 1:3.3.3-2ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Mon Jul 16 23:13:10 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: procps UpgradeStatus: Upgraded to quantal on 2012-01-04 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1213172] Re: "You need to load the kernel first" when trying select any option from grub list when using EFI
*** This bug is a duplicate of bug 1213119 *** https://bugs.launchpad.net/bugs/1213119 Sorry for not replying quicker. Just acknowleging last comment and would like to confirm this possible bug i am trying to describe is at install time. Also this is duplicate due to me trying to add reports to bug#1213119. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1213172 Title: "You need to load the kernel first" when trying select any option from grub list when using EFI Status in “linux” package in Ubuntu: Incomplete Bug description: will use url to add linux as affects to this bug report https://bugs.launchpad.net/ubiquity/+bug/1213119 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3446 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.331 Date: Fri Aug 16 17:26:40 2013 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. GA-A75-UD4H MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=gb RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8c dmi.board.name: GA-A75-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8c:bd12/07/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1072378] Re: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready
Christopher M . Penalver; Apologies for posting technical inaccuracies to an unrelated bug report. Have unmarked as affected here and will follow your advice. My troubles now seem (to me)to be vendor/firmware related and will subscribe you to another bug report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1072378 Title: [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready Status in “linux” package in Ubuntu: Incomplete Bug description: It crashes to the installation of grub (ASUS 1015BX, look screenshot) Here the hardware tested: http://kmuto.jp/debian/hcl/ASUS/1015BX+C-60 --- ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3223 F pulseaudio /dev/snd/controlC0: ubuntu 3223 F pulseaudio CasperVersion: 1.328 DistroRelease: Ubuntu 12.10 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUSTeK Computer INC. 1015BXO Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi.signed file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal Uname: Linux 3.5.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1015BXO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015BXO dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2719 F pulseaudio /dev/snd/controlC0: ubuntu 2719 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130814) MachineType: ASUSTeK Computer INC. 1015BXO MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-1-generic N/A linux-backports-modules-3.11.0-1-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 1015BXO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015BXO dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1053897] Re: kernel does not boot without noefi on commandline
On different hardware GA A75 UD4H this is a very similar issue regarding using EFI to install Ubuntu. Have tried from 11.04 and up to 13.04 all with same result ie does not run installer in EFI mode, noefi does not work for me but running installer using BIOS/legacy mode does work then installing grub-efi gets Ubuntu booting using EFI mode. My bug report (https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1213119) is still unfinished and not confirmed as bug as of yet. There are many similar bugs to this one and mine. My own research is indicating this type of problem is more and more likely to be vendor hard coding of firmware. This is unproven theory and currently stands as speculation. Just seems many vendors creating very similar issues regarding the installation of Ubuntu using U/EFI and that is with or without Secure Boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1053897 Title: kernel does not boot without noefi on commandline Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Quantal: Incomplete Bug description: The machine is an ASUS Laptop N53SN. In BIOS mode, everything works ok, but in UEFI, the kernel does not boot. The only way to boot it is to provide the noefi option on the cmdline. This machine never booted with any ubuntu distribution in efi. Direct boot with linux-efi kernel image, show the same behaviour. The only distribution that boots in UEFI is the alpha version of Fedora 18. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-14-generic 3.5.0-14.15 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing /usr/share/apport/dump_acpi_tables.py: Permission denied ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: seb1743 F pulseaudio /dev/snd/controlC0: seb1743 F pulseaudio Date: Fri Sep 21 11:04:04 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=2755aeb4-461b-4bdf-b217-63cb230defa9 ro noefi quiet splash RelatedPackageVersions: linux-restricted-modules-3.5.0-14-generic N/A linux-backports-modules-3.5.0-14-generic N/A linux-firmware1.91 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-09-07 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1053897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1053897] Re: kernel does not boot without noefi on commandline
Ubuntu flavours <=12.04.1 may cause trouble regarding making a 16bit; or wanting to use a 16bit ESP whereas firmwares are looking for 32bit ESP= no worky!? The workaround is to allow installer to run as it wants to but be sure to copy ESP save in another location then delete 16bit ESP and remake 32bit ESP replacing the files from 16bit ESP before rebooting trying to use U/EFI. source http://www.rodsbooks.com/gb-hybrid-efi/ "A FAT-16 ESP, on the other hand, seems problematic. Ubuntu 11.04 (and 11.10) in EFI mode creates a dinky FAT-16 ESP, and after my test install of Ubuntu 11.04, the board hung on reboot until I reworked the ESP as FAT-32. Thus, if you plan to install Ubuntu, or any other OS that creates a FAT-16 ESP, be prepared to fix it, preferably before the system reboots!" "rodsbooks" is an absolutely indispensible source of all things factual regarding U/EFI which demystifies and disproves many myths as well as misinformation regarding this subject. Again these type of idiosyncrasies appear to be vendor specific. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1053897 Title: kernel does not boot without noefi on commandline Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Quantal: Incomplete Bug description: The machine is an ASUS Laptop N53SN. In BIOS mode, everything works ok, but in UEFI, the kernel does not boot. The only way to boot it is to provide the noefi option on the cmdline. This machine never booted with any ubuntu distribution in efi. Direct boot with linux-efi kernel image, show the same behaviour. The only distribution that boots in UEFI is the alpha version of Fedora 18. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-14-generic 3.5.0-14.15 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing /usr/share/apport/dump_acpi_tables.py: Permission denied ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: seb1743 F pulseaudio /dev/snd/controlC0: seb1743 F pulseaudio Date: Fri Sep 21 11:04:04 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-14-generic root=UUID=2755aeb4-461b-4bdf-b217-63cb230defa9 ro noefi quiet splash RelatedPackageVersions: linux-restricted-modules-3.5.0-14-generic N/A linux-backports-modules-3.5.0-14-generic N/A linux-firmware1.91 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-09-07 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1053897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] [NEW] Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade
Public bug reported: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: raring -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Incomplete Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Re: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+attachment/3847174/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Incomplete Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Re: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+attachment/3847173/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Incomplete Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] HookError_cloud_archive.txt
apport information ** Attachment added: "HookError_cloud_archive.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847214/+files/HookError_cloud_archive.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/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847213/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847216/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847211/+files/BootDmesg.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/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847226/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847218/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847224/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847215/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847212/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Re: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade
apport information ** Tags added: apport-collected ** Description changed: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 + --- + ApportVersion: 2.9.2-0ubuntu8.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: sduncan1885 F pulseaudio + DistroRelease: Ubuntu 13.04 + HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d + InstallationDate: Installed on 2013-08-13 (45 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) + MachineType: Dell Inc. Dell System XPS L322X + MarkForUpload: True + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 + RelatedPackageVersions: + linux-restricted-modules-3.8.0-31-generic N/A + linux-backports-modules-3.8.0-31-generic N/A + linux-firmware1.106 + Tags: raring + Uname: Linux 3.8.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 05/15/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A09 + dmi.board.name: 0WG38X + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: + dmi.product.name: Dell System XPS L322X + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847210/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847220/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847219/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847223/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847221/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847222/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847217/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1232459/+attachment/3847225/+files/UdevLog.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/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Re: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade
I've double-checked, and I'm running this XPS via UEFI boot. Most of my searching for any resolution has mentioned additions/removals from GRUB_CMDLINE_LINUX_DEFAULT, but nothing has helped there (currently only arguments passed are "quiet splash") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1232459] Re: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade
I attempted the upstream 3.8.13.10 kernel, but was unable to boot. I've tagged this bug indicating that. ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1232459 Title: Brightness control broken for Dell XPS 13 on Raring 13.04 after kernel upgrade Status in “linux” package in Ubuntu: Confirmed Bug description: I've seen this problem in both kernels 3.8.0.30-generic and 3.8.0.31-generic. It seems to be working without any problems in 3.8.0.29-generic. Current version of intel packages: xserver-xorg-video-intel: 2:2.21.6-0ubuntu4.1 libdrm-intel1: 2.4.43-0ubuntu1.1 --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sduncan1885 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=c4838fd3-7b17-4660-bcee-182637bc6e6d InstallationDate: Installed on 2013-08-13 (45 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic.efi.signed root=UUID=d04e0f52-da13-4e30-9581-f0a8d2f32051 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WG38X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WG38X:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1084264] Re: Kernel 3.2.0-33 Introduces Ridiculous / Impossible Load Averages
I can no longer replicate this using the 3.2.0-54 kernel. I'm going to assume one of the intermediate versions fixed the issue. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1084264 Title: Kernel 3.2.0-33 Introduces Ridiculous / Impossible Load Averages Status in “linux” package in Ubuntu: Fix Released Bug description: After upgrading to the 3.2.0-33 kernel, our load averages have been very, very odd. Here is a sample sar -q line: 15:05:02 runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 blocked 15:05:212 322 44.02 12.51 14.08 1 A run queue size of 2, with a load average of 44? So I wrote a script to track run queue and uninterruptable sleep, since both contribute to load average. Script is attached. Sample output during a run: Stat Time Run+Sleep Load Avg 2012-11-28 15:47:53 2 71.54 2012-11-28 15:47:54 1 71.54 2012-11-28 15:47:55 1 71.54 2012-11-28 15:47:56 1 71.54 2012-11-28 15:47:57 1 71.54 2012-11-28 15:47:58 1 65.81 This behavior is not observed with kernel 3.2.0-31. Problem can be reproduced with a basic pgbench test to simulate busy state, but only seems to occur during rapid process cycling. An easy simulation: for x in {1..100}; do pgbench -T 5 -j 2 -c 2 pgbench sleep 1 done Test may need to run for several minutes to trigger load spike. It will look similar to this: Stat Time Run+Sleep Load Avg 2012-11-28 16:01:17 3 10.37 2012-11-28 16:01:18 3 9.54 2012-11-28 16:01:19 3 9.54 2012-11-28 16:01:20 2 9.54 2012-11-28 16:01:21 5 9.54 2012-11-28 16:01:22 3 9.54 2012-11-28 16:01:23 1 47.94 System info: Description: Ubuntu 12.04.1 LTS Release: 12.04 Linux 3.2.0-33-generic #52-Ubuntu SMP Thu Oct 18 16:29:15 UTC 2012 x86_64 linux-image-3.2.0-33-generic: Installed: 3.2.0-33.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1084264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895434] [NEW] Display corruption after suspend with recent kernel update
50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895434 Title: Display corruption after suspend with recent kernel update Status in linux package in Ubuntu: Confirmed Bug description: For the last few days, after suspending and resuming, I get display corruption in Google Chrome. Parts of the UI are replaces with black boxes. Resizing the window causes it to redraw but if I switch back to the original size then it goes back to black. I noticed it on 5.4.0-47 and backed down to 5.4.0-45 but still see the same. Looks like 5.4.0-45 was only released a few days before 5.4.0-47 so maybe I didn't reboot in that time. Those are the only upgrades I can see in the right timeframe. I had a look in dmesg and saw some warnings; not sure if they're related: [ 59.251347] [ cut here ] [ 59.251357] WARNING: CPU: 6 PID: 4533 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [ 59.251358] Modules linked in: msr nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter rfcomm ccm typec_displayport cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc aufs overlay bnep binfmt_misc nls_iso8859_1 btusb btrtl btbcm btintel snd_usb_audio bluetooth snd_usbmidi_lib ecdh_generic ecc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common dell_rbtn snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp mei_hdcp snd_hda_ext_core snd_hda_codec_hdmi snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_msr snd_soc_core snd_compress ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp [ 59.251391] snd_hda_codec_generic coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm dell_laptop ledtrig_audio snd_seq_mi
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
3606e0 [ 59.251478] DR0: DR1: DR2: [ 59.251479] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.251480] Call Trace: [ 59.251489] __video_do_ioctl+0x1a7/0x410 [videodev] [ 59.251499] video_usercopy+0x2b5/0x670 [videodev] [ 59.251507] ? v4l_s_fmt+0x670/0x670 [videodev] [ 59.251517] video_ioctl2+0x15/0x20 [videodev] [ 59.251525] v4l2_ioctl+0x4c/0x60 [videodev] [ 59.251528] do_vfs_ioctl+0x407/0x670 [ 59.251532] ? putname+0x4a/0x50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F.... pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
DR0: DR1: DR2: [ 59.251479] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.251480] Call Trace: [ 59.251489] __video_do_ioctl+0x1a7/0x410 [videodev] [ 59.251499] video_usercopy+0x2b5/0x670 [videodev] [ 59.251507] ? v4l_s_fmt+0x670/0x670 [videodev] [ 59.251517] video_ioctl2+0x15/0x20 [videodev] [ 59.251525] v4l2_ioctl+0x4c/0x60 [videodev] [ 59.251528] do_vfs_ioctl+0x407/0x670 [ 59.251532] ? putname+0x4a/0x50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
DR6: fffe0ff0 DR7: 0400 [ 59.251480] Call Trace: [ 59.251489] __video_do_ioctl+0x1a7/0x410 [videodev] [ 59.251499] video_usercopy+0x2b5/0x670 [videodev] [ 59.251507] ? v4l_s_fmt+0x670/0x670 [videodev] [ 59.251517] video_ioctl2+0x15/0x20 [videodev] [ 59.251525] v4l2_ioctl+0x4c/0x60 [videodev] [ 59.251528] do_vfs_ioctl+0x407/0x670 [ 59.251532] ? putname+0x4a/0x50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
fffe0ff0 DR7: 0400 [ 59.251480] Call Trace: [ 59.251489] __video_do_ioctl+0x1a7/0x410 [videodev] [ 59.251499] video_usercopy+0x2b5/0x670 [videodev] [ 59.251507] ? v4l_s_fmt+0x670/0x670 [videodev] [ 59.251517] video_ioctl2+0x15/0x20 [videodev] [ 59.251525] v4l2_ioctl+0x4c/0x60 [videodev] [ 59.251528] do_vfs_ioctl+0x407/0x670 [ 59.251532] ? putname+0x4a/0x50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895434] Re: Display corruption after suspend with recent kernel update
[ 59.251478] DR0: DR1: DR2: [ 59.251479] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.251480] Call Trace: [ 59.251489] __video_do_ioctl+0x1a7/0x410 [videodev] [ 59.251499] video_usercopy+0x2b5/0x670 [videodev] [ 59.251507] ? v4l_s_fmt+0x670/0x670 [videodev] [ 59.251517] video_ioctl2+0x15/0x20 [videodev] [ 59.251525] v4l2_ioctl+0x4c/0x60 [videodev] [ 59.251528] do_vfs_ioctl+0x407/0x670 [ 59.251532] ? putname+0x4a/0x50 [ 59.251535] ksys_ioctl+0x67/0x90 [ 59.251538] __x64_sys_ioctl+0x1a/0x20 [ 59.251542] do_syscall_64+0x57/0x190 [ 59.251547] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 59.251548] RIP: 0033:0x7fab7c00537b [ 59.251551] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 59.251552] RSP: 002b:7fffa3357b68 EFLAGS: 0246 ORIG_RAX: 0010 [ 59.251554] RAX: ffda RBX: 0017 RCX: 7fab7c00537b [ 59.251556] RDX: 7fffa3357c20 RSI: 80685600 RDI: 0017 [ 59.251557] RBP: 7fffa3357d10 R08: R09: 2f5a17cee340 [ 59.251558] R10: R11: 0246 R12: 7fffa3357b90 [ 59.251560] R13: 2f5a17cdb0c0 R14: 2f5a17cee450 R15: 2f5a17cebb70 [ 59.251562] ---[ end trace a46f21f7de3e614d ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2662 F pulseaudio /dev/snd/controlC0: shaun 2662 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 10:51:25 2020 InstallationDate: Installed on 2018-12-11 (641 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-45-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (133 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
I added ppa:canonical-kernel-team/ppa2 but still get the same error in the log file. This is after apt upgrade and booting into the newer kernel image. Should it have worked or am I missing a step to test? ... Loading new amdgpu-5.16.9.22.20-1438747~22.04 DKMS files... Building for 5.15.0-56-generic Building for architecture x86_64 Building initial module for 5.15.0-56-generic ERROR (dkms apport): kernel package linux-headers-5.15.0-56-generic is not supported Error! Bad return status for module build on kernel: 5.15.0-56-generic (x86_64) Consult /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/make.log for more information. dpkg: error processing package amdgpu-dkms (--configure): installed amdgpu-dkms package post-installation script subprocess returned error exit status 10 ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
ok, I see. I"ll try to figure out how to report the same issue for the AMD release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Still seems to be an issue; I tried 4.18.16 on 18.10 and it didn't help (nor did the most recent 4.19 kernel in UKUU). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw&sh=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.n
[Kernel-packages] [Bug 1822089] [NEW] Frequent (silent) USB disconnects with Dell TB16 dock
Public bug reported: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: New Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
** Attachment added: "lspci output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+attachment/5250165/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: New Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Dock is unusable with current Ubuntu kernel (screen locks up) as per https://bugs.launchpad.net/dell-sputnik/+bug/1752165 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
another datapoint: kernel 5.0.4 from UKUU doesn't show the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw&sh=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.sys.vendor: Del
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
I tried the latest kernel on 18.10 but still see the issue: 4.18.0-17. Dell Precision 5530, Intel+NVIDIA graphics with Intel graphics selected. I'm also using the workaround from https://bugs.freedesktop.org/show_bug.cgi?id=109675, which prevents the screen from "shuffling" back and forth after plugging in the dock. ** Bug watch added: freedesktop.org Bugzilla #109675 https://bugs.freedesktop.org/show_bug.cgi?id=109675 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw&sh=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
apport information ** Tags added: apport-collected ** Description changed: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. - Other devices disconnect too but the pattern is different. Much more - likely to see the disconnect under heavy load, such as webcam/headset - getting disconnected during a conference call. + Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC4: shaun 2837 F pulseaudio + /dev/snd/controlC3: shaun 2837 F pulseaudio + /dev/snd/controlC1: shaun 2837 F pulseaudio + /dev/snd/controlC0: shaun 2837 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-12-11 (133 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + MachineType: Dell Inc. Precision 5530 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 02/01/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.8.1 + dmi.board.name: 0FP2W2 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 5530 + dmi.product.sku: 087D + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258707/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (n
[Kernel-packages] [Bug 1822089] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258710/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258709/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258708/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258711/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258712/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258713/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258717/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258714/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258716/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258715/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258719/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258718/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Upgraded to 19.04, which has a kernel that works with the dock and attached the diagnostics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258720/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1822089/+attachment/5258721/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Attaching the dmesg.log with dyndgg=+p Device that disconnected was "Microsoft Comfort Curve Keyboard" ** Attachment added: "dmesg with usbcore.dyndbg=+p" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+attachment/5258924/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock
Yes, will see if I can borrow a Windows laptop to do that. How would I switch to hid-microsoft? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822089 Title: Frequent (silent) USB disconnects with Dell TB16 dock Status in linux package in Ubuntu: Confirmed Bug description: I see something similar (but different) to bug 1766076 on a Dell 5530: - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from other bugs that make this dock unusable) - BIOS 1.6.0 - TB16 dock with a single monitor on the display port, providing power, using native enumeration setting in the BIOS - Microsoft comfort curve keyboard, webcam, headset connected to dock USB ports - Wired ethernet via the dock. Keyboard stops responding frequently. There is no output in dmesg when this happens. If I later unplug the keyboard I see a disconnection message in dmesg and I can reconnect it to the same port. Sometimes it works for a day after this, other times it works for <60s. Other devices disconnect too but the pattern is different. Much more likely to see the disconnect under heavy load, such as webcam/headset getting disconnected during a conference call. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC4: shaun 2837 F pulseaudio /dev/snd/controlC3: shaun 2837 F pulseaudio /dev/snd/controlC1: shaun 2837 F pulseaudio /dev/snd/controlC0: shaun 2837 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-12-11 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899766] Re: Xorg freeze after selecting large cursor
Found the source of the v4l warnings; I was experimenting with v4lloopback to use a camera as webcam. Disabled that and it's gone away. Unfortunately, /var/crash is empty and I didn't see any report from the right time in the errors webpage. After applying the change to add "Crash" to the crashdb.conf, I still don't see a crash dump in /var/crash after repro. However, I did find that the problem only repros in NVIDIA PRIME mode, not Intel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Following kernel seems to fix the issue (running on 18.10 with kernel installed by UKUU): 4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I still see one or two of these errors when hotplugging but the others are gone and the external screen works: [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw&sh=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.boar
[Kernel-packages] [Bug 1882510] [NEW] IRQ/51-SYNA2393 using lots of CPU after suspend/resume
Public bug reported: After a suspend/resume cycle (using "deep" suspend mode), the process IRQ/51-SYNA2393 uses considerable CPU 10+%. Using the trackpad for a few seconds seems to fix the issue. I don't normally use the trackpad while docked so it's a bit annoying to have to remember to use it just to get this problem to go away. Looks like others have hit the same issue; I found this on askubuntu: https://askubuntu.com/questions/1138642/ubuntu-18-04-drains-battery- very-fast-after-wake-up-from-a-deep-sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.33.38 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2997 F pulseaudio /dev/snd/controlC0: shaun 2997 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 11:30:07 2020 InstallationDate: Installed on 2018-12-11 (544 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (36 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882510 Title: IRQ/51-SYNA2393 using lots of CPU after suspend/resume Status in linux package in Ubuntu: New Bug description: After a suspend/resume cycle (using "deep" suspend mode), the process IRQ/51-SYNA2393 uses considerable CPU 10+%. Using the trackpad for a few seconds seems to fix the issue. I don't normally use the trackpad while docked so it's a bit annoying to have to remember to use it just to get this problem to go away. Looks like others have hit the same issue; I found this on askubuntu: https://askubuntu.com/questions/1138642/ubuntu-18-04-drains-battery- very-fast-after-wake-up-from-a-deep-sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.33.38 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: shaun 2997 F pulseaudio /dev/snd/controlC0: shaun 2997 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 11:30:07 2020 InstallationDate: Installed on 2018-12-11 (544 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (36 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lis