[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-06 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.3.0-24.26

---
linux (5.3.0-24.26) eoan; urgency=medium

  * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)

  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- Btrfs: fix inode cache block reserve leak on failure to allocate data 
space
- btrfs: qgroup: Always free PREALLOC META reserve in
  btrfs_delalloc_release_extents()
- iio: adc: meson_saradc: Fix memory allocation order
- iio: fix center temperature of bmc150-accel-core
- libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
- perf tests: Avoid raising SEGV using an obvious NULL dereference
- perf map: Fix overlapped map handling
- perf script brstackinsn: Fix recovery from LBR/binary mismatch
- perf jevents: Fix period for Intel fixed counters
- perf tools: Propagate get_cpuid() error
- perf annotate: Propagate perf_env__arch() error
- perf annotate: Fix the signedness of failure returns
- perf annotate: Propagate the symbol__annotate() error return
- perf annotate: Fix arch specific ->init() failure errors
- perf annotate: Return appropriate error code for allocation failures
- perf annotate: Don't return -1 for error when doing BPF disassembly
- staging: rtl8188eu: fix null dereference when kzalloc fails
- RDMA/siw: Fix serialization issue in write_space()
- RDMA/hfi1: Prevent memory leak in sdma_init
- RDMA/iw_cxgb4: fix SRQ access from dump_qp()
- RDMA/iwcm: Fix a lock inversion issue
- HID: hyperv: Use in-place iterator API in the channel callback
- kselftest: exclude failed TARGETS from runlist
- selftests/kselftest/runner.sh: Add 45 second timeout per test
- nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
- arm64: cpufeature: Effectively expose FRINT capability to userspace
- arm64: Fix incorrect irqflag restore for priority masking for compat
- arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 
#1542419
- tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()'
- tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()'
- serial/sifive: select SERIAL_EARLYCON
- tty: n_hdlc: fix build on SPARC
- misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach
- RDMA/core: Fix an error handling path in 'res_get_common_doit()'
- RDMA/cm: Fix memory leak in cm_add/remove_one
- RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path
- RDMA/mlx5: Do not allow rereg of a ODP MR
- RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu
- RDMA/mlx5: Add missing synchronize_srcu() for MW cases
- gpio: max77620: Use correct unit for debounce times
- fs: cifs: mute -Wunused-const-variable message
- arm64: vdso32: Fix broken compat vDSO build warnings
- arm64: vdso32: Detect binutils support for dmb ishld
- serial: mctrl_gpio: Check for NULL pointer
- serial: 8250_omap: Fix gpio check for auto RTS/CTS
- arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG
- arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally
- efi/cper: Fix endianness of PCIe class code
- efi/x86: Do not clean dummy variable in kexec path
- MIPS: include: Mark __cmpxchg as __always_inline
- riscv: avoid kernel hangs when trapped in BUG()
- riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
- riscv: Correct the handling of unexpected ebreak in do_trap_break()
- x86/xen: Return from panic notifier
- ocfs2: clear zero in unaligned direct IO
- fs: ocfs2: fix possible null-pointer dereferences in
  ocfs2_xa_prepare_entry()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_write_end_nolock()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_info_scan_inode_alloc()
- btrfs: silence maybe-uninitialized warning in clone_range
- arm64: armv8_deprecated: Checking return value for memory allocation
- sched/fair: Scale bandwidth quota and period without losing quota/period
  ratio precision
- sched/vtime: Fix guest/system mis-accounting on task switch
- perf/core: Rework memory accounting in perf_mmap()
- perf/core: Fix corner case in perf_rotate_context()
- perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp
- drm/amdgpu: fix memory leak
- iio: imu: adis16400: release allocated memory on failure
- iio: imu: adis16400: fix memory leak
- iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller
- MIPS: include: Mark __xchg as __always_inline
- MIPS: fw: sni: Fix out of bounds init of o32 stack
- s390/cio: fix virtio-ccw DMA without PV
- virt: vbox: fix memory 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34

---
linux-oem-osp1 (5.0.0-1030.34) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1030.34 -proposed tracker (LP:
#1853116)

  * Add support for Realtek 8723DE wireless adapter (LP: #1780590)
- SAUCE: rtw88: 8822c: update PHY parameter to v38
- SAUCE: rtw88: 8822c: update pwr_seq to v13
- SAUCE: rtw88: 8822c: Enable interrupt migration
- SAUCE: rtw88: 8822c: add FW IQK support
- SAUCE: rtw88: 8822c: add SW DPK support
- SAUCE: rtw88: move IQK/DPK into phy_calibration
- SAUCE: rtw88: add dynamic cck pd mechanism
- SAUCE: rtw88: allows to receive AMSDU in AMPDU
- SAUCE: rtw88: remove redundant flag check helper function
- SAUCE: rtw88: pci: extract skbs free routine for trx rings
- SAUCE: rtw88: pci: release tx skbs DMAed when stop
- SAUCE: rtw88: not to enter or leave PS under IRQ
- SAUCE: rtw88: not to control LPS by each vif
- SAUCE: rtw88: remove unused lps state check helper
- SAUCE: rtw88: LPS enter/leave should be protected by lock
- SAUCE: rtw88: leave PS state for dynamic mechanism
- SAUCE: rtw88: add deep power save support
- SAUCE: rtw88: not to enter LPS by coex strategy
- SAUCE: rtw88: select deep PS mode when module is inserted
- SAUCE: rtw88: add deep PS PG mode for 8822c
- SAUCE: rtw88: add RTS support
- SAUCE: rtw88: add driver tx queue support
- SAUCE: rtw88: take over rate control from mac80211
- SAUCE: rtw88: report tx rate to mac80211 stack
- SAUCE: rtw88: add TX-AMSDU support
- SAUCE: rtw88: add power tracking support
- SAUCE: rtw88: Enable 802.11ac beamformee support
- SAUCE: rtw88: flush hardware tx queues
- SAUCE: rtw88: config 8822c multicast address in MAC init flow
- SAUCE: rtw88: add set_bitrate_mask support
- SAUCE: rtw88: use struct rtw_fw_hdr to access firmware header
- SAUCE: rtw88: fix NSS of hw_cap
- SAUCE: rtw88: fix error handling when setup efuse info
- SAUCE: rtw88: fix wrong rx power calculation
- SAUCE: rtw88: update regulatory settings implementaion
- SAUCE: rtw88: check firmware leave lps successfully
- SAUCE: rtw88: support wowlan feature for 8822c
- SAUCE: rtw88: wowlan: support pattern match
- SAUCE: rtw88: wowlan: support PNO for 8822C
- SAUCE: rtw88: add phy_info debugfs to show Tx/Rx physical status
- SAUCE: rtw88: coex: Set 4 slot mode for A2DP
- SAUCE: rtw88: default enable LPS + LCLK
- SAUCE: rtw88: add module parameter to enable PCIE clock request
- SAUCE: rtw88: add module parameter to enable PCIE ASPM L1
- SAUCE: rtw88: fix TX secondary channel offset of 40M if current bw is 20M 
or
  40M
- SAUCE: rtw88: Use secondary channel offset enumeration to make better read
- SAUCE: rtw88: keep leave and enter IPS as the first and last in config
  callback
- SAUCE: rtw88: fix rate mask for 1SS chip
- SAUCE: rtw88: refine conversion of rx_evm_dbm from rx_evm
- SAUCE: rtw88: 8723d: Add basic chip information of 8723D
- SAUCE: rtw88: 8723de: Add 8723DE to Kconfig and Makefile
- SAUCE: rtw88: 8723d: check set_gid_table before calling
- SAUCE: rtw88: 8723d: Add power sequence
- SAUCE: rtw88: 8723d: Add RF read/write ops
- SAUCE: rtw88: 8723d: Add mac/bb/rf/agc/power_limit tables
- SAUCE: rtw88: 8723d: Add ops cfg_ldo25 to control LDO25
- SAUCE: rtw88: 8723d: Add ops efuse_en to enable/disable efuse access
- SAUCE: rtw88: 8723d: Add read_efuse ops to recognize efuse info from map
- SAUCE: rtw88: add legacy firmware download for 8723de
- SAUCE: rtw88: Don't need send additional information to legacy firmware
- SAUCE: rtw88: 8723d: Implement mac power-on/-off function
- SAUCE: rtw88: decompose while(1) loop of power sequence polling command
- SAUCE: rtw88: 8723d: 11N chips don't support H2C queue
- SAUCE: rtw88: 8723d: implement ops set_tx_power_index to set tx power
- SAUCE: rtw88: 8723d: Organize chip TX/RX FIFO
- SAUCE: rtw88: 8723d: initialize mac/bb/rf basic functions
- SAUCE: rtw88: 8723d: Add DIG parameter
- SAUCE: rtw88: 8723d: Add ops query_rx_desc
- SAUCE: rtw88: 8723d: Add ops set_channel
- SAUCE: rtw88: handle C2H_CCX_TX_RPT (0x03) to know if packet TX 
successfully
- SAUCE: rtw88: 8723d: Add LDPC cap to chip info
- SAUCE: rtw88: 8723d: 11N chip doesn't have LS field in TX descriptor
- SAUCE: rtw88: 8723d: Add ops false_alarm_statistics
- SAUCE: rtw88: 8723d: Set IG register for CCK rate
- SAUCE: rtw88: 8723d: add interface configurations table
- SAUCE: rtw88: 8723d: Add LC calibration
- SAUCE: rtw88: 8723d: add IQ calibration
- SAUCE: rtw88: 8723d: Add power tracking
- SAUCE: rtw88: 8723d: Add shutdown callback to disable USB suspend
- SAUCE: rtw88: 8723d: implement flush queue
- SAUCE: rtw88: 8723d: set ltecoex register address in chip_info
- 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34

---
linux-oem-osp1 (5.0.0-1030.34) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1030.34 -proposed tracker (LP:
#1853116)

  * Add support for Realtek 8723DE wireless adapter (LP: #1780590)
- SAUCE: rtw88: 8822c: update PHY parameter to v38
- SAUCE: rtw88: 8822c: update pwr_seq to v13
- SAUCE: rtw88: 8822c: Enable interrupt migration
- SAUCE: rtw88: 8822c: add FW IQK support
- SAUCE: rtw88: 8822c: add SW DPK support
- SAUCE: rtw88: move IQK/DPK into phy_calibration
- SAUCE: rtw88: add dynamic cck pd mechanism
- SAUCE: rtw88: allows to receive AMSDU in AMPDU
- SAUCE: rtw88: remove redundant flag check helper function
- SAUCE: rtw88: pci: extract skbs free routine for trx rings
- SAUCE: rtw88: pci: release tx skbs DMAed when stop
- SAUCE: rtw88: not to enter or leave PS under IRQ
- SAUCE: rtw88: not to control LPS by each vif
- SAUCE: rtw88: remove unused lps state check helper
- SAUCE: rtw88: LPS enter/leave should be protected by lock
- SAUCE: rtw88: leave PS state for dynamic mechanism
- SAUCE: rtw88: add deep power save support
- SAUCE: rtw88: not to enter LPS by coex strategy
- SAUCE: rtw88: select deep PS mode when module is inserted
- SAUCE: rtw88: add deep PS PG mode for 8822c
- SAUCE: rtw88: add RTS support
- SAUCE: rtw88: add driver tx queue support
- SAUCE: rtw88: take over rate control from mac80211
- SAUCE: rtw88: report tx rate to mac80211 stack
- SAUCE: rtw88: add TX-AMSDU support
- SAUCE: rtw88: add power tracking support
- SAUCE: rtw88: Enable 802.11ac beamformee support
- SAUCE: rtw88: flush hardware tx queues
- SAUCE: rtw88: config 8822c multicast address in MAC init flow
- SAUCE: rtw88: add set_bitrate_mask support
- SAUCE: rtw88: use struct rtw_fw_hdr to access firmware header
- SAUCE: rtw88: fix NSS of hw_cap
- SAUCE: rtw88: fix error handling when setup efuse info
- SAUCE: rtw88: fix wrong rx power calculation
- SAUCE: rtw88: update regulatory settings implementaion
- SAUCE: rtw88: check firmware leave lps successfully
- SAUCE: rtw88: support wowlan feature for 8822c
- SAUCE: rtw88: wowlan: support pattern match
- SAUCE: rtw88: wowlan: support PNO for 8822C
- SAUCE: rtw88: add phy_info debugfs to show Tx/Rx physical status
- SAUCE: rtw88: coex: Set 4 slot mode for A2DP
- SAUCE: rtw88: default enable LPS + LCLK
- SAUCE: rtw88: add module parameter to enable PCIE clock request
- SAUCE: rtw88: add module parameter to enable PCIE ASPM L1
- SAUCE: rtw88: fix TX secondary channel offset of 40M if current bw is 20M 
or
  40M
- SAUCE: rtw88: Use secondary channel offset enumeration to make better read
- SAUCE: rtw88: keep leave and enter IPS as the first and last in config
  callback
- SAUCE: rtw88: fix rate mask for 1SS chip
- SAUCE: rtw88: refine conversion of rx_evm_dbm from rx_evm
- SAUCE: rtw88: 8723d: Add basic chip information of 8723D
- SAUCE: rtw88: 8723de: Add 8723DE to Kconfig and Makefile
- SAUCE: rtw88: 8723d: check set_gid_table before calling
- SAUCE: rtw88: 8723d: Add power sequence
- SAUCE: rtw88: 8723d: Add RF read/write ops
- SAUCE: rtw88: 8723d: Add mac/bb/rf/agc/power_limit tables
- SAUCE: rtw88: 8723d: Add ops cfg_ldo25 to control LDO25
- SAUCE: rtw88: 8723d: Add ops efuse_en to enable/disable efuse access
- SAUCE: rtw88: 8723d: Add read_efuse ops to recognize efuse info from map
- SAUCE: rtw88: add legacy firmware download for 8723de
- SAUCE: rtw88: Don't need send additional information to legacy firmware
- SAUCE: rtw88: 8723d: Implement mac power-on/-off function
- SAUCE: rtw88: decompose while(1) loop of power sequence polling command
- SAUCE: rtw88: 8723d: 11N chips don't support H2C queue
- SAUCE: rtw88: 8723d: implement ops set_tx_power_index to set tx power
- SAUCE: rtw88: 8723d: Organize chip TX/RX FIFO
- SAUCE: rtw88: 8723d: initialize mac/bb/rf basic functions
- SAUCE: rtw88: 8723d: Add DIG parameter
- SAUCE: rtw88: 8723d: Add ops query_rx_desc
- SAUCE: rtw88: 8723d: Add ops set_channel
- SAUCE: rtw88: handle C2H_CCX_TX_RPT (0x03) to know if packet TX 
successfully
- SAUCE: rtw88: 8723d: Add LDPC cap to chip info
- SAUCE: rtw88: 8723d: 11N chip doesn't have LS field in TX descriptor
- SAUCE: rtw88: 8723d: Add ops false_alarm_statistics
- SAUCE: rtw88: 8723d: Set IG register for CCK rate
- SAUCE: rtw88: 8723d: add interface configurations table
- SAUCE: rtw88: 8723d: Add LC calibration
- SAUCE: rtw88: 8723d: add IQ calibration
- SAUCE: rtw88: 8723d: Add power tracking
- SAUCE: rtw88: 8723d: Add shutdown callback to disable USB suspend
- SAUCE: rtw88: 8723d: implement flush queue
- SAUCE: rtw88: 8723d: set ltecoex register address in chip_info
- 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1065.75

---
linux-oem (4.15.0-1065.75) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1065.74 -proposed tracker (LP: #1852266)

  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- [Config] updateconfigs for USB_RIO500

  * Disable unreliable HPET on CFL-H system (LP: #1852216)
- SAUCE: x86/intel: Disable HPET on Intel Coffe Lake H platforms

  [ Ubuntu: 4.15.0-71.80 ]

  * bionic/linux: 4.15.0-71.80 -proposed tracker (LP: #1852289)
  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- panic: ensure preemption is disabled during panic()
- f2fs: use EINVAL for superblock with invalid magic
- [Config] updateconfigs for USB_RIO500
- USB: rio500: Remove Rio 500 kernel driver
- USB: yurex: Don't retry on unexpected errors
- USB: yurex: fix NULL-derefs on disconnect
- USB: usb-skeleton: fix runtime PM after driver unbind
- USB: usb-skeleton: fix NULL-deref on disconnect
- xhci: Fix false warning message about wrong bounce buffer write length
- xhci: Prevent device initiated U1/U2 link pm if exit latency is too long
- xhci: Check all endpoints for LPM timeout
- usb: xhci: wait for CNR controller not ready bit in xhci resume
- USB: adutux: fix use-after-free on disconnect
- USB: adutux: fix NULL-derefs on disconnect
- USB: adutux: fix use-after-free on release
- USB: iowarrior: fix use-after-free on disconnect
- USB: iowarrior: fix use-after-free on release
- USB: iowarrior: fix use-after-free after driver unbind
- USB: usblp: fix runtime PM after driver unbind
- USB: chaoskey: fix use-after-free on release
- USB: ldusb: fix NULL-derefs on driver unbind
- serial: uartlite: fix exit path null pointer
- USB: serial: keyspan: fix NULL-derefs on open() and write()
- USB: serial: ftdi_sio: add device IDs for Sienna and Echelon PL-20
- USB: serial: option: add Telit FN980 compositions
- USB: serial: option: add support for Cinterion CLS8 devices
- USB: serial: fix runtime PM after driver unbind
- USB: usblcd: fix I/O after disconnect
- USB: microtek: fix info-leak at probe
- USB: dummy-hcd: fix power budget for SuperSpeed mode
- usb: renesas_usbhs: gadget: Do not discard queues in
  usb_ep_set_{halt,wedge}()
- usb: renesas_usbhs: gadget: Fix usb_ep_set_{halt,wedge}() behavior
- USB: legousbtower: fix slab info leak at probe
- USB: legousbtower: fix deadlock on disconnect
- USB: legousbtower: fix potential NULL-deref on disconnect
- USB: legousbtower: fix open after failed reset request
- USB: legousbtower: fix use-after-free on release
- staging: vt6655: Fix memory leak in vt6655_probe
- iio: adc: ad799x: fix probe error handling
- iio: adc: axp288: Override TS pin bias current for some models
- iio: light: opt3001: fix mutex unlock race
- efivar/ssdt: Don't iterate over EFI vars if no SSDT override was specified
- perf llvm: Don't access out-of-scope array
- perf inject jit: Fix JIT_CODE_MOVE filename
- CIFS: Gracefully handle QueryInfo errors during open
- CIFS: Force revalidate inode when dentry is stale
- CIFS: Force reval dentry if LOOKUP_REVAL flag is set
- kernel/sysctl.c: do not override max_threads provided by userspace
- firmware: google: increment VPD key_len properly
- gpiolib: don't clear FLAG_IS_OUT when emulating open-drain/open-source
- Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc
- iio: hx711: add delay until DOUT is ready
- iio: adc: hx711: fix bug in sampling of data
- btrfs: fix incorrect updating of log root tree
- NFS: Fix O_DIRECT accounting of number of bytes read/written
- MIPS: Disable Loongson MMI instructions for kernel build
- Fix the locking in dcache_readdir() and friends
- media: stkwebcam: fix runtime PM after driver unbind
- tracing/hwlat: Report total time spent in all NMIs during the sample
- tracing/hwlat: Don't ignore outer-loop duration when calculating 
max_latency
- ftrace: Get a reference counter for the trace_array on filter files
- tracing: Get trace_array reference for available_tracers files
- x86/asm: Fix MWAITX C-state hint value
- iio: adc: stm32-adc: fix a race when using several adcs with dma and irq
- cifs: use cifsInodeInfo->open_file_lock while iterating to avoid a panic
- btrfs: fix uninitialized ret in ref-verify
- arm64/sve: Fix wrong free for task->thread.sve_state
- [Config] updateconfigs for USB_RIO500
  * Bionic update: upstream stable patchset 2019-11-13 (LP: #1852492)
- zram: fix race between backing_dev_show and backing_dev_store
- dm snapshot: use mutex instead of rw_semaphore
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- dm: Use kzalloc for all structs with 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1065.75

---
linux-oem (4.15.0-1065.75) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1065.74 -proposed tracker (LP: #1852266)

  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- [Config] updateconfigs for USB_RIO500

  * Disable unreliable HPET on CFL-H system (LP: #1852216)
- SAUCE: x86/intel: Disable HPET on Intel Coffe Lake H platforms

  [ Ubuntu: 4.15.0-71.80 ]

  * bionic/linux: 4.15.0-71.80 -proposed tracker (LP: #1852289)
  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- panic: ensure preemption is disabled during panic()
- f2fs: use EINVAL for superblock with invalid magic
- [Config] updateconfigs for USB_RIO500
- USB: rio500: Remove Rio 500 kernel driver
- USB: yurex: Don't retry on unexpected errors
- USB: yurex: fix NULL-derefs on disconnect
- USB: usb-skeleton: fix runtime PM after driver unbind
- USB: usb-skeleton: fix NULL-deref on disconnect
- xhci: Fix false warning message about wrong bounce buffer write length
- xhci: Prevent device initiated U1/U2 link pm if exit latency is too long
- xhci: Check all endpoints for LPM timeout
- usb: xhci: wait for CNR controller not ready bit in xhci resume
- USB: adutux: fix use-after-free on disconnect
- USB: adutux: fix NULL-derefs on disconnect
- USB: adutux: fix use-after-free on release
- USB: iowarrior: fix use-after-free on disconnect
- USB: iowarrior: fix use-after-free on release
- USB: iowarrior: fix use-after-free after driver unbind
- USB: usblp: fix runtime PM after driver unbind
- USB: chaoskey: fix use-after-free on release
- USB: ldusb: fix NULL-derefs on driver unbind
- serial: uartlite: fix exit path null pointer
- USB: serial: keyspan: fix NULL-derefs on open() and write()
- USB: serial: ftdi_sio: add device IDs for Sienna and Echelon PL-20
- USB: serial: option: add Telit FN980 compositions
- USB: serial: option: add support for Cinterion CLS8 devices
- USB: serial: fix runtime PM after driver unbind
- USB: usblcd: fix I/O after disconnect
- USB: microtek: fix info-leak at probe
- USB: dummy-hcd: fix power budget for SuperSpeed mode
- usb: renesas_usbhs: gadget: Do not discard queues in
  usb_ep_set_{halt,wedge}()
- usb: renesas_usbhs: gadget: Fix usb_ep_set_{halt,wedge}() behavior
- USB: legousbtower: fix slab info leak at probe
- USB: legousbtower: fix deadlock on disconnect
- USB: legousbtower: fix potential NULL-deref on disconnect
- USB: legousbtower: fix open after failed reset request
- USB: legousbtower: fix use-after-free on release
- staging: vt6655: Fix memory leak in vt6655_probe
- iio: adc: ad799x: fix probe error handling
- iio: adc: axp288: Override TS pin bias current for some models
- iio: light: opt3001: fix mutex unlock race
- efivar/ssdt: Don't iterate over EFI vars if no SSDT override was specified
- perf llvm: Don't access out-of-scope array
- perf inject jit: Fix JIT_CODE_MOVE filename
- CIFS: Gracefully handle QueryInfo errors during open
- CIFS: Force revalidate inode when dentry is stale
- CIFS: Force reval dentry if LOOKUP_REVAL flag is set
- kernel/sysctl.c: do not override max_threads provided by userspace
- firmware: google: increment VPD key_len properly
- gpiolib: don't clear FLAG_IS_OUT when emulating open-drain/open-source
- Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc
- iio: hx711: add delay until DOUT is ready
- iio: adc: hx711: fix bug in sampling of data
- btrfs: fix incorrect updating of log root tree
- NFS: Fix O_DIRECT accounting of number of bytes read/written
- MIPS: Disable Loongson MMI instructions for kernel build
- Fix the locking in dcache_readdir() and friends
- media: stkwebcam: fix runtime PM after driver unbind
- tracing/hwlat: Report total time spent in all NMIs during the sample
- tracing/hwlat: Don't ignore outer-loop duration when calculating 
max_latency
- ftrace: Get a reference counter for the trace_array on filter files
- tracing: Get trace_array reference for available_tracers files
- x86/asm: Fix MWAITX C-state hint value
- iio: adc: stm32-adc: fix a race when using several adcs with dma and irq
- cifs: use cifsInodeInfo->open_file_lock while iterating to avoid a panic
- btrfs: fix uninitialized ret in ref-verify
- arm64/sve: Fix wrong free for task->thread.sve_state
- [Config] updateconfigs for USB_RIO500
  * Bionic update: upstream stable patchset 2019-11-13 (LP: #1852492)
- zram: fix race between backing_dev_show and backing_dev_store
- dm snapshot: use mutex instead of rw_semaphore
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- dm: Use kzalloc for all structs with 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1065.75

---
linux-oem (4.15.0-1065.75) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1065.74 -proposed tracker (LP: #1852266)

  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- [Config] updateconfigs for USB_RIO500

  * Disable unreliable HPET on CFL-H system (LP: #1852216)
- SAUCE: x86/intel: Disable HPET on Intel Coffe Lake H platforms

  [ Ubuntu: 4.15.0-71.80 ]

  * bionic/linux: 4.15.0-71.80 -proposed tracker (LP: #1852289)
  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- panic: ensure preemption is disabled during panic()
- f2fs: use EINVAL for superblock with invalid magic
- [Config] updateconfigs for USB_RIO500
- USB: rio500: Remove Rio 500 kernel driver
- USB: yurex: Don't retry on unexpected errors
- USB: yurex: fix NULL-derefs on disconnect
- USB: usb-skeleton: fix runtime PM after driver unbind
- USB: usb-skeleton: fix NULL-deref on disconnect
- xhci: Fix false warning message about wrong bounce buffer write length
- xhci: Prevent device initiated U1/U2 link pm if exit latency is too long
- xhci: Check all endpoints for LPM timeout
- usb: xhci: wait for CNR controller not ready bit in xhci resume
- USB: adutux: fix use-after-free on disconnect
- USB: adutux: fix NULL-derefs on disconnect
- USB: adutux: fix use-after-free on release
- USB: iowarrior: fix use-after-free on disconnect
- USB: iowarrior: fix use-after-free on release
- USB: iowarrior: fix use-after-free after driver unbind
- USB: usblp: fix runtime PM after driver unbind
- USB: chaoskey: fix use-after-free on release
- USB: ldusb: fix NULL-derefs on driver unbind
- serial: uartlite: fix exit path null pointer
- USB: serial: keyspan: fix NULL-derefs on open() and write()
- USB: serial: ftdi_sio: add device IDs for Sienna and Echelon PL-20
- USB: serial: option: add Telit FN980 compositions
- USB: serial: option: add support for Cinterion CLS8 devices
- USB: serial: fix runtime PM after driver unbind
- USB: usblcd: fix I/O after disconnect
- USB: microtek: fix info-leak at probe
- USB: dummy-hcd: fix power budget for SuperSpeed mode
- usb: renesas_usbhs: gadget: Do not discard queues in
  usb_ep_set_{halt,wedge}()
- usb: renesas_usbhs: gadget: Fix usb_ep_set_{halt,wedge}() behavior
- USB: legousbtower: fix slab info leak at probe
- USB: legousbtower: fix deadlock on disconnect
- USB: legousbtower: fix potential NULL-deref on disconnect
- USB: legousbtower: fix open after failed reset request
- USB: legousbtower: fix use-after-free on release
- staging: vt6655: Fix memory leak in vt6655_probe
- iio: adc: ad799x: fix probe error handling
- iio: adc: axp288: Override TS pin bias current for some models
- iio: light: opt3001: fix mutex unlock race
- efivar/ssdt: Don't iterate over EFI vars if no SSDT override was specified
- perf llvm: Don't access out-of-scope array
- perf inject jit: Fix JIT_CODE_MOVE filename
- CIFS: Gracefully handle QueryInfo errors during open
- CIFS: Force revalidate inode when dentry is stale
- CIFS: Force reval dentry if LOOKUP_REVAL flag is set
- kernel/sysctl.c: do not override max_threads provided by userspace
- firmware: google: increment VPD key_len properly
- gpiolib: don't clear FLAG_IS_OUT when emulating open-drain/open-source
- Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc
- iio: hx711: add delay until DOUT is ready
- iio: adc: hx711: fix bug in sampling of data
- btrfs: fix incorrect updating of log root tree
- NFS: Fix O_DIRECT accounting of number of bytes read/written
- MIPS: Disable Loongson MMI instructions for kernel build
- Fix the locking in dcache_readdir() and friends
- media: stkwebcam: fix runtime PM after driver unbind
- tracing/hwlat: Report total time spent in all NMIs during the sample
- tracing/hwlat: Don't ignore outer-loop duration when calculating 
max_latency
- ftrace: Get a reference counter for the trace_array on filter files
- tracing: Get trace_array reference for available_tracers files
- x86/asm: Fix MWAITX C-state hint value
- iio: adc: stm32-adc: fix a race when using several adcs with dma and irq
- cifs: use cifsInodeInfo->open_file_lock while iterating to avoid a panic
- btrfs: fix uninitialized ret in ref-verify
- arm64/sve: Fix wrong free for task->thread.sve_state
- [Config] updateconfigs for USB_RIO500
  * Bionic update: upstream stable patchset 2019-11-13 (LP: #1852492)
- zram: fix race between backing_dev_show and backing_dev_store
- dm snapshot: use mutex instead of rw_semaphore
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- dm: Use kzalloc for all structs with 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-02 Thread You-Sheng Yang
** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: New => Invalid

** Changed in: hwe-next
   Status: Triaged => 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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34

---
linux-oem-osp1 (5.0.0-1030.34) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1030.34 -proposed tracker (LP:
#1853116)

  * Add support for Realtek 8723DE wireless adapter (LP: #1780590)
- SAUCE: rtw88: 8822c: update PHY parameter to v38
- SAUCE: rtw88: 8822c: update pwr_seq to v13
- SAUCE: rtw88: 8822c: Enable interrupt migration
- SAUCE: rtw88: 8822c: add FW IQK support
- SAUCE: rtw88: 8822c: add SW DPK support
- SAUCE: rtw88: move IQK/DPK into phy_calibration
- SAUCE: rtw88: add dynamic cck pd mechanism
- SAUCE: rtw88: allows to receive AMSDU in AMPDU
- SAUCE: rtw88: remove redundant flag check helper function
- SAUCE: rtw88: pci: extract skbs free routine for trx rings
- SAUCE: rtw88: pci: release tx skbs DMAed when stop
- SAUCE: rtw88: not to enter or leave PS under IRQ
- SAUCE: rtw88: not to control LPS by each vif
- SAUCE: rtw88: remove unused lps state check helper
- SAUCE: rtw88: LPS enter/leave should be protected by lock
- SAUCE: rtw88: leave PS state for dynamic mechanism
- SAUCE: rtw88: add deep power save support
- SAUCE: rtw88: not to enter LPS by coex strategy
- SAUCE: rtw88: select deep PS mode when module is inserted
- SAUCE: rtw88: add deep PS PG mode for 8822c
- SAUCE: rtw88: add RTS support
- SAUCE: rtw88: add driver tx queue support
- SAUCE: rtw88: take over rate control from mac80211
- SAUCE: rtw88: report tx rate to mac80211 stack
- SAUCE: rtw88: add TX-AMSDU support
- SAUCE: rtw88: add power tracking support
- SAUCE: rtw88: Enable 802.11ac beamformee support
- SAUCE: rtw88: flush hardware tx queues
- SAUCE: rtw88: config 8822c multicast address in MAC init flow
- SAUCE: rtw88: add set_bitrate_mask support
- SAUCE: rtw88: use struct rtw_fw_hdr to access firmware header
- SAUCE: rtw88: fix NSS of hw_cap
- SAUCE: rtw88: fix error handling when setup efuse info
- SAUCE: rtw88: fix wrong rx power calculation
- SAUCE: rtw88: update regulatory settings implementaion
- SAUCE: rtw88: check firmware leave lps successfully
- SAUCE: rtw88: support wowlan feature for 8822c
- SAUCE: rtw88: wowlan: support pattern match
- SAUCE: rtw88: wowlan: support PNO for 8822C
- SAUCE: rtw88: add phy_info debugfs to show Tx/Rx physical status
- SAUCE: rtw88: coex: Set 4 slot mode for A2DP
- SAUCE: rtw88: default enable LPS + LCLK
- SAUCE: rtw88: add module parameter to enable PCIE clock request
- SAUCE: rtw88: add module parameter to enable PCIE ASPM L1
- SAUCE: rtw88: fix TX secondary channel offset of 40M if current bw is 20M 
or
  40M
- SAUCE: rtw88: Use secondary channel offset enumeration to make better read
- SAUCE: rtw88: keep leave and enter IPS as the first and last in config
  callback
- SAUCE: rtw88: fix rate mask for 1SS chip
- SAUCE: rtw88: refine conversion of rx_evm_dbm from rx_evm
- SAUCE: rtw88: 8723d: Add basic chip information of 8723D
- SAUCE: rtw88: 8723de: Add 8723DE to Kconfig and Makefile
- SAUCE: rtw88: 8723d: check set_gid_table before calling
- SAUCE: rtw88: 8723d: Add power sequence
- SAUCE: rtw88: 8723d: Add RF read/write ops
- SAUCE: rtw88: 8723d: Add mac/bb/rf/agc/power_limit tables
- SAUCE: rtw88: 8723d: Add ops cfg_ldo25 to control LDO25
- SAUCE: rtw88: 8723d: Add ops efuse_en to enable/disable efuse access
- SAUCE: rtw88: 8723d: Add read_efuse ops to recognize efuse info from map
- SAUCE: rtw88: add legacy firmware download for 8723de
- SAUCE: rtw88: Don't need send additional information to legacy firmware
- SAUCE: rtw88: 8723d: Implement mac power-on/-off function
- SAUCE: rtw88: decompose while(1) loop of power sequence polling command
- SAUCE: rtw88: 8723d: 11N chips don't support H2C queue
- SAUCE: rtw88: 8723d: implement ops set_tx_power_index to set tx power
- SAUCE: rtw88: 8723d: Organize chip TX/RX FIFO
- SAUCE: rtw88: 8723d: initialize mac/bb/rf basic functions
- SAUCE: rtw88: 8723d: Add DIG parameter
- SAUCE: rtw88: 8723d: Add ops query_rx_desc
- SAUCE: rtw88: 8723d: Add ops set_channel
- SAUCE: rtw88: handle C2H_CCX_TX_RPT (0x03) to know if packet TX 
successfully
- SAUCE: rtw88: 8723d: Add LDPC cap to chip info
- SAUCE: rtw88: 8723d: 11N chip doesn't have LS field in TX descriptor
- SAUCE: rtw88: 8723d: Add ops false_alarm_statistics
- SAUCE: rtw88: 8723d: Set IG register for CCK rate
- SAUCE: rtw88: 8723d: add interface configurations table
- SAUCE: rtw88: 8723d: Add LC calibration
- SAUCE: rtw88: 8723d: add IQ calibration
- SAUCE: rtw88: 8723d: Add power tracking
- SAUCE: rtw88: 8723d: Add shutdown callback to disable USB suspend
- SAUCE: rtw88: 8723d: implement flush queue
- SAUCE: rtw88: 8723d: set ltecoex register address in chip_info
- 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-72.81

---
linux (4.15.0-72.81) bionic; urgency=medium

  * bionic/linux: 4.15.0-72.81 -proposed tracker (LP: #1854027)

  * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
(LP: #1853326)
- Revert "arm64: Use firmware to detect CPUs that are not affected by
  Spectre-v2"
- Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"

  * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
Kunpeng920 (LP: #1852723)
- SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
  correct place

linux (4.15.0-71.80) bionic; urgency=medium

  * bionic/linux: 4.15.0-71.80 -proposed tracker (LP: #1852289)

  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
- panic: ensure preemption is disabled during panic()
- f2fs: use EINVAL for superblock with invalid magic
- [Config] updateconfigs for USB_RIO500
- USB: rio500: Remove Rio 500 kernel driver
- USB: yurex: Don't retry on unexpected errors
- USB: yurex: fix NULL-derefs on disconnect
- USB: usb-skeleton: fix runtime PM after driver unbind
- USB: usb-skeleton: fix NULL-deref on disconnect
- xhci: Fix false warning message about wrong bounce buffer write length
- xhci: Prevent device initiated U1/U2 link pm if exit latency is too long
- xhci: Check all endpoints for LPM timeout
- usb: xhci: wait for CNR controller not ready bit in xhci resume
- USB: adutux: fix use-after-free on disconnect
- USB: adutux: fix NULL-derefs on disconnect
- USB: adutux: fix use-after-free on release
- USB: iowarrior: fix use-after-free on disconnect
- USB: iowarrior: fix use-after-free on release
- USB: iowarrior: fix use-after-free after driver unbind
- USB: usblp: fix runtime PM after driver unbind
- USB: chaoskey: fix use-after-free on release
- USB: ldusb: fix NULL-derefs on driver unbind
- serial: uartlite: fix exit path null pointer
- USB: serial: keyspan: fix NULL-derefs on open() and write()
- USB: serial: ftdi_sio: add device IDs for Sienna and Echelon PL-20
- USB: serial: option: add Telit FN980 compositions
- USB: serial: option: add support for Cinterion CLS8 devices
- USB: serial: fix runtime PM after driver unbind
- USB: usblcd: fix I/O after disconnect
- USB: microtek: fix info-leak at probe
- USB: dummy-hcd: fix power budget for SuperSpeed mode
- usb: renesas_usbhs: gadget: Do not discard queues in
  usb_ep_set_{halt,wedge}()
- usb: renesas_usbhs: gadget: Fix usb_ep_set_{halt,wedge}() behavior
- USB: legousbtower: fix slab info leak at probe
- USB: legousbtower: fix deadlock on disconnect
- USB: legousbtower: fix potential NULL-deref on disconnect
- USB: legousbtower: fix open after failed reset request
- USB: legousbtower: fix use-after-free on release
- staging: vt6655: Fix memory leak in vt6655_probe
- iio: adc: ad799x: fix probe error handling
- iio: adc: axp288: Override TS pin bias current for some models
- iio: light: opt3001: fix mutex unlock race
- efivar/ssdt: Don't iterate over EFI vars if no SSDT override was specified
- perf llvm: Don't access out-of-scope array
- perf inject jit: Fix JIT_CODE_MOVE filename
- CIFS: Gracefully handle QueryInfo errors during open
- CIFS: Force revalidate inode when dentry is stale
- CIFS: Force reval dentry if LOOKUP_REVAL flag is set
- kernel/sysctl.c: do not override max_threads provided by userspace
- firmware: google: increment VPD key_len properly
- gpiolib: don't clear FLAG_IS_OUT when emulating open-drain/open-source
- Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc
- iio: hx711: add delay until DOUT is ready
- iio: adc: hx711: fix bug in sampling of data
- btrfs: fix incorrect updating of log root tree
- NFS: Fix O_DIRECT accounting of number of bytes read/written
- MIPS: Disable Loongson MMI instructions for kernel build
- Fix the locking in dcache_readdir() and friends
- media: stkwebcam: fix runtime PM after driver unbind
- tracing/hwlat: Report total time spent in all NMIs during the sample
- tracing/hwlat: Don't ignore outer-loop duration when calculating 
max_latency
- ftrace: Get a reference counter for the trace_array on filter files
- tracing: Get trace_array reference for available_tracers files
- x86/asm: Fix MWAITX C-state hint value
- iio: adc: stm32-adc: fix a race when using several adcs with dma and irq
- cifs: use cifsInodeInfo->open_file_lock while iterating to avoid a panic
- btrfs: fix uninitialized ret in ref-verify
- arm64/sve: Fix wrong free for task->thread.sve_state
- [Config] updateconfigs for USB_RIO500

  * Bionic update: upstream stable patchset 2019-11-13 (LP: #1852492)
- zram: fix race between backing_dev_show and backing_dev_store
- dm snapshot: use 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.3.0-24.26

---
linux (5.3.0-24.26) eoan; urgency=medium

  * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)

  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- Btrfs: fix inode cache block reserve leak on failure to allocate data 
space
- btrfs: qgroup: Always free PREALLOC META reserve in
  btrfs_delalloc_release_extents()
- iio: adc: meson_saradc: Fix memory allocation order
- iio: fix center temperature of bmc150-accel-core
- libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
- perf tests: Avoid raising SEGV using an obvious NULL dereference
- perf map: Fix overlapped map handling
- perf script brstackinsn: Fix recovery from LBR/binary mismatch
- perf jevents: Fix period for Intel fixed counters
- perf tools: Propagate get_cpuid() error
- perf annotate: Propagate perf_env__arch() error
- perf annotate: Fix the signedness of failure returns
- perf annotate: Propagate the symbol__annotate() error return
- perf annotate: Fix arch specific ->init() failure errors
- perf annotate: Return appropriate error code for allocation failures
- perf annotate: Don't return -1 for error when doing BPF disassembly
- staging: rtl8188eu: fix null dereference when kzalloc fails
- RDMA/siw: Fix serialization issue in write_space()
- RDMA/hfi1: Prevent memory leak in sdma_init
- RDMA/iw_cxgb4: fix SRQ access from dump_qp()
- RDMA/iwcm: Fix a lock inversion issue
- HID: hyperv: Use in-place iterator API in the channel callback
- kselftest: exclude failed TARGETS from runlist
- selftests/kselftest/runner.sh: Add 45 second timeout per test
- nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
- arm64: cpufeature: Effectively expose FRINT capability to userspace
- arm64: Fix incorrect irqflag restore for priority masking for compat
- arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 
#1542419
- tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()'
- tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()'
- serial/sifive: select SERIAL_EARLYCON
- tty: n_hdlc: fix build on SPARC
- misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach
- RDMA/core: Fix an error handling path in 'res_get_common_doit()'
- RDMA/cm: Fix memory leak in cm_add/remove_one
- RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path
- RDMA/mlx5: Do not allow rereg of a ODP MR
- RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu
- RDMA/mlx5: Add missing synchronize_srcu() for MW cases
- gpio: max77620: Use correct unit for debounce times
- fs: cifs: mute -Wunused-const-variable message
- arm64: vdso32: Fix broken compat vDSO build warnings
- arm64: vdso32: Detect binutils support for dmb ishld
- serial: mctrl_gpio: Check for NULL pointer
- serial: 8250_omap: Fix gpio check for auto RTS/CTS
- arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG
- arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally
- efi/cper: Fix endianness of PCIe class code
- efi/x86: Do not clean dummy variable in kexec path
- MIPS: include: Mark __cmpxchg as __always_inline
- riscv: avoid kernel hangs when trapped in BUG()
- riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
- riscv: Correct the handling of unexpected ebreak in do_trap_break()
- x86/xen: Return from panic notifier
- ocfs2: clear zero in unaligned direct IO
- fs: ocfs2: fix possible null-pointer dereferences in
  ocfs2_xa_prepare_entry()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_write_end_nolock()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_info_scan_inode_alloc()
- btrfs: silence maybe-uninitialized warning in clone_range
- arm64: armv8_deprecated: Checking return value for memory allocation
- sched/fair: Scale bandwidth quota and period without losing quota/period
  ratio precision
- sched/vtime: Fix guest/system mis-accounting on task switch
- perf/core: Rework memory accounting in perf_mmap()
- perf/core: Fix corner case in perf_rotate_context()
- perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp
- drm/amdgpu: fix memory leak
- iio: imu: adis16400: release allocated memory on failure
- iio: imu: adis16400: fix memory leak
- iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller
- MIPS: include: Mark __xchg as __always_inline
- MIPS: fw: sni: Fix out of bounds init of o32 stack
- s390/cio: fix virtio-ccw DMA without PV
- virt: vbox: fix memory 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-12-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.0.0-37.40

---
linux (5.0.0-37.40) disco; urgency=medium

  * disco/linux: 5.0.0-37.40 -proposed tracker (LP: #1852253)

  * System hangs at early boot (LP: #1851216)
- x86/timer: Skip PIT initialization on modern chipsets

  * drm/i915: Add support for another CMP-H PCH (LP: #1848491)
- drm/i915/cml: Add second PCH ID for CMP

  * Some EFI systems fail to boot in efi_init() when booted via maas
(LP: #1851810)
- efi: efi_get_memory_map -- increase map headroom

  * seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test (LP: #1849281)
- SAUCE: seccomp: avoid overflow in implicit constant conversion
- SAUCE: seccomp: rework define for SECCOMP_USER_NOTIF_FLAG_CONTINUE
- SAUCE: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] dkms -- try launchpad librarian for pool downloads
- [Packaging] dkms -- dkms-build quieten wget verbiage

  * update ENA driver to version 2.1.0 (LP: #1850175)
- net: ena: fix swapped parameters when calling
  ena_com_indirect_table_fill_entry
- net: ena: fix: Free napi resources when ena_up() fails
- net: ena: fix incorrect test of supported hash function
- net: ena: fix return value of ena_com_config_llq_info()
- net: ena: improve latency by disabling adaptive interrupt moderation by
  default
- net: ena: fix ena_com_fill_hash_function() implementation
- net: ena: add handling of llq max tx burst size
- net: ena: ethtool: add extra properties retrieval via get_priv_flags
- net: ena: replace free_tx/rx_ids union with single free_ids field in
  ena_ring
- net: ena: arrange ena_probe() function variables in reverse christmas tree
- net: ena: add newline at the end of pr_err prints
- net: ena: documentation: update ena.txt
- net: ena: allow automatic fallback to polling mode
- net: ena: add support for changing max_header_size in LLQ mode
- net: ena: optimise calculations for CQ doorbell
- net: ena: add good checksum counter
- net: ena: use dev_info_once instead of static variable
- net: ena: add MAX_QUEUES_EXT get feature admin command
- net: ena: enable negotiating larger Rx ring size
- net: ena: make ethtool show correct current and max queue sizes
- net: ena: allow queue allocation backoff when low on memory
- net: ena: add ethtool function for changing io queue sizes
- net: ena: remove inline keyword from functions in *.c
- net: ena: update driver version from 2.0.3 to 2.1.0
- net: ena: Fix bug where ring allocation backoff stopped too late
- Revert "net: ena: ethtool: add extra properties retrieval via
  get_priv_flags"
- net: ena: don't wake up tx queue when down
- net: ena: clean up indentation issue

  * Add Intel Comet Lake ethernet support (LP: #1848555)
- SAUCE: e1000e: Add support for Comet Lake

  * Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
GEO_TX_POWER_LIMIT (LP: #1846016)
- iwlwifi: exclude GEO SAR support for 3168

  * tsc marked unstable after entered PC10 on Intel CoffeeLake (LP: #1840239)
- SAUCE: x86/intel: Disable HPET on Intel Coffe Lake platforms
- SAUCE: x86/intel: Disable HPET on Intel Ice Lake platforms

  * cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled
cloud (LP: #1848481)
- [Packaging] include iavf/i40evf in generic

  * High power consumption using 5.0.0-25-generic (LP: #1840835)
- PCI: Add a helper to check Power Resource Requirements _PR3 existence
- ALSA: hda: Allow HDA to be runtime suspended when dGPU is not bound to a
  driver
- PCI: Fix missing inline for pci_pr3_present()

  * CML CPUIDs (LP: #1843794)
- x86/cpu: Add Comet Lake to the Intel CPU models header

  * shiftfs: prevent exceeding project quotas (LP: #1849483)
- SAUCE: shiftfs: drop CAP_SYS_RESOURCE from effective capabilities

  * shiftfs: fix fallocate() (LP: #1849482)
- SAUCE: shiftfs: setup correct s_maxbytes limit

  * Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
(LP: #1850443)
- Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message

  * [SRU][B/OEM-B/OEM-OSP1/D/E] UBUNTU: SAUCE: add rtl623 codec support and fix
mic issues (LP: #1850599)
- SAUCE: ALSA: hda/realtek - Add support for ALC623
- SAUCE: ALSA: hda/realtek - Fix 2 front mics of codec 0x623

  * NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between
client and server (LP: #1828978)
- NFSv4.1: Avoid false retries when RPC calls are interrupted

  * SUNRPC: Use after free when GSSD credentials are invalid causes oops
(LP: #1842037)
- SUNRPC: Clean up
- SUNRPC: Fix a use after free when a server rejects the RPCSEC_GSS 
credential

  * Suppress "hid_field_extract() called with n (192) > 32!" message floods
(LP: #1850600)
- 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-17 Thread You-Sheng Yang
Verified bionic-proposed/4.15.0-71.80, disco-proposed/5.0.0-37.40, eoan-
proposed/5.3.0-24.26.

** Tags removed: verification-needed-bionic verification-needed-disco 
verification-needed-eoan
** Tags added: verification-done-bionic verification-done-disco 
verification-done-eoan

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-14 Thread Ubuntu Kernel Bot
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-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag 'verification-needed-disco' to 'verification-failed-disco'.

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-disco

** 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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-14 Thread Ubuntu Kernel Bot
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!

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-14 Thread Ubuntu Kernel Bot
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-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

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-eoan

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-13 Thread Stefan Bader
** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Eoan)
   Importance: Undecided => Medium

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-12 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1063.72

---
linux-oem (4.15.0-1063.72) bionic; urgency=medium

  * CVE-2019-11135
- [Config] oem: Disable TSX by default when possible

  [ Ubuntu: 4.15.0-69.78 ]

  * KVM NULL pointer deref (LP: #1851205)
- KVM: nVMX: handle page fault in vmread fix
  * CVE-2018-12207
- KVM: MMU: drop vcpu param in gpte_access
- kvm: Convert kvm_lock to a mutex
- kvm: x86: Do not release the page inside mmu_set_spte()
- KVM: x86: make FNAME(fetch) and __direct_map more similar
- KVM: x86: remove now unneeded hugepage gfn adjustment
- KVM: x86: change kvm_mmu_page_get_gfn BUG_ON to WARN_ON
- KVM: x86: add tracepoints around __direct_map and FNAME(fetch)
- kvm: x86, powerpc: do not allow clearing largepages debugfs entry
- SAUCE: KVM: vmx, svm: always run with EFER.NXE=1 when shadow paging is
  active
- SAUCE: x86: Add ITLB_MULTIHIT bug infrastructure
- SAUCE: kvm: mmu: ITLB_MULTIHIT mitigation
- SAUCE: kvm: Add helper function for creating VM worker threads
- SAUCE: kvm: x86: mmu: Recovery of shattered NX large pages
- SAUCE: cpu/speculation: Uninline and export CPU mitigations helpers
- SAUCE: kvm: x86: mmu: Apply global mitigations knob to ITLB_MULTIHIT
  * CVE-2019-11135
- KVM: x86: use Intel speculation bugs and features as derived in generic 
x86
  code
- x86/msr: Add the IA32_TSX_CTRL MSR
- x86/cpu: Add a helper function x86_read_arch_cap_msr()
- x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default
- x86/speculation/taa: Add mitigation for TSX Async Abort
- x86/speculation/taa: Add sysfs reporting for TSX Async Abort
- kvm/x86: Export MDS_NO=0 to guests when TSX is enabled
- x86/tsx: Add "auto" option to the tsx= cmdline parameter
- x86/speculation/taa: Add documentation for TSX Async Abort
- x86/tsx: Add config options to set tsx=on|off|auto
- SAUCE: x86/speculation/taa: Call tsx_init()
- SAUCE: x86/cpu: Include cpu header from bugs.c
- [Config] Disable TSX by default when possible
  * CVE-2019-0154
- SAUCE: drm/i915: Lower RM timeout to avoid DSI hard hangs
- SAUCE: drm/i915/gen8+: Add RC6 CTX corruption WA
  * CVE-2019-0155
- drm/i915/gtt: Add read only pages to gen8_pte_encode
- drm/i915/gtt: Read-only pages for insert_entries on bdw+
- drm/i915/gtt: Disable read-only support under GVT
- drm/i915: Prevent writing into a read-only object via a GGTT mmap
- drm/i915/cmdparser: Check reg_table_count before derefencing.
- drm/i915/cmdparser: Do not check past the cmd length.
- drm/i915: Silence smatch for cmdparser
- drm/i915: Move engine->needs_cmd_parser to engine->flags
- SAUCE: drm/i915: Rename gen7 cmdparser tables
- SAUCE: drm/i915: Disable Secure Batches for gen6+
- SAUCE: drm/i915: Remove Master tables from cmdparser
- SAUCE: drm/i915: Add support for mandatory cmdparsing
- SAUCE: drm/i915: Support ro ppgtt mapped cmdparser shadow buffers
- SAUCE: drm/i915: Allow parsing of unsized batches
- SAUCE: drm/i915: Add gen9 BCS cmdparsing
- SAUCE: drm/i915/cmdparser: Use explicit goto for error paths
- SAUCE: drm/i915/cmdparser: Add support for backward jumps
- SAUCE: drm/i915/cmdparser: Ignore Length operands during command matching

linux-oem (4.15.0-1062.71) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1062.71 -proposed tracker (LP: #1851507)

  * Can't adjust brightness on DELL UHD dGPU AIO (LP: #1813877)
- SAUCE: platform/x86: dell-uart-backlight: add missing status command
- SAUCE: platform/x86: dell-uart-backlight: load driver by scalar status
- SAUCE: platform/x86: dell-uart-backlight: add force parameter
- SAUCE: platform/x86: dell-uart-backlight: add quirk for old platforms

  * System hangs at early boot (LP: #1851216)
- x86/timer: Skip PIT initialization on modern chipsets

linux-oem (4.15.0-1061.70) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1061.70 -proposed tracker (LP: #1850799)

  * [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support (LP: #1849598)
- Bluetooth: btrtl: Add support for RTL8822C with USB interface

  * [SRU][B/OEM-B/OEM-OSP1/D/E] UBUNTU: SAUCE: add rtl623 codec support and fix
mic issues (LP: #1850599)
- SAUCE: ALSA: hda/realtek - Add support for ALC623
- SAUCE: ALSA: hda/realtek - Fix 2 front mics of codec 0x623

  * Add Intel Comet Lake ethernet support (LP: #1848555)
- e1000e: Add support for Comet Lake

  * Suppress "hid_field_extract() called with n (192) > 32!" message floods
(LP: #1850600)
- HID: core: reformat and reduce hid_printk macros
- HID: core: Add printk_once variants to hid_warn() etc
- HID: core: fix dmesg flooding if report field larger than 32bit

  * tsc marked unstable after entered PC10 on Intel CoffeeLake (LP: #1840239)
- SAUCE: x86/intel: Disable HPET on Intel Coffe Lake platforms
- SAUCE: 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-11 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Disco)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: New => Fix Committed

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-07 Thread You-Sheng Yang
Fix for #3 is being SRU-ed in bug 1851216.

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  New
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-04 Thread You-Sheng Yang
Same device boots with disable-hpet patches applied to current korg-next
HEAD tagged next-20191031.

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  New
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-04 Thread You-Sheng Yang
Fix landed to linux-oem blocks one platform from booting up normally.
Reported in https://bugs.launchpad.net/ubuntu/+source/linux-
oem/+bug/1851216 .

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  New
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-11-02 Thread AceLan Kao
** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  New
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact] 
  TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.

  [Fix]
  Disable HPET on affected SoC generations, currently happens to CFL and
  ICL.
   
  [Test]
  I can confirm disabling HPET can avoid this issue.

  [Regression Potential]
  Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
  harmless to disable HPET on these platforms.

  === Original Bug Report ===
  This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

    [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
    [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

    [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
    [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
    [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
    [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
    [ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-10-30 Thread Kai-Heng Feng
** Description changed:

- This is actually a duplicate to
- https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal
- tracking.
+ === SRU Justification ===
+ [Impact] 
+ TSC marked unstable by skewed HPET after Intel SoC reached PC10 state.
+ 
+ [Fix]
+ Disable HPET on affected SoC generations, currently happens to CFL and
+ ICL.
+  
+ [Test]
+ I can confirm disabling HPET can avoid this issue.
+ 
+ [Regression Potential]
+ Low. TSC on recent Intel SoC is now an invariant clocksource, so it's
+ harmless to disable HPET on these platforms.
+ 
+ === Original Bug Report ===
+ This is actually a duplicate to 
https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal 
tracking.
  
  [Overview]
  
  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed in
  dmesg when this occurs:
  
-   [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
-   [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

-   [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
-   [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
-   [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
-   [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
-   [ 115.455825] clocksource: Switched to clocksource hpet
+   [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
+   [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

+   [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
+   [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
+   [ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
+   [ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
+   [ 115.455825] clocksource: Switched to clocksource hpet
  
  [Step to reproduce]
  
  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages
  
  [Actual Results]
  
  TSC marked unstable and clock source switched to HPET.
  
  [Expected Results]
  
  TSC remains the clock source across the PC10 event.
  
  [Build Date & Hardware]
  
  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.
  
  [Additional Information]
  
  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin suspend
  process.

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: linux-oem (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Won't 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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in 

[Kernel-packages] [Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-09-24 Thread You-Sheng Yang
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0f0b7e1cc7abf8e1a8b301f2868379d611d05ae2
introduced another parameter "tsc=nowatchdog", which should have the
same effect of the current work-around "tsc=reliable", but that's not
meant to be and will not be the ultimate solution for this issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is actually a duplicate to
  https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for
  internal tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

[ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

[ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
[ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
[ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
[ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
[ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-08-28 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: hwe-next
   Status: New => Triaged

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is actually a duplicate to
  https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for
  internal tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

[ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

[ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
[ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
[ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
[ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
[ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-08-15 Thread You-Sheng Yang
** Tags added: oem-priority originate-from-1813901 somerville

-- 
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/1840239

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is actually a duplicate to
  https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for
  internal tracking.

  [Overview]

  On Intel CoffeeLake it's observed tsc is always marked unstable after
  turning off screen and let cpu enter idle state Package C10(PC10), and
  then clock source is switched to hpet. Following messages are printed
  in dmesg when this occurs:

[ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: 

[ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd 
mask: 
[ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog
[ 115.454675] TSC found unstable after boot, most likely due to broken 
BIOS. Use 'tsc=unstable'.
[ 115.454679] sched_clock: Marking unstable (115712298090, 
-257671127)<-(115460381128, -5706726)
[ 115.455825] clocksource: Switched to clocksource hpet

  [Step to reproduce]

  1. use `powertop` to observe if CPU has ever enter PC10,
  2. issue `xset dpms force off` to turn off screen and idle for some minutes,
  3. check dmesg for above tsc marked unstable messages

  [Actual Results]

  TSC marked unstable and clock source switched to HPET.

  [Expected Results]

  TSC remains the clock source across the PC10 event.

  [Build Date & Hardware]

  This is reproducible on kernel version 4.14 through 5.1-rc2. Order
  kernel versions are not tested.

  [Additional Information]

  This was first found on Ubuntu (all versions) that system doesn't go
  suspend after stayed idle for 20 minutes. Clock source was switched to
  HPET, the system time is no correctly synced with reality so that the
  system doesn't consider it has stayed idle long enough to begin
  suspend process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+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