[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I have this laptop. Bug happens on S3 suspend, much better on modern standby (once it took two minutes or so for the touchpad to resume, every other time it has worked). Modern suspend does not use much battery. Mine slept for 8:20h last night and the battery percentage declined from 96% to 94%. my kernel is 5.13 and the session is Wayland gnome. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from the impish repos. To recreate: 1. Reboot a X1C9 machine and see that the touchpad works fine 2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a software suspend) 3. Resume from suspend and see that touchpad acts differently and less responsive than right after a clean boot What is expected: 1. Same responsive touchpad experience after resuming from suspend as right after a clean boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: pop:GNOME DistUpgraded: Fresh install DistroCodename: hirsute DistroRelease: Pop!_OS 21.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Xe Graphics [17aa:22d5] MachineType: LENOVO 20XW005PMX Package: libinput10 1.18.0-1 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet systemd.show_status=false loglevel=0 splash Tags: hirsute third-party-packages ubuntu Uname: Linux 5.13.5-051305-generic x86_64 UnreportableReason: This does not seem to be an official Pop!_OS package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 06/15/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET66W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW005PMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW005PMX dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1927767] [NEW] All apps crashed in my X11 session, then terminal console crashed, reboot failed
Public bug reported: The reboot failed with many services that could not stop. I think there may have been a crash in the network stack. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim4093 F pulseaudio /dev/snd/controlC2: tim4093 F pulseaudio /dev/snd/controlC0: tim4093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 8 03:07:12 2021 InstallationDate: Installed on 2020-11-22 (166 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax mitigations=off crashkernel=192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to hirsute on 2021-04-23 (14 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927767 Title: All apps crashed in my X11 session, then terminal console crashed, reboot failed Status in linux package in Ubuntu: New Bug description: The reboot failed with many services that could not stop. I think there may have been a crash in the network stack. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim4093 F pulseaudio /dev/snd/controlC2: tim4093 F pulseaudio /dev/snd/controlC0: tim4093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 8 03:07:12 2021 InstallationDate: Installed on 2020-11-22 (166 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax mitigations=off crashkernel=192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to hirsute on 2021-04-23 (14 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@olepet I have 14ARE05 too, same symptoms. It seems the hardware is different, we need a new bug. I see no elan modules loaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW 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: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 ** This bug has been marked a duplicate of bug 1872159 booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.
@Alberto, couldn't prime-select do this when going into hybrid or Optimus mode? Only users with nvidia hybrid graphics would go down this logic path, and they are only ones who need the fix (but only if they are using gdm3, sddm and lightdm continue to be unaffected by this) The set of users who "need" this fix are gdm3 users with hybrid Nvidia graphics (where "need" = want tear-free graphics on their laptop panel if Optimus, or on all displays if it's something like a T-series Thinkpad where the nvidia card has no direct access to any display). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
not 'a fix', the intel maintainer's 5.4 patch has been applied by the ubuntu devs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
Confirming that a fix has been backported to 20.04, currently in the proposed kernel. I'm testing it, the power usage is great. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
This bug persists in 20.04 daily. The one-line Pop!OS solution (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26) works, just logout and login. Pop!OS has used this for several releases now, just saying. ** Summary changed: - nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg + nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
Also, please note the upstream bug discussion also includes patches for 5.4 It seems that 5.4 is destined for 20.04. So far 5.4 upstream is still using the first release of this patch, which means 5.4 has the i915 RC6 bug. 5.4 is a LTS kernel bug so it strange to me, but please, I hope you can consider making sure that 20.04 does not launch with this nasty power 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/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
Yes, that little patch applies cleanly to every 5.3 hwe build I've done (about
five I'd say)
To be clear:
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c
b/drivers/gpu/drm/i915/gt/intel_lrc.c
index 82b7ace62d97..b18f281d5d12 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -510,7 +510,11 @@ execlists_user_begin(struct intel_engine_execlists
*execlists,
inline void
execlists_user_end(struct intel_engine_execlists *execlists)
{
+ struct intel_engine_cs *engine =
+ container_of(execlists, typeof(*engine), execlists);
+
execlists_clear_active(execlists, EXECLISTS_ACTIVE_USER);
+ mod_delayed_work(engine->i915->wq, >i915->gem.retire_work, 0);
}
static inline void
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856653
Title:
CVE-2019-0154 caused major power problem, pls backport upstream's fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
https://gitlab.freedesktop.org/drm/intel/issues/614
the fix released as CVE-2019-0154 increases idle power consumption on intel
i915 6th gen and later.
That's because the GPU does not enter RC6 any more.
For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels.
Previously, it idled at 5W.
Effects on a T480 (8th gen) are less dramatic but still significant.
5.5RC1 has the maintainer's second pass at this, which restores RC6
idling
The maintainer's patch for 5.3 is here:
https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057
I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it
builds. I am testing it now.
I think it would be very helpful to backport this if you can.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
PS I've been running on hwe 5.3 from Ubuntu's kernel git repository for a few weeks, with the patch linked above, and it is stable on my Thinkpad T480. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
If the power-saving patch is backported,will this be updated? I'm on own patched kernel so I won't notice. It's an awful problem, by the way, it harms battery life on any laptop with intel graphics from 2016 or later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport maintainers fix
logs not applicable ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - CVE-2019-0154 caused major power problem, pls backport maintainers fix + CVE-2019-0154 caused major power problem, pls backport maintainer's fix ** Summary changed: - CVE-2019-0154 caused major power problem, pls backport maintainer's fix + CVE-2019-0154 caused major power problem, pls backport upstream's fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport maintainers fix
** Description changed: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. - That's because the GPU does not enter RC6 any more. + That's because the GPU does not enter RC6 any more. - For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. - Effects on a T480 (8th gen) are less dramatic but still significant. + For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. + Effects on a T480 (8th gen) are less dramatic but still significant. + 5.5RC1 has the maintainer's second pass at this, which restores RC6 + idling - 5.5RC1 has the maintainers second pass at this, which restores RC6 idling - - The maintainers patch for 5.3 is here: - https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 + The maintainer's patch for 5.3 is here: + https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport maintainers fix Status in linux package in Ubuntu: Incomplete Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856653] [NEW] CVE-2019-0154 caused major power problem, pls backport maintainers fix
Public bug reported: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport maintainers fix Status in linux package in Ubuntu: Incomplete Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
With my T480 and the 5.0 ubuntu kernel, and the 5.3 in the proposed PPA, two finger scrolling does not work unless I specify psmouse.synaptics_intertouch=0 or =1 either value fixes 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/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's solution (root rights granted in Xwrapper) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
And PS: workaround continues to be: use lightdm, a five minute fix at worst. https://askubuntu.com/questions/139491/how-to-change-from-gdm-to-lightdm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
19.10 beta and nvidia drivers 430 and 435 have the same problem. I have made the bug title correctly specific. ** Summary changed: - nvidia-drm.modeset=1 results in no monitors detected by Xorg + nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
just one last thing, possibly you are not aware that 19.04 Ubuntu wayland sessions have exactly the same problem: no external monitors. While this bug refers to Xorg, the problem is not limited to Xorg. At least on my Optimus laptop. And when I use its multiplexor to go into pure Nvidia mode, no monitors work, not even the laptop panel. On Fri, 21 Jun 2019 at 12:50, Daniel van Vugt wrote: > Actually, maybe those other DMs don't run as root. My memory is failing. > So again maybe we do want a similar workaround in gdm3. But that doesn't > seem to be the root cause of the bug. > > ** Changed in: gdm3 (Ubuntu) >Status: Invalid => Opinion > > ** No longer affects: mutter (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I think his point was to isolate the problem as being gdm3's wayland code. If you need modeset=1 for wayland, then why is there any effort to support nvidia and wayland under gnome, since it won't work (or are only optimus systems affected by this?) my point was that you marked this as invalid, but the only way to avoid this bug is to avoid using gdm3. You don't have to change anything else. So it looks like a gdm3 bug. On Fri, 21 Jun 2019 at 11:50, Daniel van Vugt wrote: > Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind > of pointless. It's pointless because the most common reason for using > nvidia-drm.modeset=1 is to get Wayland support. I know there are other > reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in > PRIME setups. But mostly if people use modeset=1 it is to get Wayland > support. > > If we can't get a fix from Nvidia then some kind of workaround that runs > Xorg as root (like comment #26) is probably the next best option. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
"gdm3 compile without wayland", I meant -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
What we know about this bug is that gdm3, nvidia and modeset=1 is broken under configurations which are not broken when sddm and lightdm are used. we know that gdm3 sessions with external monitors work with root permissions. we know that gdm3 compiled with wayland also works (according to the gentoo user generix). And neither gnome developers nor nvidia acknowledge a bug. If you make a venn diagram of all of this, gdm3 is the intersection of every observation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50
I should add that the "fix" I reported is only a narrow fix. The internal display works. But external displays don't work if you have nvidia drivers, gdm3 and if you are using modeset=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1706474 Title: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50 Status in gdm3 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Invalid Bug description: ubuntu 17.04 with gnome desktop. The laptop is a Thinkpad p50 with a quadro M1000M. To get this bug I am using the hybrid graphics mode. This problem occurs with 375.82 and also with the new 384 driver. When using gdm3 and options nvidia_375_drm modeset=1 the greeter only shows the laptop screen. My two external displays are not turned on. they do not appear in the listing of diplays in xrandr the problem does not occur if modeset=0 or if I use lightdm I suspect this is a known bug but I am not quite sure so I'm reporting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I posted here: https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in- modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes- it-is-an-nvidia-bug/?offset=3#5351122 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
User generix reports that when gdm3 is compiled without wayland support, this bug is not seen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I will post your findings to the nvidia developers forum. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Hi Daniel, thanks for not forgetting about this, unlike everyone else :) Have you communicated this observation to Nvidia at all? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
already fixed (see https://lists.ubuntu.com/archives/cosmic- changes/2019-March/012430.html) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: Fix Committed Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
Yep. I didn't find that, I filed a new Ubuntu kernel bug which I will now close. On Tue, 19 Mar. 2019, 16:05 Kai-Heng Feng, wrote: > LP: #1812099? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1820796 > > Title: > natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions > ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: Fix Committed Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798708] Re: It will load nvidia driver when swith to Intel mode
The external monitor problem is probably a well-known gdm3 bug: gdm3 with nvidia modeset=1 stops the nvidia driver from detecting external monitors (possibly it invokes some wayland features when it shouldn't). It is not a problem with nvidia-prime or with the kernel. You can fix it by using lightdm instead of gdm3. This bug affects fedora as well. ubuntu 19.04 has reverted to nvidia modeset = 0 be default to avoid this bug (at the cost of unfixable screen tearing for Optimus users in nvidia mode). nvidia-prime does always include the nvidia modules in the initramfs kernel, this was a change in 18.10 backported to 18.04. Previous nvidia- prime pacakges used to rebuild initramfs to add or remove the module, but this is not required any longer. Choosing prime-select intel means the nvidia module is unloaded when the machine is starting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798708 Title: It will load nvidia driver when swith to Intel mode Status in linux package in Ubuntu: Confirmed Bug description: We found the nvidia-prime will not run update-initramfs as before. After switch to intel, then reboot I found the nvidia modules was loaded. If I did S3 or close the lid, and resume back, the nvidia modules was removed, so the gnome session will be reloaded, you need to login again, all the opend applications in this session was gone. nvidia-prime 0.8.8.1 linux 4.15.0-1021-oem nvidia-driver-390 380.87-0ubuntu0~gpu18.04.1. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2218 F pulseaudio /dev/snd/controlC0: u 2218 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20181018-40+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2b45d917-3587-410f-9b94-f52eb082b7dc InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20181018-09:17 MachineType: LENOVO 20MEZ480US NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-oem root=UUID=e68fa8d5-22f5-464b-9775-753b4ae159eb ro noprompt quiet splash acpi_osi=! acpi_osi=Linux-Lenovo-NV-HDMI-Audio vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-oem N/A linux-backports-modules-4.15.0-1021-oem N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-1021-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET30W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MEZ480US dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET30W(1.12):bd10/04/2018:svnLENOVO:pn20MEZ480US:pvrThinkPadP1:rvnLENOVO:rn20MEZ480US:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MEZ480US dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+attachment/5247477/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: New Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] [NEW] natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
Public bug reported: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: New Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687910] Re: [Lenovo W520] Linux Freezing Issue At Boot
exists in 4.12 and 4.13 in the 17.10 repositories. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687910 Title: [Lenovo W520] Linux Freezing Issue At Boot Status in linux package in Ubuntu: Confirmed Bug description: Boot error occurs in a 64-bit system and only when certain conditions are met: BIOS/UEFI Settings: Config -> Display -> Graphics Device [Discrete Graphics] -> OS Detection for NVIDIA Optimus [Disabled] Security -> Virtualization -> Intel(R) Virtualization Technology [Enabled] -> Intel(R) VT-d Feature [Enabled] System hangs at boot time either after kernel log shows: [1.043982] ACPI: Video Device [VID1] (multi-head: yes rom: yes post: no) [1.047138] FUJITSU Extended Socket Network Device Driver - version 1.0 - Copyright (c) 2015 FUJITSU LIMITED or later after: [OK] Started Load/Save Screen Backlight Brightness of backlight:nv_backlight. The error occurs randomly (about 50% of all boot tries). The error has already been known for a long time (e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/776999) and has never been fixed. It also occurs for older BIOS/UEFI versions and Ubuntu versions (e.g. 14.04) than shown in the report. Other related reports can be found here: https://bugzilla.kernel.org/show_bug.cgi?id=43054 https://bugzilla.kernel.org/show_bug.cgi?id=156341 https://bugzilla.opensuse.org/show_bug.cgi?id=1022443 https://ubuntuforums.org/showthread.php?t=2044699 https://binaryimpulse.com/2014/08/lenovo-thinkpad-w520-workaround-for-linux-freezing-issue-at-boot/ https://forums.lenovo.com/t5/Linux-Discussion/64-bit-Linux-W520-amp-nVidia/td-p/577789/page/2 A workaround for this issue is to add kernel parameter "nox2apic" to the GRUB_CMDLINE_LINUX_DEFAULT line. Another possible workaround (at least for the first hanging position is to use kernel parameters 'acpi_osi=! acpi_osi="!Windows 2009"' instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 2040 F pulseaudio /dev/snd/controlC0: 2040 F pulseaudio CurrentDesktop: XFCE Date: Wed May 3 13:03:38 2017 HibernationDevice: RESUME=UUID=19c8581e-f65b-4382-a940-e82a48d9297f MachineType: LENOVO 42844AG ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=2f25428b-c54c-422e-be18-18233f17990d ro nox2apic RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 42844AG 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:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn42844AG:pvrThinkPadW520:rvnLENOVO:rn42844AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42844AG dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1169984] Re: 3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device fails with -ENODEV
Since the bug was fixed I have had no regressions. Now on 14.04. On Mon, Sep 8, 2014 at 10:34 AM, Gordon McIntosh 1169...@bugs.launchpad.net wrote: Updated to 14.04 - also used pulse audio settings to correct this problem - Have had no trouble since mods done: !!! hope this helps On 08/09/14 01:24, TEN wrote: http://ubuntuforums.org/showthread.php?t=2236419p=13117007#post13117007 suggests this may not be entirely resolved yet. Any hints what to look for in the /var/log/syslog (and/or get into a debug mode) appreciated. -- You received this bug notification because you are subscribed to a duplicate bug report (1169761). https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device fails with -ENODEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-tests/+bug/1169984/+subscriptions -- Tim Richardson -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening device fails with -ENODEV Status in Ubuntu Desktop Tests: New Status in Release Notes for Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Raring: Fix Released Bug description: Release note text * There are reports of non-functional HDMI audio on various machines, even with proprietary drivers. In some cases analog built-in audio is affected too. Typically the the audio device does not show up in sound settings at all. ([[https://bugs.launchpad.net/bugs/1169984 | LP: #1169984]] /Release note text === Current recommended workaround === Hopefully there'll soon be a proposed kernel to test instead, but if you can't wait, simplest is to: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS === Alternate workaround === IF you have no intention to use the HDMI audio, blacklisting the HDMI audio module will probably prevent this issue. The following commands should do it: echo blacklist snd-hda-codec-hdmi | sudo tee -a /etc/modprobe.d/blacklisthmdi.conf sudo depmod -a (Reboot) === Sound card is no longer detected in the latest upgrade. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Apr 17 11:13:20 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-01 (106 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121231) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to raring on 2013-02-12 (64 days ago) dmi.bios.date: 07/27/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd07/27/2012:svnTOSHIBA:pnSatelliteU845W:pvrPSU5RU-00Q003:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite U845W dmi.product.version: PSU5RU-00Q003 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-tests/+bug/1169984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
the patch for this has been added to stable kernels 3.15 and 3.14 so I hope it gets picked up by Ubuntu soon. This is a note to let you know that I've just added the patch titled drm/i915: Avoid div-by-zero when pixel_multiplier is zero to the 3.15-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: drm-i915-avoid-div-by-zero-when-pixel_multiplier-is-zero.patch and it can be found in the queue-3.15 subdirectory. If you, or anyone else, feels it should not be added to the stable tree, please let sta...@vger.kernel.org know about it. From 2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= ville.syrj...@linux.intel.com Date: Mon, 9 Jun 2014 16:20:46 +0300 Subject: drm/i915: Avoid div-by-zero when pixel_multiplier is zero MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Ville Syrjälä ville.syrj...@linux.intel.com commit 2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in The Linux Mint Distribution: New Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
The good news is that just an hour ago the Intel engineer and I finished testing the fix, so it will go into the kernel soon (I don't know when). Ubuntu kernel developers will pick it up I expect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in The Linux Mint Distribution: New Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
Follow the upstream bug.perhaps you can help with testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in The Linux Mint Distribution: New Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1289721] Re: [TOSHIBA Satellite U400] suspend/resume failure
** Tags added: kernel-bug-reported-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/1289721 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Triaged Bug description: suspend fails, does not resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1695 F pulseaudio Date: Sat Mar 8 19:42:01 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (118 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (5 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
this is a kernel bug ** Package changed: lightdm (Ubuntu) = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux-meta” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
Note: it is not an upstream bug. I can not reproduce it like so: go to terminal sudo service lightdm stop pm-suspend this always works, with 3.11.10, 3.12.14, 3.13.6 and 3.14 rc7 However, when lightdm is running, does not resume. ** Tags removed: kernel-bug-reported-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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
testing reveals that the bug is linked to lightdm It is not reproducible when lightdm is not running. When lightdm is running, a wide range of kernels show the resume fail. These kernels do not fail resume when lightdm is not running ** Description changed: does not resume (no backlight on LCD panel, for example) + seems to be caused by lightdm not by kernel; when + service lightdm stop + bug is not reproduced by pm-suspend + ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: katherine 1676 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: - TERM=linux - PATH=(custom, no user) + TERM=linux + PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.13.0-17-generic N/A - linux-backports-modules-3.13.0-17-generic N/A - linux-firmware 1.126 + linux-restricted-modules-3.13.0-17-generic N/A + linux-backports-modules-3.13.0-17-generic N/A + linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: - + dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA ** Package changed: linux (Ubuntu) = lightdm (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “lightdm” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) seems to be caused by lightdm not by kernel; when service lightdm stop bug is not reproduced by pm-suspend ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
upstream report https://bugs.freedesktop.org/show_bug.cgi?id=76520 ** Bug watch added: freedesktop.org Bugzilla #76520 https://bugs.freedesktop.org/show_bug.cgi?id=76520 ** Tags added: kernel-bug-reported-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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Triaged Bug description: does not resume (no backlight on LCD panel, for example) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1289721] Re: [TOSHIBA Satellite U400] suspend/resume failure
with 3.13.6-031306-generic the bug still exists. Now I'll check the latest 3.14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1289721 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: suspend fails, does not resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1695 F pulseaudio Date: Sat Mar 8 19:42:01 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (118 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (5 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1290787] Re: [TOSHIBA Satellite U400] suspend/resume failure
3.13.6-031306-generic kernel-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/1290787 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: does not resume (no backlight on LCD panel, for example) ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1676 F pulseaudio Date: Tue Mar 11 21:08:32 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (121 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (8 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1289721] Re: [TOSHIBA Satellite U400] suspend/resume failure
bug exists in 3.14.0-031400rc6-generic ** 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/1289721 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: suspend fails, does not resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1695 F pulseaudio Date: Sat Mar 8 19:42:01 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (118 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (5 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1289721] [NEW] [TOSHIBA Satellite U400] suspend/resume failure
Public bug reported: suspend fails, does not resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1695 F pulseaudio Date: Sat Mar 8 19:42:01 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (118 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (5 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1289721 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: suspend fails, does not resume ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1695 F pulseaudio Date: Sat Mar 8 19:42:01 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (118 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (5 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1288657] [NEW] [TOSHIBA Satellite U400] suspend/resume failure
Public bug reported: After resuming the hard drive and fan flash. But there is no screen. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-15-generic 3.13.0-15.35 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1598 F pulseaudio Date: Thu Mar 6 21:23:53 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (116 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-15-generic N/A linux-backports-modules-3.13.0-15-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (3 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-kerneloops i386 resume suspend trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1288657 Title: [TOSHIBA Satellite U400] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: After resuming the hard drive and fan flash. But there is no screen. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-15-generic 3.13.0-15.35 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1598 F pulseaudio Date: Thu Mar 6 21:23:53 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3dd143c7-add5-4b7b-8c26-bbd7446abb39 InstallationDate: Installed on 2013-11-09 (116 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) InterpreterPath: /usr/bin/python3.4 MachineType: TOSHIBA Satellite U400 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-15-generic N/A linux-backports-modules-3.13.0-15-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [TOSHIBA Satellite U400] suspend/resume failure UpgradeStatus: Upgraded to trusty on 2014-03-02 (3 days ago) UserGroups: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288657/+subscriptions --
[Kernel-packages] [Bug 1288652] [NEW] not resuming, Toshiba laptop, intel video
Public bug reported: I run ubuntu-bug linux and I get a message that it is sending the information, but then firefox opens me in a new bug report which again asks me to run ubuntu-bug linux. I don't know what to do. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-15-generic 3.13.0-15.35 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1437 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Mar 6 21:16:59 2014 InstallationDate: Installed on 2013-11-09 (116 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: TOSHIBA Satellite U400 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-03-02 (3 days ago) WifiSyslog: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1288652 Title: not resuming, Toshiba laptop, intel video Status in “linux” package in Ubuntu: Incomplete Bug description: I run ubuntu-bug linux and I get a message that it is sending the information, but then firefox opens me in a new bug report which again asks me to run ubuntu-bug linux. I don't know what to do. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-15-generic 3.13.0-15.35 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: katherine 1437 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Mar 6 21:16:59 2014 InstallationDate: Installed on 2013-11-09 (116 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: TOSHIBA Satellite U400 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic root=UUID=9d9d9d28-df78-475d-af30-72b9ecb189be ro quiet splash vt.handoff=7 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-03-02 (3 days ago) WifiSyslog: dmi.bios.date: 10/25/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V4.70 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV4.70:bd10/25/2010:svnTOSHIBA:pnSatelliteU400:pvrPSU40A-01M001:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40A-01M001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1288652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
13.04 is ok for me. On 09/11/2013 10:05 pm, Andrejs Hanins ahan...@gmail.com wrote: Hi all, sorry for bothering, but I'm upgraded to latest Ubuntu 13.10 and the bug is still there, despite the fact fix was available few months ago. Is it expected situation? Thanks. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1136110 Title: USB Audio Codec choppy playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1136110/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 v3.5.7.6 ~ v3.5.7.8 v3.7.6 v3.7.7 ~ v3.7.10 v3.8.0-rc6 v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called Asynchronous USB Digital Audio Codec (DAC). It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called Synchronous USB DAC, uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 3.5.0-26 3.5.7.5 3.5.7.6 (and all 3.5.7.x above) 3.7.6 3.7.7 (and all 3.7.x above) 3.8.0-rc6 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless
