[Bug 1358116] Re: The mute led status can't be kept after s3/s4
This bug was fixed in the package linux - 3.13.0-39.66 --- linux (3.13.0-39.66) trusty; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1386629 [ Upstream Kernel Changes ] * KVM: x86: Check non-canonical addresses upon WRMSR - LP: #1384539 - CVE-2014-3610 * KVM: x86: Prevent host from panicking on shared MSR writes. - LP: #1384539 - CVE-2014-3610 * KVM: x86: Improve thread safety in pit - LP: #1384540 - CVE-2014-3611 * KVM: x86: Fix wrong masking on relative jump/call - LP: #1384545 - CVE-2014-3647 * KVM: x86: Warn if guest virtual address space is not 48-bits - LP: #1384545 - CVE-2014-3647 * KVM: x86: Emulator fixes for eip canonical checks on near branches - LP: #1384545 - CVE-2014-3647 * KVM: x86: emulating descriptor load misses long-mode case - LP: #1384545 - CVE-2014-3647 * KVM: x86: Handle errors when RIP is set during far jumps - LP: #1384545 - CVE-2014-3647 * kvm: vmx: handle invvpid vm exit gracefully - LP: #1384544 - CVE-2014-3646 * Input: synaptics - gate forcepad support by DMI check - LP: #1381815 linux (3.13.0-38.65) trusty; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1379244 [ Andy Whitcroft ] * Revert "SAUCE: scsi: hyper-v storsvc switch up to SPC-3" - LP: #1354397 * [Config] linux-image-extra is additive to linux-image - LP: #1375310 * [Config] linux-image-extra postrm is not needed on purge - LP: #1375310 [ Upstream Kernel Changes ] * Revert "KVM: x86: Increase the number of fixed MTRR regs to 10" - LP: #1377564 * Revert "USB: option,zte_ev: move most ZTE CDMA devices to zte_ev" - LP: #1377564 * aufs: bugfix, stop calling security_mmap_file() again - LP: #1371316 * ipvs: fix ipv6 hook registration for local replies - LP: #1349768 * Drivers: add blist flags - LP: #1354397 * sd: fix a bug in deriving the FLUSH_TIMEOUT from the basic I/O timeout - LP: #1354397 * drm/i915/bdw: Add 42ms delay for IPS disable - LP: #1374389 * drm/i915: add null render states for gen6, gen7 and gen8 - LP: #1374389 * drm/i915/bdw: 3D_CHICKEN3 has write mask bits - LP: #1374389 * drm/i915/bdw: Disable idle DOP clock gating - LP: #1374389 * drm/i915: call lpt_init_clock_gating on BDW too - LP: #1374389 * drm/i915: shuffle panel code - LP: #1374389 * drm/i915: extract backlight minimum brightness from VBT - LP: #1374389 * drm/i915: respect the VBT minimum backlight brightness - LP: #1374389 * drm/i915/bdw: Apply workarounds in render ring init function - LP: #1374389 * drm/i915/bdw: Cleanup pre prod workarounds - LP: #1374389 * drm/i915: Replace hardcoded cacheline size with macro - LP: #1374389 * drm/i915: Refactor Broadwell PIPE_CONTROL emission into a helper. - LP: #1374389 * drm/i915: Add the WaCsStallBeforeStateCacheInvalidate:bdw workaround. - LP: #1374389 * drm/i915/bdw: Remove BDW preproduction W/As until C stepping. - LP: #1374389 * mptfusion: enable no_write_same for vmware scsi disks - LP: #1371591 * iommu/amd: Fix cleanup_domain for mass device removal - LP: #1375266 * cifs: mask off top byte in get_rfc1002_length() - LP: #1372482 * Input: synaptics - add support for ForcePads - LP: #1377564 * ASoC: pxa-ssp: drop SNDRV_PCM_FMTBIT_S24_LE - LP: #1377564 * drm/radeon: add bapm module parameter - LP: #1377564 * drm/radeon: Add missing lines to ci_set_thermal_temperature_range - LP: #1377564 * drm/radeon: Add ability to get and change dpm state when radeon PX card is turned off - LP: #1377564 * ALSA: hda/realtek - Avoid setting wrong COEF on ALC269 & co - LP: #1377564 * of/irq: Fix lookup to use 'interrupts-extended' property first - LP: #1377564 * Possible null ptr deref in SMB2_tcon - LP: #1377564 * CIFS: Fix SMB2 readdir error handling - LP: #1377564 * CIFS: Fix wrong directory attributes after rename - LP: #1377564 * md/raid6: avoid data corruption during recovery of double-degraded RAID6 - LP: #1377564 * ARM: dts: i.MX53: fix apparent bug in VPU clks - LP: #1377564 * pata_scc: propagate return value of scc_wait_after_reset - LP: #1377564 * libata: widen Crucial M550 blacklist matching - LP: #1377564 * ALSA: hda - restore the gpio led after resume - LP: #1358116, #1377564 * md/raid10: fix memory leak when reshaping a RAID10. - LP: #1377564 * md/raid10: Fix memory leak when raid10 reshape completes. - LP: #1377564 * MIPS: OCTEON: make get_system_type() thread-safe - LP: #1377564 * can: c_can: checking IS_ERR() instead of NULL - LP: #1377564 * HID: logitech: perform bounds checking on device_id early enough - LP: #1377564 * firmware: Do not use WARN_ON(!spin_is_locked()) - LP: #1377564 * drm/radeon: add new KV pci id - LP: #1377564 * drm/radeon:
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
The fix has been merged by upstream. commit f475371aa65de84fa483a998ab7594531026b9d9 Author: Hui Wang Date: Tue Aug 19 12:07:03 2014 +0800 ALSA: hda - restore the gpio led after resume On some HP laptops, the mute led is controlled by codec gpio. When some machine resume from s3/s4, the codec gpio data will be cleared to 0 by BIOS: Before suspend: IO[3]: enable=1, dir=1, wake=0, sticky=0, data=1, unsol=0 After resume: IO[3]: enable=1, dir=1, wake=0, sticky=0, data=0, unsol=0 To skip the AFG node to enter D3 can't fix this problem. A workaround is to restore the gpio data when the system resume back from s3/s4. It is safe even on the machines without this problem. BugLink: https://bugs.launchpad.net/bugs/1358116 Tested-by: Franz Hsieh Cc: sta...@vger.kernel.org Signed-off-by: Hui Wang Signed-off-by: Takashi Iwai ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358116] Re: The mute led status can't be kept after s3/s4
** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Importance: Undecided => High ** Changed in: hwe-next Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358116 Title: The mute led status can't be kept after s3/s4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs