[Kernel-packages] [Bug 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor
Thanks for looking so quickly. I'm almost certain the problem will go away without the nvidia driver because the nouveau driver didn't recognise the hardware when I booted off the USB installer, so reverse prime won't work and there will be no external monitor, which is a completely new problem. I was logged into a clean profile with no non-standard gnome-shell extensions running, and 'top' showed Xorg (40%) and irq/93-nvidia (1%) and nvidia-modeset/ (0.3%) as the top three CPU hogs, so it's unlikely to be extensions causing it. FYI, when I checked the journal log for those nv_drm_master_set errors right now, I can see a bunch at 11:47 and another bunch at 11:54, but nothing since (it's now 12:43). But the CPU usage is still high. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944667 Title: High CPU usage in Xorg with NVIDIA reverse prime external monitor Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the laptop display) and an external monitor connected via the nvidia card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with no apps running. If I put the laptop in discrete graphics mode so the nvidia card drives both the laptop display and the external monitor Xorg uses close to 0% CPU, which is what I would expect it to be in hybrid mode. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-core 2:1.20.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Sep 23 11:48:15 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:380c] InstallationDate: Installed on 2021-09-15 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash 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 SourcePackage: xorg-server 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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Kernel-packages] [Bug 1944094] [NEW] Can't adjust screen backlight on Legion Slim 7 AMD
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You 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 AMD Status in linux package in Ubuntu: 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:
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Just to confirm, Ubuntu's mainline 5.14.5 kernel does boot successfully on my machine with CONFIG_UBSAN_TRAP not set. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
I also can't boot the mainline 5.14-4 or 5.14-5 kernels on a Lenovo S7 (AMD 5800H and NVIDIA GPU) - it goes to a blank screen when trying to boot graphics and freezes - I can't open a tty and have to hard reset the system. It looks like I have the laptop in the same mode as the other posters, ie hybrid/dynamic graphics mode using the amdgpu driver for the laptop screen. I can't see any relevant errors in the output "journalctl -b -1" for the failed boot - I think the hang occurs before it has a chance to log them. However, when booting the stock Ubuntu 21.10 5.13.0-16 kernel I do see some nvidia_drm RIP errors in the log in nv_drm_master_set(). Presumably these errors in combination with CONFIG_UBSAN_TRAP are causing the hang? The documentation says that in order to save around 5% of the kernel size, CONFIG_UBSAN_TRAP "reduces the kernel size overhead but turns all warnings (including potentially harmless conditions) into full exceptions that abort the running kernel code (regardless of context, locks held, etc), which may destabilize the system." It seems like a pretty aggressive config option to set! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898395] Re: [nvidia] [amdgpu] Problem with external monitor
Could this be the problem described here: https://forums.developer.nvidia.com/t/ryzen-7-gtx-1660ti-blank-screen- on-external-outputs-in-hybrid-graphics-mode/157800 ie (and this is the case if the external display is connected to the NVIDIA card): "Using amdgpu as a display offload source is currently not supported due to an incompatibility between how the amdgpu driver creates “transparent huge pages” without the compound page flag set and how the NVIDIA driver tries to map them. You can see that this is happening in the dmesg log: [ 49.852234] Unhandled error in __nv_drm_gem_user_memory_handle_vma_fault: -22 Unfortunately, the only current workaround is to recompile the kernel without the CONFIG_TRANSPARENT_HUGEPAGE flag enabled. We’re investigating other ways to work around the problem." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1898395 Title: [nvidia] [amdgpu] Problem with external monitor Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: So, I installed Ubuntu 20.04 on my laptop with Ryzen 7 4800h processor and Nvidia gtx 1650 graphic card.. But i wasn't able to make my external monitor work.. At first it wasn't even recognized, but after I updated kernel to version 5.7.1 and with(only with latest) nvidia drivers 450 it recognized external monitor and I get options when I press SUPER KEY + P that I can switch screens.. But even though I pick external monitor and I see that it switch to it, monitor is turned on, but I have only black screen and can't do anything.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.1-050701-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 22:59:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.7.1-050701-generic, x86_64: installed nvidia, 450.66, 5.7.1-050701-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2020-09-15 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=29bfdbd7-583f-4a6e-8e15-9bf5e33c383d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO 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 N/A 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
[Kernel-packages] [Bug 1841556] Re: cpu frequency stuck below min frequency with power_save governor
I've not had a chance to test it recently - I haven't seen it happen for a while, but I'm not switching between the nvidia and intel cards, either, so I don't expect to. If I get a chance to try it on the weekend I'll report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841556 Title: cpu frequency stuck below min frequency with power_save governor Status in linux package in Ubuntu: Confirmed Bug description: Sometimes my laptop will be very sluggish after rebooting from prime- select = nvidia back into intel and it's because the cpu frequency is stuck in the range approx 450-750 MHz instead of its normal range of 800 MHz to 3.8 GHz. Switching to use the performance governor restores performance, but if I switch back to powersave, the frequency gets stuck again below the minimum. I've attached dumps of /sys/cpuinfo and /sys/devices/system/cpu/cpu0/cpufreq/* to show the current frequency is below 750 MHz even though the minimum frequency is 800 MHz. Usually this resolves after a second reboot but this time it has persisted over several reboots (and it doesn't matter whether I boot into linux 5.2 or 5.3-rc6). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1400 F pulseaudio rocko 1829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 16:46:08 2019 InstallationDate: Installed on 2019-07-01 (56 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-10-generic root=UUID=f5a24957-19c2-4a22-acc0-3776c6300bf5 ro rootflags=subvol=@ quiet splash scsi_mod.use_blk_mq=1 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.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd05/23/2019:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841556] [NEW] cpu frequency stuck below min frequency with power_save governor
Public bug reported:
Sometimes my laptop will be very sluggish after rebooting from prime-
select = nvidia back into intel and it's because the cpu frequency is
stuck in the range approx 450-750 MHz instead of its normal range of 800
MHz to 3.8 GHz. Switching to use the performance governor restores
performance, but if I switch back to powersave, the frequency gets stuck
again below the minimum.
I've attached dumps of /sys/cpuinfo and
/sys/devices/system/cpu/cpu0/cpufreq/* to show the current frequency is
below 750 MHz even though the minimum frequency is 800 MHz.
Usually this resolves after a second reboot but this time it has
persisted over several reboots (and it doesn't matter whether I boot
into linux 5.2 or 5.3-rc6).
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-10-generic 5.2.0-10.11
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1400 F pulseaudio
rocko 1829 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 27 16:46:08 2019
InstallationDate: Installed on 2019-07-01 (56 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-10-generic
root=UUID=f5a24957-19c2-4a22-acc0-3776c6300bf5 ro rootflags=subvol=@ quiet
splash scsi_mod.use_blk_mq=1 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.2.0-10-generic N/A
linux-backports-modules-5.2.0-10-generic N/A
linux-firmware1.181
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.0:bd05/23/2019:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
** Attachment added: "cpu system files"
https://bugs.launchpad.net/bugs/1841556/+attachment/5284879/+files/cpuinfo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1841556
Title:
cpu frequency stuck below min frequency with power_save governor
Status in linux package in Ubuntu:
New
Bug description:
Sometimes my laptop will be very sluggish after rebooting from prime-
select = nvidia back into intel and it's because the cpu frequency is
stuck in the range approx 450-750 MHz instead of its normal range of
800 MHz to 3.8 GHz. Switching to use the performance governor restores
performance, but if I switch back to powersave, the frequency gets
stuck again below the minimum.
I've attached dumps of /sys/cpuinfo and
/sys/devices/system/cpu/cpu0/cpufreq/* to show the current frequency
is below 750 MHz even though the minimum frequency is 800 MHz.
Usually this resolves after a second reboot but this time it has
persisted over several reboots (and it doesn't matter whether I boot
into linux 5.2 or 5.3-rc6).
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-10-generic 5.2.0-10.11
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1400 F pulseaudio
rocko 1829 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 27 16:46:08 2019
InstallationDate: Installed on 2019-07-01 (56 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-10-generic
root=UUID=f5a24957-19c2-4a22-acc0-3776c6300bf5 ro rootflags=subvol=@ quiet
splash scsi_mod.use_blk_mq=1 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! (
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
The patch that satmandu mentioned in https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1830961/comments/16 fixes the v5.2.0 mainline kernel build as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: Confirmed Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830170] [NEW] modprobe nvidia fails after suspend/resume cycle
Public bug reported: My hyrbrid intel-nvidia system is set up to use the intel card by default, and the nvidia card power management is done by the kernel (I run a version of bbswitch that does no power management.) After a reboot, the nvidia card on my hyrbrid intel-nvidia system is by default suspended by the kernel, but you can enable it by loading the module with "sudo modprobe nvidia". Using bumblebee, I can run programs on the nvidia card via optirun. However, after a suspend/resume cycle, trying to load the nvidia module fails: $ sudo modprobe nvidia modprobe: ERROR: could not insert 'nvidia': No such device This happens whether I disable bumblebeed.service or not via systemctl. It also happens if I load the nvidia module prior to suspending so the card is active. It also happens whether I'm doing a S0 sleep (mem_sleep = s2idle) or a S3 sleep (mem_sleep = deep). In Ubuntu 18.10 this wasn't an issue, so it's a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 6057 F pulseaudio /dev/snd/pcmC0D0p: rocko 6057 F...m pulseaudio Date: Thu May 23 15:01:44 2019 HibernationDevice: # https://askubuntu.com/questions/1013830/slow-boot-due-to-long-kernel-load-time-18-04 #RESUME=UUID=f48744af-908f-4614-9f8d-1295987f1246 RESUME=none InstallationDate: Installed on 2017-08-16 (644 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-16-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-01-15 (127 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-04-21T22:20:29.600541 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830170 Title: modprobe nvidia fails after suspend/resume cycle Status in linux package in Ubuntu: New Bug description: My hyrbrid intel-nvidia system is set up to use the intel card by default, and the nvidia card power management is done by the kernel (I run a version of bbswitch that does no power management.) After a reboot, the nvidia card on my hyrbrid intel-nvidia system is by default suspended by the kernel, but you can enable it by loading the module with "sudo modprobe nvidia". Using bumblebee, I can run programs on the nvidia card via optirun. However, after a suspend/resume cycle, trying to load the nvidia module fails: $ sudo modprobe nvidia modprobe: ERROR: could not insert 'nvidia': No such device This happens whether I disable bumblebeed.service or not via systemctl. It also happens if I load the nvidia module prior to suspending so the card is active. It also happens whether I'm doing a S0 sleep (mem_sleep = s2idle) or a S3 sleep (mem_sleep = deep). In Ubuntu 18.10 this wasn't an issue, so it's a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 6057 F pulseaudio /dev/snd/pcmC0D0p: ro
[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com
Yes, the amd64 kernels have now built on kernel.ubuntu.com. But newer mainline kernels are no longer appearing there - 4.20.4 and 5.0-rc3 are missing! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811721 Title: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com Status in linux package in Ubuntu: Fix Released Bug description: It appears that mainline kernel builds (on kernel.ubuntu.com) have been failing for amd64 since v4.20.1. Interestingly enough v4.20 was able to build successfully. Note: this also includes 5.0rc builds as well. You can see the build logs here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64 https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64 Looking at the build logs it appears that the kernel and all the in- tree modules build successfully, but the build fails when trying to build the proprietary nvidia kernel modules. With v4.20 building these modules does not appear in the log. Perhaps this build step was added more recently? Here are the relevant lines from the end of the build log for v4.20.2 (which I've also attached): - 2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source- 390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608] II: dkms-build downloading nvidia-390 (nvidia-dkms-390_390.87-0ubuntu4_amd64.deb) --2019-01-10 03:38:13-- http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 91.189.91.23, 2001:67c:1562::16, ... Connecting to us.archive.ubuntu.com (us.archive.ubuntu.com)|91.189.91.26|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 27288 (27K) [application/x-debian-package] Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb' 0K .. .. .. 100% 9.46M=0.003s 2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms- 390_390.87-0ubuntu4_amd64.deb' saved [27288/27288] linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), II: dkms-build building nvidia-390 Creating symlink /home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source -> /home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87 DKMS: add completed. applying patch buildfix_kernel_4.18.patch...patching file conftest.sh patching file nvidia-drm/nvidia-drm-connector.c patching file nvidia-drm/nvidia-drm-encoder.c patching file nvidia-drm/nvidia-drm-helper.h patching file nvidia-drm/nvidia-drm.Kbuild Building module: cleaning build area...(bad exit status: 2) unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic LD=/usr/bin/ld.bfd modules.(bad exit status: 2) Error! Bad return status for module build on kernel: 4.20.1-042001-generic (x86_64) Consult /home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log for more information. debian/scripts/dkms-build: line 121: /home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log: No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1 Thanks! Rob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560
Oops, it was either acpi_osi=! or acpi_osi='Windows 2009' that was causing the problem. I had copied them in to try and get the nvidia card working after resume, but it turns out they aren't needed for the nvidia card to work anyway. Sorry for the noise. ** Changed in: upower (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Invalid Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com
I can build the mainline 4.20.3 kernel locally if I set "do_dkms_nvidia = false" in its 0001-base-packaging.patch. Why would we even want to build the nvidia driver for recent kernels? Even the most up-to-date nvidia drivers rarely compile for -rc kernels, and ubuntu typically has an older version of the nvidia driver anyway (currently nvidia-390 from last August), so kernel build failure seems highly likely to occur if it relies on the nvidia driver building successfully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811721 Title: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com Status in linux package in Ubuntu: Confirmed Bug description: It appears that mainline kernel builds (on kernel.ubuntu.com) have been failing for amd64 since v4.20.1. Interestingly enough v4.20 was able to build successfully. Note: this also includes 5.0rc builds as well. You can see the build logs here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64 https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64 Looking at the build logs it appears that the kernel and all the in- tree modules build successfully, but the build fails when trying to build the proprietary nvidia kernel modules. With v4.20 building these modules does not appear in the log. Perhaps this build step was added more recently? Here are the relevant lines from the end of the build log for v4.20.2 (which I've also attached): - 2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source- 390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608] II: dkms-build downloading nvidia-390 (nvidia-dkms-390_390.87-0ubuntu4_amd64.deb) --2019-01-10 03:38:13-- http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 91.189.91.23, 2001:67c:1562::16, ... Connecting to us.archive.ubuntu.com (us.archive.ubuntu.com)|91.189.91.26|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 27288 (27K) [application/x-debian-package] Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb' 0K .. .. .. 100% 9.46M=0.003s 2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms- 390_390.87-0ubuntu4_amd64.deb' saved [27288/27288] linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), II: dkms-build building nvidia-390 Creating symlink /home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source -> /home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87 DKMS: add completed. applying patch buildfix_kernel_4.18.patch...patching file conftest.sh patching file nvidia-drm/nvidia-drm-connector.c patching file nvidia-drm/nvidia-drm-encoder.c patching file nvidia-drm/nvidia-drm-helper.h patching file nvidia-drm/nvidia-drm.Kbuild Building module: cleaning build area...(bad exit status: 2) unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic LD=/usr/bin/ld.bfd modules.(bad exit status: 2) Error! Bad return status for module build on kernel: 4.20.1-042001-generic (x86_64) Consult /home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log for more information. debian/scripts/dkms-build: line 121: /home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log: No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1 Thanks! Rob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
@dholbert: your lockup looks like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904 (and the upstream bug is https://bugs.freedesktop.org/show_bug.cgi?id=100516). It's a bug in the Intel graphics drivers that unfortunately is present in both kernels 4.10 and 4.11, but should be fixed in 4.12. ** Bug watch added: freedesktop.org Bugzilla #100516 https://bugs.freedesktop.org/show_bug.cgi?id=100516 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I find it absolutely astonishing that a bug that is easy to trigger, can cause data loss, and requires a hard reboot is treated with a lower priority than security bugs. Surely Ubuntu 17.04 should be flagged "not suitable for production machines" until this issue is fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687534] Re: Mainline kernels no longer build due to obsolete compression type bzip2
It's working again, eg http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.11/ ** Changed in: linux (Ubuntu) Status: Triaged => 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/1687534 Title: Mainline kernels no longer build due to obsolete compression type bzip2 Status in linux package in Ubuntu: Fix Released Bug description: From 2017-04-27 onwards, the mainline kernels are failing to build, eg see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/ The error logged is: dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip instead ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1490 F pulseaudio Date: Tue May 2 12:36:11 2017 InstallationDate: Installed on 2017-04-13 (18 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=3f51db63-3e0b-4fe3-86b9-4d5ca0c792d5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687557] [NEW] kernel BUG at linux-4.10.0 swapops.h
Public bug reported: Log attached. I've seen the 4.10 kernel crash at least twice (on two different machines) apparently when trying to handle swap. The system slows down at first and commands like "ps xa" lock up, then the system completely locks up (I couldn't even access a terminal via CTRL-ALT-F1 etc when it happened just now). Note that I have swap partitions rather than swapfiles because I'm running btrfs, which doesn't support a swapfile. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sean 3113 F pulseaudio Date: Tue May 2 16:04:17 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (301 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-20-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ pcie_port_pm=off quiet splash nogpumanager vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-29 (92 days ago) dmi.bios.date: 02/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.21 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.21:bd02/17/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "kernel swap oops" https://bugs.launchpad.net/bugs/1687557/+attachment/4870678/+files/kernel%20swap%20oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687557 Title: kernel BUG at linux-4.10.0 swapops.h Status in linux package in Ubuntu: New Bug description: Log attached. I've seen the 4.10 kernel crash at least twice (on two different machines) apparently when trying to handle swap. The system slows down at first and commands like "ps xa" lock up, then the system completely locks up (I couldn't even access a terminal via CTRL-ALT-F1 etc when it happened just now). Note that I have swap partitions rather than swapfiles because I'm running btrfs, which doesn't support a swapfile. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sean 3113 F pulseaudio Date: Tue May 2 16:04:17 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (301 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-20-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ pcie_port_pm=off quiet splash nogpumanager vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-29 (92 days ago) dmi.bios.date: 02/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.21 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1687534] [NEW] Mainline kernels no longer build due to obsolete compression type bzip2
Public bug reported: >From 2017-04-27 onwards, the mainline kernels are failing to build, eg see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/ The error logged is: dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip instead ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1490 F pulseaudio Date: Tue May 2 12:36:11 2017 InstallationDate: Installed on 2017-04-13 (18 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=3f51db63-3e0b-4fe3-86b9-4d5ca0c792d5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687534 Title: Mainline kernels no longer build due to obsolete compression type bzip2 Status in linux package in Ubuntu: New Bug description: From 2017-04-27 onwards, the mainline kernels are failing to build, eg see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/ The error logged is: dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip instead ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1490 F pulseaudio Date: Tue May 2 12:36:11 2017 InstallationDate: Installed on 2017-04-13 (18 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=3f51db63-3e0b-4fe3-86b9-4d5ca0c792d5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.p
[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x25
Just a note that you can also find the 4.8 kernel (image and headers) at http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D, and if you install the deb files from there, you don't need to enable the yakkety repos. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded to 17.04. It appears that now leaving the system locked for long enough now makes it unable to respond to any input but SysRq. This apepars to be the only relevant bit in `journalctl --boot -1`: BUG: unable to handle kernel NULL pointer dereference at 0018 IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100 CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic #16-Ubuntu Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 99ddb372da00 task.stack: b0ec037dc000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 0018:b0ec037df880 EFLAGS: 00010246 RAX: 99dd0367b880 RBX: 0003 RCX: 0003 RDX: RSI: 99ddb737e000 RDI: 99de4ad9 RBP: b0ec037df8d8 R08: R09: R10: R11: 0001 R12: 99ddc994a000 R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000 FS: 7fd3a0fa7b00() GS:99de5e58() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 000174607000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] ? __alloc_pages_nodemask+0xff/0x260 gen8_alloc_va_range+0x23d/0x470 [i915] i915_vma_bind+0x7e/0x170 [i915] __i915_vma_do_pin+0x2a5/0x450 [i915] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915] ? radix_tree_lookup_slot+0x22/0x50 ? shmem_getpage_gfp+0xf9/0xc10 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x21b/0x4c0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] ? __seccomp_filter+0x67/0x250 do_vfs_ioctl+0xa3/0x610 ? __secure_computing+0x3f/0xd0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7fd39a33a907 RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907 RDX: 76323860 RSI: c0406469 RDI: 000e RBP: 76323860 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: b0ec037df880 CR2: 0018 ---[ end trace 2a4103476767c23b ]--- I walked to my computer 12 minutes later, finding it soft-locked as described above. I realize that this appears somewhat far removed from the real cause of the problem, so please let me know what other data I can provide to facilitate the debugging process. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sraffa 2780 F pulseaudio /dev/snd/controlC0: sraffa 2780 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Mar 30 17:44:00 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640 InstallationDate:
[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x25
How is this only medium priority? It causes data loss, which is rather catastrophic... This might also be related to https://bugs.freedesktop.org/show_bug.cgi?id=100516, which unfortunately isn't going to be fixed until kernel 4.12. ** Bug watch added: freedesktop.org Bugzilla #100516 https://bugs.freedesktop.org/show_bug.cgi?id=100516 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded to 17.04. It appears that now leaving the system locked for long enough now makes it unable to respond to any input but SysRq. This apepars to be the only relevant bit in `journalctl --boot -1`: BUG: unable to handle kernel NULL pointer dereference at 0018 IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100 CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic #16-Ubuntu Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 99ddb372da00 task.stack: b0ec037dc000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 0018:b0ec037df880 EFLAGS: 00010246 RAX: 99dd0367b880 RBX: 0003 RCX: 0003 RDX: RSI: 99ddb737e000 RDI: 99de4ad9 RBP: b0ec037df8d8 R08: R09: R10: R11: 0001 R12: 99ddc994a000 R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000 FS: 7fd3a0fa7b00() GS:99de5e58() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 000174607000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] ? __alloc_pages_nodemask+0xff/0x260 gen8_alloc_va_range+0x23d/0x470 [i915] i915_vma_bind+0x7e/0x170 [i915] __i915_vma_do_pin+0x2a5/0x450 [i915] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915] ? radix_tree_lookup_slot+0x22/0x50 ? shmem_getpage_gfp+0xf9/0xc10 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x21b/0x4c0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] ? __seccomp_filter+0x67/0x250 do_vfs_ioctl+0xa3/0x610 ? __secure_computing+0x3f/0xd0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7fd39a33a907 RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907 RDX: 76323860 RSI: c0406469 RDI: 000e RBP: 76323860 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: b0ec037df880 CR2: 0018 ---[ end trace 2a4103476767c23b ]--- I walked to my computer 12 minutes later, finding it soft-locked as described above. I realize that this appears somewhat far removed from the real cause of the problem, so please let me know what other data I can provide to facilitate the debugging process. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sraffa 2780 F pulseaudio /dev/snd/controlC0: sraffa 2780 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Mar 30
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
It has been fixed for me since kernel 4.0, so yes, I think it can be closed now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627214] Re: Random display flickering on Kernel 4.8 with dual-screen
On the bright side, upstream has ameliorated this issue considerably in drm-intel-nightly and the vanilla 4.9-rc1 kernels. So far the upstream bug has suggested two patches for kernel 4.8.x that reduce the flickering - with those patches, it only occurs a few times a day for me instead of every few seconds or minutes. Maybe we could cherry-pick those patches? ** This bug is no longer a duplicate of bug 1626935 [yakkety] desktop is black and/or flickering after plugging in a second monitor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627214 Title: Random display flickering on Kernel 4.8 with dual-screen Status in linux package in Ubuntu: Confirmed Bug description: The update to linux-image 4.8.0-15-generic has caused both my laptop screen and external monitor screen to flicker at random intervals on my Skylake laptop, making the desktop annoyingly unusable at times. This issue is not present in the 4.7 or earlier kernels. Upstream is aware of the issue: see https://bugs.freedesktop.org/show_bug.cgi?id=97450. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 4715 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 24 07:29:44 2016 HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (81 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-15-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-07-24 (61 days ago) WifiSyslog: dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627214] Re: Random display flickering on Kernel 4.8 with dual-screen
This is *not* a duplicate of bug #1626935. For a start, it occurs whether the monitor is plugged in at reboot or not, and it refers to a different kind of flickering. I believe I've also seen the flickering referred to in that bug, and it's a constant flickering of part or all of the screen, whereas the flickering mentioned here is where the entire laptop screen goes black temporarily, for half a second or sometimes longer, and then returns to normal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627214 Title: Random display flickering on Kernel 4.8 with dual-screen Status in linux package in Ubuntu: Confirmed Bug description: The update to linux-image 4.8.0-15-generic has caused both my laptop screen and external monitor screen to flicker at random intervals on my Skylake laptop, making the desktop annoyingly unusable at times. This issue is not present in the 4.7 or earlier kernels. Upstream is aware of the issue: see https://bugs.freedesktop.org/show_bug.cgi?id=97450. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 4715 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 24 07:29:44 2016 HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (81 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-15-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-07-24 (61 days ago) WifiSyslog: dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627214] Re: Random display flickering on Kernel 4.8 with dual-screen
It's not fixed in the 4.8.0-generic kernel. Additionally, that kernel shows flickering artefact windows when using two monitors, as reported here: https://bugs.freedesktop.org/show_bug.cgi?id=97596 ** Bug watch added: freedesktop.org Bugzilla #97596 https://bugs.freedesktop.org/show_bug.cgi?id=97596 ** 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/1627214 Title: Random display flickering on Kernel 4.8 with dual-screen Status in linux package in Ubuntu: Confirmed Bug description: The update to linux-image 4.8.0-15-generic has caused both my laptop screen and external monitor screen to flicker at random intervals on my Skylake laptop, making the desktop annoyingly unusable at times. This issue is not present in the 4.7 or earlier kernels. Upstream is aware of the issue: see https://bugs.freedesktop.org/show_bug.cgi?id=97450. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 4715 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 24 07:29:44 2016 HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (81 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-15-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-07-24 (61 days ago) WifiSyslog: dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver (and Mir) has
So I can confirm that adding the extra modeline works, eg I now have 2560x1440@60 Hz both appearing in xrandr and working on the laptop monitor using the modeset driver. (There's a separate bug for the modeset driver whereby if you change the mode, eg from 1920x1080 to 2560x1440, the new screen only uses the top 1920x1080 display space - except, curiously, for the unity launcher and top bar - but once I restarted lightdm, the new resolution works fine.) No, I hadn't heard of quilt before. I'll check it out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver (and Mir) has Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
Why isn't this a bug in gcc 6? It doesn't seem right that we have to patch the kernel makefile to get it to build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in dkms package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in dkms source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1574982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver (and Mir) has
Ok, thanks for the info re dpkg-buildpackage. xf86DefModeSet.c is created by hw/xfree86/common/modeline2c.awk. If you run dpkg-buildpackage, you'll find it two places: $ find -name xf86DefModeSet.c ./build-main/hw/xfree86/common/xf86DefModeSet.c ./build-udeb/hw/xfree86/common/xf86DefModeSet.c xf86DefModeSet.c is built using the files hw/xfree86/common/vesamodes and hw/xfree86/common/extramodes. extramodes is modified in the build process by debian/patches/001_fedora_extramodes.patch, so editing extramodes directly means the patch and therefore build fails. The packages do build if I add my missing modes to vesamodes and because all the modes are combined into the one xf86DefModeSet.c, I assume it'll work for testing purposes. dpkg-buildpackage builds a whole bunch of debs: xserver-common_1.18.4-1ubuntu6_all.deb xserver-xorg-core-udeb_1.18.4-1ubuntu6_amd64.udeb xserver-xephyr_1.18.4-1ubuntu6_amd64.deb xserver-xorg-dev_1.18.4-1ubuntu6_amd64.deb xserver-xorg-core_1.18.4-1ubuntu6_amd64.deb xserver-xorg-legacy_1.18.4-1ubuntu6_amd64.deb xserver-xorg-core-dbg_1.18.4-1ubuntu6_amd64.deb xserver-xorg-xmir_1.18.4-1ubuntu6_all.deb It looks like installing xserver-common and xserver-xorg-core should be sufficient to test my changes, is that correct or do I need the udeb or any of the other packages? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver (and Mir) has Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver (and Mir) has
>From https://bugs.freedesktop.org/show_bug.cgi?id=97163#c15, I think
it's just a matter of some modelines missing from the xf86DefaultModes
array in xf86DefModeSet.c, eg I suspect that adding this:
/* 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz */
{MODEPREFIX, 312250, 2560,2752,3024,3488,0, 1440,1443,1448,1493,0,
V_NHSYNC | V_PVSYNC, MODESUFFIX},
will give me my missing 2560x1440 mode. My xserver builds but I still
haven't figured out how to get it to run, so I can't test it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1606103
Title:
modeset driver is missing some modes that the intel driver (and Mir)
has
Status in linux package in Ubuntu:
Invalid
Status in xorg-server package in Ubuntu:
Confirmed
Status in xorg-server package in Debian:
New
Bug description:
My laptop's 4K screen (Dell XPS 15 9550) has these resolutions,
according to the intel driver:
3840x2160 60.00 +
3200x1800 60.00
2880x1620 60.00
2560x1440 60.00*
2048x1536 60.00
1920x1440 60.00
1856x1392 60.01
1792x1344 60.01
2048x1152 60.00
1920x1200 59.95
1920x1080 60.0059.93
1600x1200 60.00
1680x1050 59.9559.88
1600x1024 60.17
1400x1050 59.98
1600x900 60.00
1280x1024 60.02
1440x900 59.89
1280x960 60.00
1368x768 60.00
1360x768 59.8059.96
1152x864 60.00
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.3256.25
864x486 60.00
640x480 59.94
720x405 60.00
640x360 60.00
But with the modeset driver, it detects these resolutions:
3840x2160 60.00*+
2048x1536 60.00
1920x1440 60.00
1856x1392 60.01
1792x1344 60.01
1920x1200 59.95
1920x1080 59.93
1600x1200 60.00
1680x1050 59.9559.88
1600x1024 60.17
1400x1050 59.98
1280x1024 60.02
1440x900 59.89
1280x960 60.00
1360x768 59.8059.96
1152x864 60.00
1024x768 60.0460.00
960x720 60.00
928x696 60.05
896x672 60.01
960x600 60.00
960x540 59.99
800x600 60.0060.3256.25
840x525 60.0159.88
800x512 60.17
700x525 59.98
640x512 60.02
720x450 59.89
640x480 60.0059.94
680x384 59.8059.96
576x432 60.06
512x384 60.00
400x300 60.3256.34
320x240 60.05
It seems to be picking up some extra super-low resolutions (like
320x240) but not the higher 16:9 resolutions. I normally run it at
2560x1440, because the native resolution is too high with an external
monitor attached at 1980x1080, but I can't do this with the modeset
driver.
I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23
/intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver-
on-x/, although note that there are several inaccuracies in that post
- there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video-
intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you
correct the typo, and I couldn't use ubuntu-bug to report this against
xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't
exist.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg-server-source (not installed)
Uname: Linux 4.6.4-040604-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
BootLog:
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Jul 25 11:09:00 2016
DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed
nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed
nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: Dell HD Graphics 530 [1028:06e4]
InstallationDate: Installed on 2016-07-04 (20 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint:
[Kernel-packages] [Bug 1627214] [NEW] Random display flickering on Kernel 4.8 with dual-screen
Public bug reported: The update to linux-image 4.8.0-15-generic has caused both my laptop screen and external monitor screen to flicker at random intervals on my Skylake laptop, making the desktop annoyingly unusable at times. This issue is not present in the 4.7 or earlier kernels. Upstream is aware of the issue: see https://bugs.freedesktop.org/show_bug.cgi?id=97450. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 4715 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 24 07:29:44 2016 HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (81 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-15-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-07-24 (61 days ago) WifiSyslog: dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1627214 Title: Random display flickering on Kernel 4.8 with dual-screen Status in linux package in Ubuntu: New Bug description: The update to linux-image 4.8.0-15-generic has caused both my laptop screen and external monitor screen to flicker at random intervals on my Skylake laptop, making the desktop annoyingly unusable at times. This issue is not present in the 4.7 or earlier kernels. Upstream is aware of the issue: see https://bugs.freedesktop.org/show_bug.cgi?id=97450. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-15-generic 4.8.0-15.16 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 4715 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 24 07:29:44 2016 HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7 InstallationDate: Installed on 2016-07-04 (81 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-15-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-15-generic N/A linux-backports-modules-4.8.0-15-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-07-24 (61 days ago) WifiSyslog: dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about t
[Kernel-packages] [Bug 1567417] Re: WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
I tried 4.8-rc4 and I didn't see the skl_update_other_pipe_wm warning any more. Unfortunately there are regular video glitches and suspend/resume is broken, so the 4.8 kernel isn't usable yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567417 Title: WARN_ON(!wm_changed) skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm using a new Skylake Thinkpad T460s with and external monitor connected via Displayport and Ubuntu 16.04 and the latest kernel as of today: Linux test 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux X will from time to time lock up when the computer is left idle for a long time and both displays (laptop and external) go to sleep and then woken up. Apr 7 08:00:49 test kernel: [9.950929] [ cut here ] Apr 7 08:00:49 test kernel: [9.950950] WARNING: CPU: 0 PID: 214 at /build/linux-YiIlnA/linux-4.4.0/ubuntu/i915/intel_pm.c:3572 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() Apr 7 08:00:49 test kernel: [9.950951] WARN_ON(!wm_changed) Apr 7 08:00:49 test kernel: [9.950972] Modules linked in: btusb btrtl btbcm btintel bluetooth binfmt_misc nls_iso8859_1 arc4 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm thinkpad_acpi intel_rapl x86_pkg_temp_thermal nvram intel_powerclamp snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi iwlmvm snd_seq joydev snd_seq_device input_leds mac80211 snd_timer serio_raw snd rtsx_pci_ms memstick soundcore iwlwifi cfg80211 mei_me mei tpm_crb mac_hid shpchp kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg hid_microsoft dm_crypt hid_generic usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul i915_bpo aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_ips i2c_algo_bit drm_kms_helper e1000e syscop yarea sysfillrect psmouse sysimgblt ptp fb_sys_fops pps_core drm nvme rtsx_pci wmi video fjes Apr 7 08:00:49 test kernel: [9.950980] CPU: 0 PID: 214 Comm: plymouthd Not tainted 4.4.0-17-generic #33-Ubuntu Apr 7 08:00:49 test kernel: [9.950981] Hardware name: LENOVO 20F9CTO1WW/20F9CTO1WW, BIOS N1CET40W (1.08 ) 03/09/2016 Apr 7 08:00:49 test kernel: [9.950982] 0286 39cb6999 880502bc3618 813e8123 Apr 7 08:00:49 test kernel: [9.950983] 880502bc3660 c0343c70 880502bc3650 8107fe12 Apr 7 08:00:49 test kernel: [9.950984] 880502da8000 880501f79d9c 880502dab000 880508186b78 Apr 7 08:00:49 test kernel: [9.950984] Call Trace: Apr 7 08:00:49 test kernel: [9.950988] [] dump_stack+0x63/0x90 Apr 7 08:00:49 test kernel: [9.950990] [] warn_slowpath_common+0x82/0xc0 Apr 7 08:00:49 test kernel: [9.950991] [] warn_slowpath_fmt+0x5c/0x80 Apr 7 08:00:49 test kernel: [9.951002] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951010] [] skl_update_wm+0x186/0x5f0 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951023] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951034] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951048] [] haswell_crtc_enable+0x321/0x8c0 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951061] [] ? intel_finish_crtc_commit+0xe/0x10 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951072] [] ? drm_atomic_helper_commit_planes_on_crtc+0x154/0x270 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951085] [] intel_atomic_commit+0x5dd/0xdb0 [i915_bpo] Apr 7 08:00:49 test kernel: [9.951101] [] ? drm_atomic_check_only+0x18e/0x590 [drm] Apr 7 08:00:49 test kernel: [9.951109] [] drm_atomic_commit+0x37/0x60 [drm] Apr 7 08:00:49 test kernel: [9.951113] [] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951121] [] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm] Apr 7 08:00:49 test kernel: [9.951125] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951128] [] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951131] [] drm_fb_helper_hotplug_event+0xd2/0x120 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951134] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x56/0x80 [drm_kms_helper] Apr 7 08:00:49 test kernel: [9.951136] [] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] Apr 7 08:00:49 test
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver had
Just FYI, I proposed a patch at https://bugs.freedesktop.org/show_bug.cgi?id=97163. I can't test it beyond checking it compiles without warnings because when I built my own xserver xorg-server_1.18.4 and installed it to the default prefix (/usr/local/bin), X crashed. This was without any changes to the source returned by apt-get source command, so it's not due to code changes; I'm not sure if this is because I need to build more modules or whether I need to install to /usr/bin, or something else entirely. Does anyone have any hints? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver had Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver had
Is that the right place? The modesetting driver is incorporated into xserver now, so the versions it offers to report against are very old. I reported it anyway (against git) at https://bugs.freedesktop.org/show_bug.cgi?id=97163, in case it helps. ** Bug watch added: freedesktop.org Bugzilla #97163 https://bugs.freedesktop.org/show_bug.cgi?id=97163 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver had Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver had
Thanks for the info. So it turns out that the problem is that the modesetting driver is pruning these modelines because it thinks their vertical refresh is greater than the max vrefresh. The function in question is hw/xfree86/drivers/modesetting/drmmode_display.c#add_gtf_modes(), and it is calculating refresh rates between 65 and 85 but thinks that the max vrefresh is 60.58 because of these lines: max_vrefresh = max(max_vrefresh, 60.0); max_vrefresh *= (1 + SYNC_TOLERANCE); However, I can see from the MonPtr variable passed to hw/xfree86/modes/xf86Modes.c#xf86ValidateModesSync() that the driver has figured out a range of 56.25 to 120 for this screen, so my guess is that it shouldn't be restricting the max to 60 plus 1% in add_gtf_modes(). Looking at get_modes(), which calls add_gtf_modes(), it is also extracting a MonPtr variable from the EDID, so perhaps it could pass this pointer to add_gtf_modes() and add_gtf_modes() could use the actual maximum vertical refresh for the monitor instead of locking it to 60. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver had Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed
[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver had
Another Ubuntu Perthian! Excellent! I checked another laptop and the kernel only listed the native resolution of the screen on that as well, so perhaps the issue is in xserver/modeset after all. But out of curiosity, what role is the kernel supposed to take here? It does list all the modes for my external monitor, just not for the laptop screens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver had Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice.
[Kernel-packages] [Bug 1606103] Re: modeset driver does not detect all screen resolutions
The output is the same for the 4.7.0 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver does not detect all screen resolutions Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.6.4-040604-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to yakkety on
[Kernel-packages] [Bug 1606103] Re: modeset driver does not detect all screen resolutions
This is the output for kernel 4.6.4-040604-generic (running back on Ubuntu 16.04, but I guess that shouldn't make any difference if we're just reading the kernel info): /sys/class/drm/card0-eDP-1/modes:3840x2160 (There's a bunch of other modes but they are all for the various resolutions on the HDMI screen). So it looks like it's just seeing one mode for the laptop screen, the native resolution. Does that mean it's inventing a bunch of modes anyway - just not the right ones? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver does not detect all screen resolutions Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the
[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)
Does this bug happen for people after a USB drive has spun down and the computer tries to access it? My USB freezing issue goes away if I disable UAS for a particular drive. It works fine with UAS until it spins down but the USB subsystem freezes when it tries to spin it up, requiring me to reboot the PC and power cycle the drive. To disable UAS for the drive, first find its identifier with the lsbusb command. For example mine looks like this, ie with identifier 1058:1230: Bus 002 Device 003: ID 1058:1230 Western Digital Technologies, Inc. My Book Add a file like /etc/modprobe.d/usb_storage.conf with the contents and the appropriate identifier: options usb_storage quirks=1058:1230:u and run "sudo update-initramfs -u -k all" and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1413440 Title: USB stops working after a while (xhci_hcd :00:14.0: Timeout while waiting for setup device command) Status in System76: Triaged Status in linux package in Ubuntu: Triaged Bug description: On my laptop the kernel will sometimes drop the USB hub. After this, the laptop doesn't recognise any device plugged in to the USB ports - plugging and unplugging any device I've tried into any of the USB ports produces no response, not even dmesg entries. Strangely this also applies to bluetooth - it no longer works once USB has dropped (possibly the module is hung of the bus internally). Once this has happened only a reboot fixes it; I've not managed to find any combination of module unload/reload or suspend cycles to reinitialise things correctly. Relevant snippet of dmesg: [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe the host is dead [48838.079742] xhci_hcd :00:14.0: Abort command ring failed [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device command [48838.079806] sched: RT throttling activated [48838.079981] usb 1-1: USB disconnect, device number 16 [48838.079985] usb 1-1.2: USB disconnect, device number 18 [48838.079987] usb 1-1.2.3: USB disconnect, device number 19 [48838.080285] usb 1-1.2.4: USB disconnect, device number 20 [48838.111892] usb 1-1.4: USB disconnect, device number 17 [48838.191292] usb 1-4: USB disconnect, device number 6 [48838.267550] usb 1-10: USB disconnect, device number 8 [48838.282968] usb 2-1: device not accepting address 8, error -62 [48838.282983] usb 2-1: USB disconnect, device number 8 [48838.282986] usb 2-1.2: USB disconnect, device number 9 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.18.0-9-generic 3.18.0-9.10 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 4255 F pulseaudio /dev/snd/controlC0: chris 4255 F pulseaudio CRDA: country AU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (3, 23), (N/A) (5250 - 5330 @ 40), (3, 23), (0 ms), DFS (5735 - 5835 @ 40), (3, 30), (N/A) CurrentDesktop: Unity Date: Thu Jan 22 12:59:27 2015 InstallationDate: Installed on 2013-08-06 (533 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Galago UltraPro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd break=mount RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.141 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago UltraPro dmi.board.vendor: System76, Inc. dmi.board.version: galu1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc, dmi.chassis.version: galu1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1413440/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
Cool, I see the patch is in 4.0-rc3 now (commit 6d65261a09adaa374c05de807f73a144d783669e). I applied it to 3.19.1-generic and can confirm it works as advertised. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Triaged Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
I don't like the idea of eCryptfs supporting the clone ioctl by default. It would allow an attacker to discover that the files (the original and the clone) are the same. I agree with that reasoning. In any case, I think that the btrfs clone operation should be disallowed in ecryptfs as a matter of urgency (upstream as well), since it can result in data loss, which is far worse than the (presumably small in practice) disk space savings available though using the clone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
As a follow-up to comment #16: generally attempting to clone a file in
a non-ecryptfs folder into a mounted ecryptfs folder appears to succeed
but in fact creates a zero-length invalid target file, but going the
other way (cloning from the mounted ecryptfs folder into the non-
ecryptfs folder) fails as it should. (Both cp --reflink=auto and glib's
file_copy_fallback try a clone operation and then try a non-clone
operation if this fails, so this second case is fine.)
The attached script demonstrates both cases by creating a mounted
ecryptfs system in /tmp/ecryptfs-test and using the folder 'private' to
hold the 'lower' encrypted ecryptfs files and the folder 'plaintext' as
the 'higher' mounted ecryptfs folder and then trying the clone operation
in both directions. ( /tmp must be on a btrfs partition and you need at
least ecryptfs-utils installed but you don't need an encrypted home
folder.)
The btrfs_ioctl_clone command (in fs/btrfs/ioctl.c in the kernel source)
is designed to only perform a clone if the source and dest files have
the same VFS mountpoint and to fail with EXDEV (invalid cross-device
link) if they don't:
ret = -EXDEV;
if (src_file.file-f_path.mnt != file-f_path.mnt)
goto out_fput;
When trying to clone from the 'plaintext' folder into /tmp/ecryptfs-
test, this test fails (the mountpoints are represented by two different
dentries, '@' and '/').
However, when cloning into the 'plaintext' folder, btrfs_ioctl_clone is
actually being asked to clone using the 'lower' ecryptfs file as the
target (ie the target points to the 'private' folder, not the
'plaintext' folder), so the test passes. This is obviously wrong -
ecryptfs is designed so that the information gets directed to the
'plaintext' folder, intercepted in the kernel, and stored encrypted
instead in the 'private' folder.
To demonstrate this, I added this code just before the test:
{
#define BUFLEN 256
char src_path[BUFLEN],dest_path[BUFLEN];
int i;
for (i=0;iBUFLEN;++i) src_path[i]=dest_path[i]=0;
printk(KERN_INFO btrfs reflink src: %s [mnt %s], dest: %s [mnt %s]\n,
dentry_path_raw(src_file.file-f_path.dentry, src_path, BUFLEN),
src_file.file-f_path.mnt-mnt_root-d_iname,
dentry_path_raw(file-f_path.dentry, dest_path, BUFLEN),
file-f_path.mnt-mnt_root-d_iname
);
}
With that code included in the kernel, the syslog shows something like
this after running the attached test script:
... btrfs reflink src: /@/tmp/ecryptfs-test/test [mnt @], dest: /@/tmp
/ecryptfs-test/private/ECRYPTFS_FNEK_ENCRYPTED... [mnt @]
ie the target file passed to btrfs_ioctl_clone is the 'lower' file in
'private'. (Note that after the clone, trying to access this file
results in an I/O error.)
I checked the cp code, and it calls:
return ioctl (dest_fd, BTRFS_IOC_CLONE, src_fd);
I used readlink to get the file path for dest_fd from
/proc/self/fd/file desriptor, and it returned /tmp/ecryptfs-
test/plaintext/test, so desc_fd in the cp command is pointing to the
correct path for the 'higher' file.
My guess is that ecryptfs intercepts this 'higher' path and converts it
to the 'lower' path before it gets passed through to btrfs, but it
should just do a pass-through for the btrfs clone operation.
** Attachment added: Script demonstrating the bug
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1305335/+attachment/4325528/+files/test-reflink.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1305335
Title:
Cutting or copying files on btrfs to ecryptfs results in data loss
Status in eCryptfs:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in nautilus package in Ubuntu:
Confirmed
Bug description:
I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I
used btrfs as the filesystem.
I set up a Private folder usying ecryptfs-setup-private.
I copied a few folders into the Private folder, and the entire
directory structure and subfolders are copied, including the files
themselves, yet every file contains 0 bytes.
However, I can create and save new files in the Private directory.
Also, folders and files can be correctly copied if I use the command line cp
-R.
Thanks,
Damon
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 9 18:12:56 2014
EcryptfsInUse: Yes
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order'
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group',
'permissions', 'mime_type', 'where']
InstallationDate: Installed on 2014-04-05 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr -
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
In case anyone still reads bugzilla.kernel.org, I reported this at https://bugzilla.kernel.org/show_bug.cgi?id=93691. ** Bug watch added: Linux Kernel Bug Tracker #93691 http://bugzilla.kernel.org/show_bug.cgi?id=93691 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
I think it is still useful for ecryptfs to support the btrfs clone ioctl for the case where both source and target higher files are in the same ecryptfs mount, since this saves disk space. We might be able to handle this in fs/ecryptfs/file.c#ecryptfs_unlocked_ioctl, which gets passed the btrfs ioctrl clone command along with the the higher target file. It unconditionally converts it to the lower file and then passes it down to btrfs: struct file *lower_file = ecryptfs_file_to_lower(file); ... if (lower_file-f_op-unlocked_ioctl) rc = lower_file-f_op-unlocked_ioctl(lower_file, cmd, arg); Adding code here that returns failure if the command is BTRFS_IOC_CLONE makes the cp --reflink=always command fail. (cp --reflink=auto then works because cp detects the failure and does a non-clone copy, and the same should go for the glib file copy). However, note that: 1. When it fails to clone, ecryptfs still creates a valid but zero-byte file after the failed clone operation, so ecryptfs should probably remove this when it returns fail for the clone operation. 2. It shouldn't fail if the source and target files are both inside the same ecryptfs mount. 3. Do symlinks affect it, eg if the target is a symlink outside the ecryptfs mount that points to the higher ecryptfs file? 4. ecryptfs_compat_ioctl might possibly be affected as well since it does the same thing as ecryptfs_unlocked_ioctl. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
ecryptfs_unlocked_ioctl gets passed the (higher) target file struct as the first argument, the command as the second, and the source file descriptor as the third argument. It looks like the source file descriptor has already been converted to the lower file if it is associated with a higher file inside an ecryptfs mount. This makes it harder to compare the mountpoints of the source and target to see if the clone should be allowed - you'd need to figure out if the source file descriptor is associated with a higher file then compare that higher file with the (higher) target file to see if they have the same mountpoint. I'm not sure how to do that - there aren't many comments in the ecryptfs 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/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
I checked the mainline 3.11 kernel and it has the bug (as well as 3.13, 3.18 and 3.19, based on the other comments), so I would say it is not a regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
@whoop: If you mean that the thumbnail file length is correct but the image file is zero bytes, the reason is that the thumbnail file isn't copied from the non-ecryptfs folder to the ecryptfs folder. Instead, the system stores thumbnails in ~/.cache/thumbnails. So it creates a new thumbnail file for the newly-copied zero-byte image file in the ecryptfs folder, meaning the thumbnail file itself is valid. But the system tries to generate the thumbnail image from the zero-byte image file, which means that the thumbnail image is broken and so it appears broken in nautilus. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
Just to note: in the example commands above, of course, /home needs to be write-accessible to the current user, or you need to use a command like su root -c echo test /home/test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
The 3.19 kernel still has the problem. You can reproduce it by copying a test file from say /home into an encrypted home directory using --reflink: echo test /home/test cp --reflink=always /home/test ~ ls -l ~/test # This shows 0 bytes This command, however, copies the file correctly, assuming you haven't aliased cp to use reflink: echo test /home/test cp /home/test ~ ls -l ~/test # This shows 5 bytes nautilus is using the g_local_file_copy library command in glib, which since automatically applies reflink since 2.36.4 (libglib2.0-bin is at 2.43.4-1 in Vivid). See the comment at http://upstream.rosalinux.ru/changelogs/glib/2.36.4/changelog.html, where it lists Btrfs clone/reflink ioctl support in g_local_file_copy as one of the changes. So one solution would seem to be to modify the copy functionality to disable reflink (or disallow the copy) if it detects it is copying into a mounted ecryptfs directory (eg using /proc/mounts) from a directory that is not in the same mount. Presumably ecryptfs intercepts the copy request, so perhaps the check should be done in ecryptfs? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1305335] Re: Cutting or copying files on btrfs to ecryptfs results in data loss
** 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/1305335 Title: Cutting or copying files on btrfs to ecryptfs results in data loss Status in eCryptfs: Confirmed Status in linux package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: I've installed a fresh copy of 14.04 beta 2 on a brand-new SSD. I used btrfs as the filesystem. I set up a Private folder usying ecryptfs-setup-private. I copied a few folders into the Private folder, and the entire directory structure and subfolders are copied, including the files themselves, yet every file contains 0 bytes. However, I can create and save new files in the Private directory. Also, folders and files can be correctly copied if I use the command line cp -R. Thanks, Damon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 18:12:56 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-05 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1305335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
@jondee: those are the intel pstate governors. You should be able to confirm this using the cpufreq-info command. If you disable intel pstate and reboot you should get the option of using the other governors (like ondemand) - see http://askubuntu.com/questions/501840/ubuntu-14-04-used-too-much- processor-after-latest-updatest, except you want to use intel_pstate=disable instead of intel_pstate=enable. I recommend sticking with intel pstate, though, as it appears to use less power and give better performance. That's why they developed it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in System76: New Status in linux package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2]
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
@Paul Gear: you could try 3.18-rc6 from http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.18-rc6-vivid/, it works fine with utopic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in System76: New Status in linux package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0 [82218.556278] [81787c3c] ret_from_fork+0x7c/0xb0
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
I just experienced the bug in 3.18-rc3. ** Tags added: bug-exists-upstream ** 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/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0 [82218.556278] [81787c3c] ret_from_fork+0x7c/0xb0 [82218.556280] [81094a10] ?
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
Re 3.18-rc3, I take it back - I was looking at an old log entry. I did experience a complete system freeze that required a hard reset, but I don't think it managed to record the error that caused it in the syslog. ** Tags removed: 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/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10]
[Kernel-packages] [Bug 1384342] Re: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang
FYI, the 3.17.2 kernel still has the bug. I haven't tried 3.18-rcX yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384342 Title: kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: I am fairly frequently (maybe once every 2 days) seeing screen lockups. The system is fine, and then screen locks up. mouse is still movable and even changes icon based on content under it (ie mouse over link changes to pointing hand). Programs are still running (often this occurs during a google hangout, and the hangout, audio and mic seem to work fine). Today when this happened I had more patience and hit ctrl-alt-f1, and then subsequently saw that dmesg had: [82218.556025] [ cut here ] [82218.556074] WARNING: CPU: 0 PID: 8799 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]() [82218.556095] Modules linked in: xt_conntrack ipt_REJECT overlayfs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep binfmt_misc dm_crypt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dm_multipath scsi_dh coretemp kvm_intel kvm arc4 joydev iwldvm mac80211 serio_raw btusb bluetooth pcmcia 6lowpan_iphc thinkpad_acpi snd_seq_midi snd_seq_midi_event nvram snd_hda_codec_conexant snd_hda_codec_generic r852 sm_common lpc_ich nand snd_rawmidi nand_ecc nand_bch snd_hda_intel bch nand_ids snd_hda_controller snd_hda_codec snd_hwdep mtd snd_seq iwlwifi r592 memstick snd_pcm [82218.556112] yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_seq_device shpchp snd_timer mei_me mei snd soundcore mac_hid parport_pc ppdev tp_smapi(OE) thinkpad_ec(OE) lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid psmouse firewire_ohci ahci libahci firewire_core sdhci_pci sdhci crc_itu_t i915 wmi e1000e i2c_algo_bit drm_kms_helper video drm ptp pps_core pata_acpi [last unloaded: ipmi_msghandler] [82218.556114] CPU: 0 PID: 8799 Comm: kworker/0:1 Tainted: GW OE 3.16.0-23-generic #30-Ubuntu [82218.556115] Hardware name: LENOVO 7417CTO/7417CTO, BIOS 7UET94WW (3.24 ) 10/17/2012 [82218.556119] Workqueue: events console_callback [82218.556122] 0009 880016a3faf8 8177fcbc [82218.556123] 880016a3fb30 8106fd8d 880035a5a000 [82218.556124] 880035948210 880035826800 880035826800 880016a3fb40 [82218.556125] Call Trace: [82218.556130] [8177fcbc] dump_stack+0x45/0x56 [82218.556133] [8106fd8d] warn_slowpath_common+0x7d/0xa0 [82218.556135] [8106fe6a] warn_slowpath_null+0x1a/0x20 [82218.556153] [c015dffc] intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915] [82218.556156] [810b9590] ? prepare_to_wait_event+0x100/0x100 [82218.556175] [c0160ac3] intel_crtc_disable_planes+0x33/0x1c0 [i915] [82218.556177] [81784e5b] ? __ww_mutex_lock+0x1b/0xb0 [82218.556196] [c0160ca1] i9xx_crtc_disable+0x51/0x3f0 [i915] [82218.556220] [c0162457] intel_crtc_update_dpms+0x67/0xa0 [i915] [82218.556237] [c0166ac9] intel_connector_dpms+0x59/0x70 [i915] [82218.556245] [c00c4901] drm_fb_helper_dpms.isra.5+0xc1/0x100 [drm_kms_helper] [82218.556251] [c00c4971] drm_fb_helper_blank+0x31/0x90 [drm_kms_helper] [82218.556254] [81415d47] fb_blank+0x57/0xc0 [82218.556256] [8140c87b] fbcon_blank+0xfb/0x300 [82218.556258] [8108b4a2] ? __queue_delayed_work+0x182/0x1c0 [82218.556259] [8108b7b9] ? try_to_grab_pending+0xa9/0x160 [82218.556262] [8107cbdb] ? lock_timer_base.isra.34+0x2b/0x50 [82218.556264] [8107dd1f] ? try_to_del_timer_sync+0x4f/0x70 [82218.556266] [81497ba3] do_blank_screen+0x1d3/0x280 [82218.556267] [8149a348] console_callback+0x68/0x160 [82218.556269] [8108d8e2] process_one_work+0x182/0x4e0 [82218.556270] [8108dcab] worker_thread+0x6b/0x6a0 [82218.556272] [8178294d] ? __schedule+0x39d/0x890 [82218.556273] [8108dc40] ? process_one_work+0x4e0/0x4e0 [82218.556275] [81094aeb] kthread+0xdb/0x100 [82218.556277] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0 [82218.556278] [81787c3c] ret_from_fork+0x7c/0xb0 [82218.556280] [81094a10] ? kthread_create_on_node+0x1c0/0x1c0
[Kernel-packages] [Bug 1380444] Re: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk
The initial crash appears to be a UAS issue. Disabling UAS for this particular device with this in the file /etc/modprobe.d/usb-storage.conf stops the initial uas error and the resulting kernel crash: options usb-storage quirks=1058:1230:u Instead, the drive wakes up as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380444 Title: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: In Ubuntu 14.10, my laptop locks up completely when trying to wake my WD 1230 USB3 external hard drive from its default 10-minute standby. The system tries to wake up the drive, which is unsuccessful, and after a few seconds uas_eh_abort_handler gets called. Shortly after this the NULL pointer dereference occurs in xhci_alloc_streams or xhci_check_streams_endpoint (most times the NULL pointer dereference error doesn't even get persisted to disk, so there may be other points where it occurs). Not long after this the laptop locks up completely and both it and the hard drive have to be power-cycled. I can put the drive manually into and out of standby using hdparm, so I guess there are two problems: one which makes the drive crash (ie it must crash because it needs to be power cycled) and the other being the NULL pointer dereference and complete kernel lockup. The last good kernel was 3.15-rc4. All kernels since since have this problem, including the latest upstream kernel. I did a git bisect, which says: The merge base 6d4596905b65bf4c63c1a008f50bf385fa49f19b is bad. This means the bug has been fixed between 6d4596905b65bf4c63c1a008f50bf385fa49f19b and [89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd] I have reported this upstream at https://bugzilla.kernel.org/show_bug.cgi?id=85741. More details including the logs showing the error ocurring are there. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko F pulseaudio CurrentDesktop: Unity Date: Mon Oct 13 10:15:41 2014 HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a InstallationDate: Installed on 2014-02-08 (246 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-22-generic root=UUID=3e785733-7f93-4ea8-8cdd-c42606029905 ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-04 (8 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1380444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380444] Re: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk
Note that just blacklisting the uas module (blacklist uas in a conf file in /etc/modprobe.d) stops the drive from ever mounting, even though the usb subsystem sees it being attached. The discussion at this link appears to be related to this issue: https://bbs.archlinux.org/viewtopic.php?id=183190p=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380444 Title: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: In Ubuntu 14.10, my laptop locks up completely when trying to wake my WD 1230 USB3 external hard drive from its default 10-minute standby. The system tries to wake up the drive, which is unsuccessful, and after a few seconds uas_eh_abort_handler gets called. Shortly after this the NULL pointer dereference occurs in xhci_alloc_streams or xhci_check_streams_endpoint (most times the NULL pointer dereference error doesn't even get persisted to disk, so there may be other points where it occurs). Not long after this the laptop locks up completely and both it and the hard drive have to be power-cycled. I can put the drive manually into and out of standby using hdparm, so I guess there are two problems: one which makes the drive crash (ie it must crash because it needs to be power cycled) and the other being the NULL pointer dereference and complete kernel lockup. The last good kernel was 3.15-rc4. All kernels since since have this problem, including the latest upstream kernel. I did a git bisect, which says: The merge base 6d4596905b65bf4c63c1a008f50bf385fa49f19b is bad. This means the bug has been fixed between 6d4596905b65bf4c63c1a008f50bf385fa49f19b and [89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd] I have reported this upstream at https://bugzilla.kernel.org/show_bug.cgi?id=85741. More details including the logs showing the error ocurring are there. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko F pulseaudio CurrentDesktop: Unity Date: Mon Oct 13 10:15:41 2014 HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a InstallationDate: Installed on 2014-02-08 (246 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-22-generic root=UUID=3e785733-7f93-4ea8-8cdd-c42606029905 ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-04 (8 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1380444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380444] Re: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk
The regression is still in 3.17.1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380444 Title: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: In Ubuntu 14.10, my laptop locks up completely when trying to wake my WD 1230 USB3 external hard drive from its default 10-minute standby. The system tries to wake up the drive, which is unsuccessful, and after a few seconds uas_eh_abort_handler gets called. Shortly after this the NULL pointer dereference occurs in xhci_alloc_streams or xhci_check_streams_endpoint (most times the NULL pointer dereference error doesn't even get persisted to disk, so there may be other points where it occurs). Not long after this the laptop locks up completely and both it and the hard drive have to be power-cycled. I can put the drive manually into and out of standby using hdparm, so I guess there are two problems: one which makes the drive crash (ie it must crash because it needs to be power cycled) and the other being the NULL pointer dereference and complete kernel lockup. The last good kernel was 3.15-rc4. All kernels since since have this problem, including the latest upstream kernel. I did a git bisect, which says: The merge base 6d4596905b65bf4c63c1a008f50bf385fa49f19b is bad. This means the bug has been fixed between 6d4596905b65bf4c63c1a008f50bf385fa49f19b and [89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd] I have reported this upstream at https://bugzilla.kernel.org/show_bug.cgi?id=85741. More details including the logs showing the error ocurring are there. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko F pulseaudio CurrentDesktop: Unity Date: Mon Oct 13 10:15:41 2014 HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a InstallationDate: Installed on 2014-02-08 (246 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-22-generic root=UUID=3e785733-7f93-4ea8-8cdd-c42606029905 ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-04 (8 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1380444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1380444] [NEW] xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk
Public bug reported: In Ubuntu 14.10, my laptop locks up completely when trying to wake my WD 1230 USB3 external hard drive from its default 10-minute standby. The system tries to wake up the drive, which is unsuccessful, and after a few seconds uas_eh_abort_handler gets called. Shortly after this the NULL pointer dereference occurs in xhci_alloc_streams or xhci_check_streams_endpoint (most times the NULL pointer dereference error doesn't even get persisted to disk, so there may be other points where it occurs). Not long after this the laptop locks up completely and both it and the hard drive have to be power-cycled. I can put the drive manually into and out of standby using hdparm, so I guess there are two problems: one which makes the drive crash (ie it must crash because it needs to be power cycled) and the other being the NULL pointer dereference and complete kernel lockup. The last good kernel was 3.15-rc4. All kernels since since have this problem, including the latest upstream kernel. I did a git bisect, which says: The merge base 6d4596905b65bf4c63c1a008f50bf385fa49f19b is bad. This means the bug has been fixed between 6d4596905b65bf4c63c1a008f50bf385fa49f19b and [89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd] I have reported this upstream at https://bugzilla.kernel.org/show_bug.cgi?id=85741. More details including the logs showing the error ocurring are there. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko F pulseaudio CurrentDesktop: Unity Date: Mon Oct 13 10:15:41 2014 HibernationDevice: RESUME=UUID=ca164267-edcd-4d3c-b325-acbd60802e7a InstallationDate: Installed on 2014-02-08 (246 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) MachineType: Dell Inc. Dell System XPS L502X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-22-generic root=UUID=3e785733-7f93-4ea8-8cdd-c42606029905 ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-22-generic N/A linux-backports-modules-3.16.0-22-generic N/A linux-firmware 1.135 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-04 (8 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380444 Title: xhci locks up computer with NULL pointer dereference trying to wake up external USB3 disk Status in “linux” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, my laptop locks up completely when trying to wake my WD 1230 USB3 external hard drive from its default 10-minute standby. The system tries to wake up the drive, which is unsuccessful, and after a few seconds uas_eh_abort_handler gets called. Shortly after this the NULL pointer dereference occurs in xhci_alloc_streams or xhci_check_streams_endpoint (most times the NULL pointer dereference error doesn't even get persisted to disk, so there may be other points where it occurs). Not long after this the laptop locks up completely and both it and the hard drive have to be power-cycled. I can put the drive manually into and out of standby using hdparm, so I guess there are two problems: one which makes the drive crash (ie it must crash because it needs to be power cycled) and the other being the NULL pointer dereference and complete kernel lockup. The last good kernel was 3.15-rc4. All kernels since since have this problem, including the latest upstream kernel. I did a git bisect, which says: The merge base 6d4596905b65bf4c63c1a008f50bf385fa49f19b is bad. This means the bug has been fixed between 6d4596905b65bf4c63c1a008f50bf385fa49f19b and [89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd] I have reported this upstream at https://bugzilla.kernel.org/show_bug.cgi?id=85741. More details including the logs showing the error ocurring are there. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-22-generic 3.16.0-22.29 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
With 3.17-rc6, the VM recognises the video device again, but guvcview segfaults. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
I tried 3.17-rc6 on the laptop instead of in a VM, and guvcview doesn't segfault, but exhibits the same error as originally reported for 3.16 in this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
I haven't received any response from the bugzilla report (see the link I posted, https://bugzilla.kernel.org/show_bug.cgi?id=81611). I tried 3.17-rc5 but it failed to create the /dev/videoX file, so guvcview just reported it couldn't find a video device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
3.16-rc1 doesn't boot on my main laptop, either, even in recovery mode. I can see a bunch of [169198.816426] init: plymouth-upstart-bridge respawning too fast, stopped messages in the log. There doesn't seem to be any interest in the upstream bug, which I reported four weeks ago - is it not the right place to report it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
Same problem in 3.17-rc2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] Re: uvcvideo doesn't work with USB webcam with linux 3.16
Yes, it works fine with 3.15.10-031510-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1362358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1362358] [NEW] uvcvideo doesn't work with USB webcam with linux 3.16
Public bug reported: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1362358 Title: uvcvideo doesn't work with USB webcam with linux 3.16 Status in “linux” package in Ubuntu: New Bug description: uvcvideo doesn't work with linux 3.16 on at least two USB webcams. guvcvideo shows a black screen and reports Could not grab image or ignoring empty buffer. The camera works fine with Motion or Skype in linux 3.16. guvcvideo works fine with linux 3.15. There is more info at https://bugzilla.kernel.org/show_bug.cgi?id=81611. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-10-generic 3.16.0-10.15 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1894 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 27 17:26:27 2014 HibernationDevice: RESUME=UUID=e586cc1f-5429-445e-b3fa-d15a1f5b54a0 InstallationDate: Installed on 2014-08-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140821) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0408:2fb1 Quanta Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic root=UUID=fa1da5bc-d7d9-40bf-9d26-ad7bcf1ab6bc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-10-generic N/A linux-backports-modules-3.16.0-10-generic N/A linux-firmware 1.132 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https
[Kernel-packages] [Bug 703180] Re: 197b:2391 SD card reader inaccessible without pci bus rescan
Yes, this bug was fixed in the 3.13 kernel, so it works fine in Trusty
(and should do in earlier releases if you install a 3.13 kernel). But I
don't know exactly what fixed it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/703180
Title:
197b:2391 SD card reader inaccessible without pci bus rescan
Status in The Linux Kernel:
Confirmed
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
This is a Dell XPS L501X laptop (the new ones with USB3 etc:
http://www.dell.com/us/p/xps-15/pd.aspx)
The card reader neither shows up in lspci nor in lsusb (only device
connected via USB seems to be the internal webcam which works), so I
can't even figure out which model it is…
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-24-generic-pae 2.6.35-24.42
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
Uname: Linux 2.6.35-24-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC665 Analog [ALC665 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pascal 1777 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf090 irq 49'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:10ec0665,1028046e,0013
HDA:80862804,80860101,0010'
Controls : 29
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xadefc000 irq 17'
Mixer name : 'Nvidia GPU 14 HDMI/DP'
Components : 'HDA:10de0014,10de0101,00100100'
Controls : 16
Simple ctrls : 4
Date: Sat Jan 15 05:06:50 2011
Frequency: Once a day.
HibernationDevice: RESUME=UUID=e7d13dad-6e7f-4320-8b4f-98e29cfde6f0
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS L501X
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic-pae
root=UUID=b8eb30a4-6bd4-4d52-b356-8cb3431ba849 ro quiet splash
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/usr/bin/zsh
RelatedPackageVersions: linux-firmware 1.38.3
SourcePackage: linux
dmi.bios.date: 11/26/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 00CKNG
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias:
dmi:bvnDellInc.:bvrA04:bd11/26/2010:svnDellInc.:pnXPSL501X:pvrA04:rvnDellInc.:rn00CKNG:rvrA04:cvnDellInc.:ct8:cvrA04:
dmi.product.name: XPS L501X
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/703180/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1102797] Re: 04c5:11a2 Fujitsu ScanSnap S1500 does not work on USB3 ports
This bug is still present in Ubuntu 13.10 using the latest (stable) 3.12-1 kernel from the weekly kernel builds. ** Changed in: linux (Ubuntu) Status: Expired = 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/1102797 Title: 04c5:11a2 Fujitsu ScanSnap S1500 does not work on USB3 ports Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Fujitsu ScanSnap S1500. This scanner worked fine in 12.04, 32-bit. I wiped the hard drive and installed 12.10, 64-bit, fresh. The scanner has not worked since and I can't figure out why. I'm not quite sure which package to put this bug in. The wiki says any hardware problems get assigned to the kernel, but my scanner shows up in lsusb and shows up in /var/log/udev. That makes it sound like the hardware is getting seen. What doesn't work is sane-find-scanner, xsane, simple-scan, or gscan2pdf. Nothing that actually interfaces with the scanner works. Yes, I'm in the scanner and saned groups. The USB device ID is 04c5:11a2. The device is in /lib/udev/rules.d/40-libsane.rules. The backend is enabled in /etc/sane.d/dll.conf. The only bug-like event I see anywhere is in dmesg: [12864.421157] usb 3-4: new high-speed USB device number 7 using xhci_hcd [12864.453163] usb 3-4: New USB device found, idVendor=04c5, idProduct=11a2 [12864.453167] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [12864.453170] usb 3-4: Product: ScanSnap S1500 [12864.453172] usb 3-4: Manufacturer: Fujitsu [12864.453456] usb 3-4: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes [12864.453461] usb 3-4: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.5.0-22.35~pre201301190400-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Jan 22 00:10:19 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3113 F pulseaudio ubuntu 4968 F pulseaudio /dev/snd/controlC0: ubuntu 3113 F pulseaudio ubuntu 4968 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.333 DistroRelease: Ubuntu 13.10 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130615) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 RelatedPackageVersions: linux-restricted-modules-3.9.0-6-generic N/A linux-backports-modules-3.9.0-6-generic N/A linux-firmware 1.109 RfKill: Tags: saucy Uname: Linux 3.9.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1102797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1233479] Re: [Dell XPS 15 L502X] On demand cpufreq governor does not scale CPU freq
I'm not enormously keen to upgrade the BIOS, given that this is a regression with a relatively easy workaround, that BIOS updates can be risky, and that Dell lists the only change as Fix system resume from S4 automatically after upgrade to Windows 8, but I'll see what I can do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233479 Title: [Dell XPS 15 L502X] On demand cpufreq governor does not scale CPU freq Status in “linux” package in Ubuntu: Incomplete Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). Edit: See comment #1 below - it looks like I can manually change the cpu freq, but the governor cannot. Also, switching to use intel pstate fixes the problem. The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1233479] Re: ondemand cpufreq governor does not scale CPU freq on Sandybridge
No, 3.12-rc3 with acpi-cpufreq/ondemand doesn't have a problem switching frequencies. I booted with intel_pstate=disabled just to be absolutely sure. Although the files in /sys/devices/system/cpu/cpu0/cpufreq indicate that acpi-cpufreq is being used, turbostat's output make it look like intel_pstate is running (those aren't frequencies that acpi- cpufreq advertises!): cor CPU%c0 GHz TSC SMI%c1%c3%c6%c7 CTMP PTMP %pc2 %pc3 %pc6 %pc7 Pkg_W Cor_W GFX_W 2.50 2.31 2.00 0 8.88 0.02 0.00 88.60 58 58 1.71 0.02 2.35 70.59 9.39 3.61 0.39 0 0 1.28 2.12 2.00 1 9.94 0.01 0.00 88.77 58 58 1.71 0.02 2.35 70.60 9.39 3.61 0.39 0 1 8.13 2.63 2.00 1 3.10 1 2 2.08 1.89 2.00 1 16.41 0.01 0.00 81.51 58 1 3 1.25 2.15 2.00 1 17.24 2 4 2.24 2.16 2.00 1 6.11 0.03 0.00 91.62 58 2 5 1.05 2.42 2.00 1 7.30 3 6 2.41 2.09 2.00 1 5.03 0.04 0.00 92.52 58 3 7 1.53 1.93 2.00 1 5.91 As I stated in the original description, running Saucy under 3.12-rc3 has a different problem from 3.11 - instead of being stuck at a particular (low) frequency, it tends to run the cpus at high frequencies. The power usage on my laptop with 3.11 using intel pstate is around 18W - with 3.12 it is around 35W. I suspect that this is compiz's fault, though - 'top' shows that it jumps between 20% and 250% cpu running under 3.12-rc3. Moving windows around is noticeably 'jerkier' under 3.12-rc3, and this is when I see the highest cpu usage from compiz. ** Tags added: kernel-fixed-upstream ** 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/1233479 Title: ondemand cpufreq governor does not scale CPU freq on Sandybridge Status in “linux” package in Ubuntu: Confirmed Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). Edit: See comment #1 below - it looks like I can manually change the cpu freq, but the governor cannot. Also, switching to use intel pstate fixes the problem. The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29
[Kernel-packages] [Bug 1233479] Re: ondemand cpufreq governor does not scale CPU freq on Sandybridge
I've tagged it kernel-fixed-upstreamm as requested, although from the frequencies that turbostat is showing I'm not entirely convinced that the acpi-cpufreq driver is being used in the upstream kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233479 Title: ondemand cpufreq governor does not scale CPU freq on Sandybridge Status in “linux” package in Ubuntu: Confirmed Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). Edit: See comment #1 below - it looks like I can manually change the cpu freq, but the governor cannot. Also, switching to use intel pstate fixes the problem. The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1233479] Re: ondemand cpufreq governor does not scale CPU freq on Sandybridge
Out of interest, why are all your cores running over 3.5GHz when you've only loaded CPU 7? When acpi-cpufreq/ondemand was working properly on my system, it would have had seven cores running near the minimum (0.8 GHz) and the loaded one running at turbo. Has anything been patched in the ondemand governor for Ubuntu's 3.11 kernel? Since I can manually change the CPU frequencies, it might be that acpi-cpufreq has no issues, but the ondemand governor isn't detecting the increase in load on my system. And it looks like the problem doesn't carry across to the 'vanilla' 3.12. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233479 Title: ondemand cpufreq governor does not scale CPU freq on Sandybridge Status in “linux” package in Ubuntu: Confirmed Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). Edit: See comment #1 below - it looks like I can manually change the cpu freq, but the governor cannot. Also, switching to use intel pstate fixes the problem. The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1233479] [NEW] CPUs stuck at minimum frequency with ondemand cpufreq governor, even after reboot
Public bug reported: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: log output from the turbostat command https://bugs.launchpad.net/bugs/1233479/+attachment/3852207/+files/turbostat%20log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233479 Title: CPUs stuck at minimum frequency with ondemand cpufreq governor, even after reboot Status in “linux” package in Ubuntu: New Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature
[Kernel-packages] [Bug 1233479] Re: CPUs stuck at minimum frequency with ondemand cpufreq governor, even after reboot
If I switch to to 'turbomode' using the cpufreq-indicator, turbostat shows the cpus still stuck at 800MHz: cor CPU%c0 GHz TSC SMI%c1%c3%c6%c7 CTMP PTMP %pc2 %pc3 %pc6 %pc7 Pkg_W Cor_W GFX_W 11.67 0.80 2.00 0 13.31 0.21 0.00 74.82 53 53 2.75 0.07 2.00 13.06 6.02 1.74 0.32 0 0 7.61 0.80 2.00 0 12.78 0.59 0.00 79.02 53 53 2.75 0.07 2.00 13.07 6.02 1.74 0.32 0 1 10.68 0.80 2.00 0 9.71 1 2 7.12 0.80 2.00 0 13.89 0.06 0.00 78.93 52 1 3 11.48 0.80 2.00 0 9.53 2 4 5.12 0.80 2.00 0 6.70 0.11 0.00 88.07 51 2 5 5.53 0.80 2.00 0 6.29 3 6 10.14 0.80 2.00 0 36.54 0.07 0.00 53.24 53 3 7 35.69 0.80 2.00 0 11.00 although scaling_cur_freq then does indicate 2001000. However, when I run the stress test, scaling_cur_freq does not change from the standard 800MHz. The CPU Blowfish benchmark in hardinfo shows that the CPU performs faster if I manually change the frequency, so it appears that the frequency is not locked per se but just that the governor does not automatically switch it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233479 Title: ondemand cpufreq governor does not scale CPU freq on Sandybridge Status in “linux” package in Ubuntu: Confirmed Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). Edit: See comment #1 below - it looks like I can manually change the cpu freq, but the governor cannot. Also, switching to use intel pstate fixes the problem. The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1233479] Re: CPUs stuck at minimum frequency with ondemand cpufreq governor, even after reboot
Rebooting with intel_pstate=enable has fixed the issue and vastly improved the responsiveness of this laptop. ** Summary changed: - CPUs stuck at minimum frequency with ondemand cpufreq governor, even after reboot + ondemand cpufreq governor does not scale CPU freq on Sandybridge ** Description changed: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). - The only unusual thing I had done prior to this was to boot into the - weekly build of 3.12-rc3 just prior (this kernel kept the frequencies - rather high, typically over 2GHz, ie using a lot more power than usual, - so I rebooted back into the standard kernel). + + Edit: See comment #1 below - it looks like I can manually change the cpu freq, but the governor cannot. Also, switching to use intel pstate fixes the problem. + + + The only unusual thing I had done prior to this was to boot into the weekly build of 3.12-rc3 just prior (this kernel kept the frequencies rather high, typically over 2GHz, ie using a lot more power than usual, so I rebooted back into the standard kernel). This is the contents of the files in /sys/devices/system/cpu/cpu0/cpufreq/: affected_cpus: 0 bios_limit: 2001000 cpuinfo_cur_freq: 80 cpuinfo_max_freq: 2001000 cpuinfo_min_freq: 80 cpuinfo_transition_latency: 1 freqdomain_cpus: 0 1 2 3 4 5 6 7 related_cpus: 0 scaling_available_frequencies: - 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 + 2001000 200 190 180 170 160 150 140 130 120 110 100 90 80 scaling_available_governors: - conservative ondemand userspace powersave performance + conservative ondemand userspace powersave performance scaling_cur_freq: 80 scaling_driver: acpi-cpufreq scaling_governor: ondemand scaling_max_freq: 2001000 scaling_min_freq: 80 scaling_setspeed: unsupported stats: ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: rocko 2813 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: rocko 2813 F pulseaudio Date: Tue Oct 1 10:13:24 2013 InstallationDate: Installed on 2012-08-25 (401 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.11.0-9-generic N/A - linux-backports-modules-3.11.0-9-generic N/A - linux-firmware1.115 + linux-restricted-modules-3.11.0-9-generic N/A + linux-backports-modules-3.11.0-9-generic N/A + linux-firmware1.115 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-01 (30 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233479 Title: ondemand cpufreq governor does not scale CPU freq on Sandybridge Status in “linux” package in Ubuntu: Confirmed Bug description: I notice that turbostat shows all cpus stuck at the minimum 800MHz (see attached log) on my system, even after rebooting twice. I used stress --cpu 8 to confirm that the frequencies remained at 800MHz even under load. It looks like the system is using the acpi-cpufreq driver with the ondemand governor (has the default been changed so it does not use intel p-state, as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647?). Edit: See comment #1 below - it looks like I can manually change the cpu freq
[Kernel-packages] [Bug 1188647] Re: Please change intel_pstate default to disable
I recommend switching back to to use intel pstate by default for the 3.11 kernel in Saucy as the overly-high frequency issue seems to be resolved now (from what I recall when I was trying out the 3.10 and 3.11 kernels, this issue was caused by particular settings in the kernel config; changing the settings fixed the issue and the stock Ubuntu 3.11 kernel now has those changed settings). This is particularly important as the acpi-cpufreq ondemand governor appears to have major issues in 3.11 (at least it does on my laptop - it can't change the cpu frequencies and they remain locked at the lowest setting so system performance is abysmal - see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233479). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188647 Title: Please change intel_pstate default to disable Status in “linux” package in Ubuntu: Fix Released Bug description: 3.9 introduced a new default governor on SandyBridge CPUs called INTEL_PSTATE which, when built in and enabled (the default), removes all other governors (like our usual default, ondemand). 3.10 extended this to Ivybridge generation CPUs. In theory, this isn't an awful thing, as the new Intel pstate governor should be higher performance and give better power savings. In theory. In practice, it drives my CPUs to max frequency nearly constantly, spins my fans like mad and, somehow, does all of this while also eating enough CPU time in kernel threads to make my machine choppy, unresponsive, and unable to do simple things like play videos when I get off work. Therefore, I propose that we, for now, toggle intel_pstate to disable by default (I am using intel_pstate=disable on my command line right now, with great success), so it's still built in, and people can play with it, but it's off by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adconrad 2574 F pulseaudio CurrentDmesg: [ 30.633035] init: plymouth-stop pre-start process (2079) terminated with status 1 [ 36.086916] br0: port 1(eth0) entered forwarding state Date: Fri Jun 7 08:48:56 2013 HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c InstallationDate: Installed on 2012-12-09 (179 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121209) MachineType: LENOVO 4173LPB MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic root=UUID=aad5-ef31-4428-973f-71740fc7cb6a ro intel_pstate=disable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET55WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 4173LPB dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET55WW(1.35):bd09/13/2012:svnLENOVO:pn4173LPB:pvrThinkPadT420s:rvnLENOVO:rn4173LPB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4173LPB dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
