[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
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- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Tags removed: verification-needed-bionic ** Tags added: kernel-fixup-verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
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- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
This bug was fixed in the package linux-oem - 4.13.0-1024.27 --- linux-oem (4.13.0-1024.27) xenial; urgency=medium * linux-oem: 4.13.0-1024.27 -proposed tracker (LP: #1763296) * [8086:3e92] display becomes blank after S3 (LP: #1763271) - drm/i915/edp: Allow alternate fixed mode for eDP if available. - drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp - drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp - drm/i915/edp: Do not do link training fallback or prune modes on EDP * No network with e1000e driver on 4.13.0-38-generic (LP: #1762693) - e1000e: Fix e1000_check_for_copper_link_ich8lan return value. linux-oem (4.13.0-1023.25) xenial; urgency=medium * linux-oem: 4.13.0-1023.25 -proposed tracker (LP: #1761464) * Fix Runtime PM for r8169 (LP: #1757422) - r8169: only enable PCI wakeups when WOL is active - PCI: Add pcim_set_mwi(), a device-managed pci_set_mwi() - r8169: switch to device-managed functions in probe - r8169: remove netif_napi_del in probe error path - r8169: remove unneeded rpm ops in rtl_shutdown - r8169: improve runtime pm in rtl8169_check_link_status - r8169: improve runtime pm in general and suspend unused ports * Ryzen/Raven Ridge USB ports do not work (LP: #1756700) - xhci: Fix front USB ports on ASUS PRIME B350M-A - SAUCE: xhci: Fix USB ports for Dell Inspiron 5775 * Miscellaneous Ubuntu changes - Rebase to 4.13.0-39.44 [ Ubuntu: 4.13.0-39.44 ] * linux: 4.13.0-39.44 -proposed tracker (LP: #1761456) * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel) // CVE-2017-5754 - x86/mm: Reinitialize TLB state on hotplug and resume * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel) - Revert "x86/mm: Only set IBPB when the new thread cannot ptrace current thread" - x86/speculation: Use Indirect Branch Prediction Barrier in context switch * DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel (LP: #1760876) - [Packaging] include the retpoline extractor in the headers * retpoline hints: primary infrastructure and initial hints (LP: #1758856) - [Packaging] retpoline-extract: flag *0xNNN(%reg) branches - x86/speculation, objtool: Annotate indirect calls/jumps for objtool - x86/speculation, objtool: Annotate indirect calls/jumps for objtool on 32bit - x86/paravirt, objtool: Annotate indirect calls - [Packaging] retpoline -- add safe usage hint support - [Packaging] retpoline-check -- only report additions - [Packaging] retpoline -- widen indirect call/jmp detection - [Packaging] retpoline -- elide %rip relative indirections - [Packaging] retpoline -- clear hint information from packages - KVM: x86: Make indirect calls in emulator speculation safe - KVM: VMX: Make indirect call speculation safe - x86/boot, objtool: Annotate indirect jump in secondary_startup_64() - SAUCE: early/late -- annotate indirect calls in early/late initialisation code - SAUCE: vga_set_mode -- avoid jump tables - [Config] retpoline -- switch to new format - [Packaging] retpoline hints -- handle missing files when RETPOLINE not enabled - [Packaging] final-checks -- remove check for empty retpoline files * retpoline: ignore %cs:0xNNN constant indirections (LP: #1752655) - [Packaging] retpoline -- elide %cs:0x constants on i386 * zfs system process hung on container stop/delete (LP: #1754584) - SAUCE: Fix non-prefaulted page deadlock (LP: #1754584) * zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2 (LP: #1737761) - SAUCE: (noup) Update zfs to 0.6.5.11-1ubuntu3.2 * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 (LP: #1759312) - powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features * btrfs and tar sparse truncate archives (LP: #1757565) - Btrfs: move definition of the function btrfs_find_new_delalloc_bytes - Btrfs: fix reported number of inode blocks after buffered append writes * efifb broken on ThunderX-based Gigabyte nodes (LP: #1758375) - drivers/fbdev/efifb: Allow BAR to be moved instead of claiming it * Intel i40e PF reset due to incorrect MDD detection (continues...) (LP: #1723127) - i40e/i40evf: Account for frags split over multiple descriptors in check linearize * Fix an issue that when system in S3, USB keyboard can't wake up the system. (LP: #1759511) - ACPI / PM: Allow deeper wakeup power states with no _SxD nor _SxW * [8086:3e92] display becomes blank after S3 (LP: #1759188) - drm/i915: Apply Display WA #1183 on skl, kbl, and cfl * add audio kernel patches for Raven (LP: #
[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
This bug was fixed in the package linux - 4.13.0-39.44 --- linux (4.13.0-39.44) artful; urgency=medium * linux: 4.13.0-39.44 -proposed tracker (LP: #1761456) * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel) // CVE-2017-5754 - x86/mm: Reinitialize TLB state on hotplug and resume * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel) - Revert "x86/mm: Only set IBPB when the new thread cannot ptrace current thread" - x86/speculation: Use Indirect Branch Prediction Barrier in context switch * DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel (LP: #1760876) - [Packaging] include the retpoline extractor in the headers * retpoline hints: primary infrastructure and initial hints (LP: #1758856) - [Packaging] retpoline-extract: flag *0xNNN(%reg) branches - x86/speculation, objtool: Annotate indirect calls/jumps for objtool - x86/speculation, objtool: Annotate indirect calls/jumps for objtool on 32bit - x86/paravirt, objtool: Annotate indirect calls - [Packaging] retpoline -- add safe usage hint support - [Packaging] retpoline-check -- only report additions - [Packaging] retpoline -- widen indirect call/jmp detection - [Packaging] retpoline -- elide %rip relative indirections - [Packaging] retpoline -- clear hint information from packages - KVM: x86: Make indirect calls in emulator speculation safe - KVM: VMX: Make indirect call speculation safe - x86/boot, objtool: Annotate indirect jump in secondary_startup_64() - SAUCE: early/late -- annotate indirect calls in early/late initialisation code - SAUCE: vga_set_mode -- avoid jump tables - [Config] retpoline -- switch to new format - [Packaging] retpoline hints -- handle missing files when RETPOLINE not enabled - [Packaging] final-checks -- remove check for empty retpoline files * retpoline: ignore %cs:0xNNN constant indirections (LP: #1752655) - [Packaging] retpoline -- elide %cs:0x constants on i386 * zfs system process hung on container stop/delete (LP: #1754584) - SAUCE: Fix non-prefaulted page deadlock (LP: #1754584) * zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2 (LP: #1737761) - SAUCE: (noup) Update zfs to 0.6.5.11-1ubuntu3.2 * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 (LP: #1759312) - powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features * btrfs and tar sparse truncate archives (LP: #1757565) - Btrfs: move definition of the function btrfs_find_new_delalloc_bytes - Btrfs: fix reported number of inode blocks after buffered append writes * efifb broken on ThunderX-based Gigabyte nodes (LP: #1758375) - drivers/fbdev/efifb: Allow BAR to be moved instead of claiming it * Intel i40e PF reset due to incorrect MDD detection (continues...) (LP: #1723127) - i40e/i40evf: Account for frags split over multiple descriptors in check linearize * Fix an issue that when system in S3, USB keyboard can't wake up the system. (LP: #1759511) - ACPI / PM: Allow deeper wakeup power states with no _SxD nor _SxW * [8086:3e92] display becomes blank after S3 (LP: #1759188) - drm/i915: Apply Display WA #1183 on skl, kbl, and cfl * add audio kernel patches for Raven (LP: #1758364) - ALSA: hda: Add Raven PCI ID - ALSA: hda/realtek - Fix ALC700 family no sound issue * Cpu utilization showing system time for kvm guests (performance) (sysstat) (LP: #1755979) - KVM: PPC: Book3S HV: Fix guest time accounting with VIRT_CPU_ACCOUNTING_GEN * Kernel panic on a nfsroot system (LP: #1734327) - Revert "UBUNTU: SAUCE: LSM stacking: add stacking support to apparmor network hooks" - Revert "UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of the remaining blobs" * can't record sound via front headset port on the Dell Precision 3630 (LP: #1759088) - ALSA: hda/realtek - Fix Dell headset Mic can't record * speaker can't output sound anymore after system resumes from S3 on a lenovo machine with alc257 (LP: #1758829) - ALSA: hda/realtek - Fix speaker no sound after system resume * hda driver initialization takes too much time on the machine with coffeelake audio controller [8086:a348] (LP: #1758800) - ALSA: hda - Force polling mode on CFL for fixing codec communication * Let headset-mode initialization be called on Dell Precision 3930 (LP: #1757584) - ALSA: hda/realtek - Add headset mode support for Dell laptop * ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64 (LP: #1755073) - SAUCE: crypto: thunderx_zip: Fix fallou
[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
This bug was fixed in the package linux - 4.15.0-15.16 --- linux (4.15.0-15.16) bionic; urgency=medium * linux: 4.15.0-15.16 -proposed tracker (LP: #1761177) * FFe: Enable configuring resume offset via sysfs (LP: #1760106) - PM / hibernate: Make passing hibernate offsets more friendly * /dev/bcache/by-uuid links not created after reboot (LP: #1729145) - SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE uevent * Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) (LP: #1752026) - powerpc: Use feature bit for RTC presence rather than timebase presence - powerpc: Book E: Remove unused CPU_FTR_L2CSR bit - powerpc: Free up CPU feature bits on 64-bit machines - powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2 - powerpc/powernv: Provide a way to force a core into SMT4 mode - KVM: PPC: Book3S HV: Work around transactional memory bugs in POWER9 - KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode - KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state * Important Kernel fixes to be backported for Power9 (kvm) (LP: #1758910) - powerpc/mm: Fixup tlbie vs store ordering issue on POWER9 * Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe) (LP: #1757497) - powerpc/64s: Fix lost pending interrupt due to race causing lost update to irq_happened * fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build (LP: #1760876) - [Packaging] include the retpoline extractor in the headers linux (4.15.0-14.15) bionic; urgency=medium * linux: 4.15.0-14.15 -proposed tracker (LP: #1760678) * [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor (LP: #1758662) - net/mlx4_en: Change default QoS settings * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 (LP: #1759312) - powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features * Bionic update to 4.15.15 stable release (LP: #1760585) - net: dsa: Fix dsa_is_user_port() test inversion - openvswitch: meter: fix the incorrect calculation of max delta_t - qed: Fix MPA unalign flow in case header is split across two packets. - tcp: purge write queue upon aborting the connection - qed: Fix non TCP packets should be dropped on iWARP ll2 connection - sysfs: symlink: export sysfs_create_link_nowarn() - net: phy: relax error checking when creating sysfs link netdev->phydev - devlink: Remove redundant free on error path - macvlan: filter out unsupported feature flags - net: ipv6: keep sk status consistent after datagram connect failure - ipv6: old_dport should be a __be16 in __ip6_datagram_connect() - ipv6: sr: fix NULL pointer dereference when setting encap source address - ipv6: sr: fix scheduling in RCU when creating seg6 lwtunnel state - mlxsw: spectrum_buffers: Set a minimum quota for CPU port traffic - net: phy: Tell caller result of phy_change() - ipv6: Reflect MTU changes on PMTU of exceptions for MTU-less routes - net sched actions: return explicit error when tunnel_key mode is not specified - ppp: avoid loop in xmit recursion detection code - rhashtable: Fix rhlist duplicates insertion - test_rhashtable: add test case for rhltable with duplicate objects - kcm: lock lower socket in kcm_attach - sch_netem: fix skb leak in netem_enqueue() - ieee802154: 6lowpan: fix possible NULL deref in lowpan_device_event() - net: use skb_to_full_sk() in skb_update_prio() - net: Fix hlist corruptions in inet_evict_bucket() - s390/qeth: free netdevice when removing a card - s390/qeth: when thread completes, wake up all waiters - s390/qeth: lock read device while queueing next buffer - s390/qeth: on channel error, reject further cmd requests - soc/fsl/qbman: fix issue in qman_delete_cgr_safe() - dpaa_eth: fix error in dpaa_remove() - dpaa_eth: remove duplicate initialization - dpaa_eth: increment the RX dropped counter when needed - dpaa_eth: remove duplicate increment of the tx_errors counter - dccp: check sk for closed state in dccp_sendmsg() - ipv6: fix access to non-linear packet in ndisc_fill_redirect_hdr_option() - l2tp: do not accept arbitrary sockets - net: ethernet: arc: Fix a potential memory leak if an optional regulator is deferred - net: ethernet: ti: cpsw: add check for in-band mode setting with RGMII PHY interface - net: fec: Fix unbalanced PM runtime calls - net/iucv: Free memory obtained by kzalloc - netlink: avoid a double skb free in genlmsg_mcast() - net: Only honor ifindex in IP_PKTINFO if non-0 - net: systemport: Rewrite __bcm_sysport_tx_reclaim() - qed
[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
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- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. 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-artful -- 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
The system can get woken up by USB keyboard in -1023. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
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- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. 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-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Changed in: linux-oem (Ubuntu Xenial) Status: New => 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Changed in: linux (Ubuntu Artful) Status: In Progress => 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Changed in: linux (Ubuntu Artful) Status: New => In Progress -- 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Status in linux source package in Artful: New Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: New Status in linux source package in Artful: New Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Tags added: dawson originate-from-1757305 -- 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/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+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
