date:20180423

[Bug 1744543] Re: Screen updating with Compiz or Wayland causes high-CPU kworker thread in recent kernels

2018-04-23 Thread Misaki

** Tags added: vsync

** Description changed:

Originally filed under compiz:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1744515. Testing
indicates it affects Wayland as well.

The automatically-included information for this reports notes that I'm
using kernel 4.8, where this issue doesn't occur.

When the screen updates in recent versions of the Linux kernel,
including 4.13 and 4.15 while running Compiz or Wayland, it causes high
CPU usage in a kworker thread. This was 30~40% of a CPU core on my
system with 4.13 kernel, and is 65% with 4.15. This doesn't happen with
Metacity or non-Wayland Gnome. Since Unity uses Compiz, it happens there
as well.

This seems unrelated to how much of the screen is being repainted, as
the 'Show Repaint' plugin in Compiz can show that only a few pixels are
being updated and the kworker load is the same.

Updated test results, having upgraded to Bionic Beaver 18.04, with
kernel 4.15.0-15-generic,

-my Flashback compiz login no longer works, it just crashes back to the login
screen, so I can't test it.
-Unity uses compiz and still works for me, and still has this bug.
-Wayland has this bug and doesn't use compiz.

Other display managers remain the same. Metacity is the best in terms of
not causing the kernel to waste CPU; 'Ubuntu with Gnome' is the second-
best, only causing an extra 10~20% of CPU usage from gnome-shell, and no
high-CPU kworker threads.

When screen is updating under Wayland, one or two kworker threads use a
combined 65% of a CPU core, with gnome-shell using an additional 8% CPU.

This can be trivially triggered by running glxgears, the command 'ffmpeg
-filter_complex color=orange:2x2 -f opengl -', or the command 'ffplay
dummy -f lavfi -graph color=orange:2x2:60' which all should update a
small part of the screen at a tiny CPU cost. For me glxgears uses 1.5%,
while ffplay or ffmpeg use 7~12% to create a 2x2 pixel video, but all
three programs cause an extra 65% CPU use from the kernel.

My laptop's battery is completely dead so I have to keep it plugged in
all the time, but this should be a concern to anyone with a laptop as it
will affect battery life.

The 18.04 kernel is not one for which bugs can be filed at kernel.org:
https://www.kernel.org/doc/html/v4.10/admin-guide/reporting-bugs.html

I already confirmed the bug upstream, I assume from Debian; can someone
who can replicate this bug test the latest -rc kernel from kernel.org?

+ NEW DATA POINT! I followed the instructions here to stop screen tearing
+ in Metacity: http://dan.bodar.com/2018/02/26/stop-screen-tearing-on-
+ ubuntu-by-changing-compositor/
+
+ However, after testing for this bug with compton running, I found that
+ the bug does occur. Seeing 55% CPU from kworker. If I kill compton while
+ glxgears is running, the kworker thread immediately disappears from
+ 'top'.
+
+ I'm guessing the kernel is trying too hard to match screen vsync
+ (vertical sync).
+
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-generic 4.13.0.25.26
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: misaki 1685 F...m pulseaudio
/dev/snd/controlC0: misaki 1685 F pulseaudio
CurrentDesktop: GNOME-Flashback:GNOME
Date: Sun Jan 21 00:17:16 2018
HibernationDevice: RESUME=UUID=ea8d7b22-9a3e-412e-af6a-8fc260a76a2c
MachineType: ASUSTeK Computer Inc. N50Vn
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic
root=UUID=b09dc720-93ec-4fdf-a42f-7ea19a9af555 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.8.0-34-generic N/A
linux-backports-modules-4.8.0-34-generic N/A
linux-firmware1.169.1
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2018-01-09 (12 days ago)
WpaSupplicantLog:

dmi.bios.date: 03/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N50Vn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr211:bd03/05/2009:svnASUSTeKComputerInc.:pnN50Vn:pvr1.0:rvnASUSTeKComputerInc.:rnN50Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: N50Vn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744543

Title:
Screen updating with Compiz or Wayland causes high-CPU kworker thread
in recent kernels

To manage

[Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk

2018-04-23 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762353

Title:
  [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on  failed'
  when setting up a second end-to-end encrypted disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762353/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734130] Re: [18.04 FEAT] Add kvm_stat from kernel tree

2018-04-23 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734130

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1734130/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765083] Re: Please cherrypick s390 unwind fix

2018-04-23 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765083

Title:
  Please cherrypick s390 unwind fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1765083/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766478] [NEW] Deepin terminal is installed in base install unintentionally

2018-04-23 Thread Lyn Perrine

Public bug reported:

To reproduce on an alternate install of lubuntu 18.04 open the menu and
see that under system tools deepin terminal is at the the top.

lubuntu-desktop:
  Installed: 0.94
  Candidate: 0.94
  Version table:
 *** 0.94 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

Description:Ubuntu Bionic Beaver (development branch)
Release:18.04


I did not expect deepin terminal to be installed by default as it is not 
expected to be there.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lubuntu-desktop 0.94
ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
Uname: Linux 4.15.0-19-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon Apr 23 22:21:05 2018
InstallationDate: Installed on 2018-04-24 (0 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
SourcePackage: lubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766478

Title:
  Deepin terminal is installed in base install unintentionally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1766478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

2018-04-23 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762719

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1762719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766479] [NEW] Resizing a window's left border to the right can cause it to scoot right

2018-04-23 Thread Misaki

Public bug reported:

Tested with 18.04 beta.

Created a small window, ffmpeg or ffplay showing a 2x2 pixel video. When
trying to move it, instead selected left border. Dragging right caused
the window to scoot away faster than the pointer was moving, vanishing
in less than a second.

** Affects: wayland (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766479

Title:
  Resizing a window's left border to the right can cause it to scoot
  right

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1766479/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766024] Re: linux-aws: 4.15.0-1006.6 -proposed tracker

2018-04-23 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-aws - 4.15.0-1006.6

---
linux-aws (4.15.0-1006.6) bionic; urgency=medium

  * linux-aws: 4.15.0-1006.6 -proposed tracker (LP: #1766024)

  [ Ubuntu: 4.15.0-19.20 ]

  * linux: 4.15.0-19.20 -proposed tracker (LP: #1766021)
  * Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers (LP: #1765232)
- Revert "blk-mq: simplify queue mapping & schedule with each possisble CPU"
- Revert "genirq/affinity: assign vectors to all possible CPUs"

linux-aws (4.15.0-1005.5) bionic; urgency=medium

  * linux-aws: 4.15.0-1005.5 -proposed tracker (LP: #1765494)


  [ Ubuntu: 4.15.0-18.19 ]

  * linux: 4.15.0-18.19 -proposed tracker (LP: #1765490)
  * [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel:
meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
(LP: #1765429)
- powerpc/pseries: Fix clearing of security feature flags
  * signing: only install a signed kernel (LP: #1764794)
- [Packaging] update to Debian like control scripts
- [Packaging] switch to triggers for postinst.d postrm.d handling
- [Packaging] signing -- switch to raw-signing tarballs
- [Packaging] signing -- switch to linux-image as signed when available
- [Config] signing -- enable Opal signing for ppc64el
- [Packaging] printenv -- add signing options
  * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154)
- [Packaging] signing -- add support for signing Opal kernel binaries
  * Please cherrypick s390 unwind fix (LP: #1765083)
- s390/compat: fix setup_frame32
  * Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L]
[ipr] (LP: #1751813)
- d-i: move ipr to storage-core-modules on ppc64el
  * drivers/gpu/drm/bridge/adv7511/adv7511.ko missing (LP: #1764816)
- SAUCE: (no-up) rename the adv7511 drm driver to adv7511_drm
  * Miscellaneous Ubuntu changes
- [Packaging] Add linux-oem to rebuild test blacklist.

  [ Ubuntu: 4.15.0-17.18 ]

  * linux: 4.15.0-17.18 -proposed tracker (LP: #1764498)
  * Eventual OOM with profile reloads (LP: #1750594)
- SAUCE: apparmor: fix memory leak when duplicate profile load

linux-aws (4.15.0-1004.4) bionic; urgency=medium

  * linux-aws: 4.15.0-1004.4 -proposed tracker (LP: #1763788)


  [ Ubuntu: 4.15.0-16.17 ]

  * linux: 4.15.0-16.17 -proposed tracker (LP: #1763785)
  * [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed (LP: #1757346)
- [Config]: Set CONFIG_PINCTRL_CANNONLAKE=y
  * [Ubuntu 18.04] USB Type-C test failed on GLK (LP: #1758797)
- SAUCE: usb: typec: ucsi: Increase command completion timeout value
  * Fix trying to "push" an already active pool VP (LP: #1763386)
- SAUCE: powerpc/xive: Fix trying to "push" an already active pool VP
  * hisi_sas: Revert and replace SAUCE patches w/ upstream (LP: #1762824)
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to
  userspace"
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES"
- scsi: hisi_sas: modify some register config for hip08
- scsi: hisi_sas: add v3 hw MODULE_DEVICE_TABLE()
  * Realtek card reader - RTS5243 [VEN_10EC_5260] (LP: #1737673)
- misc: rtsx: Move Realtek Card Reader Driver to misc
- updateconfigs for Realtek Card Reader Driver
- misc: rtsx: Add support for RTS5260
- misc: rtsx: Fix symbol clashes
  * Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in
./include/linux/net_dim.h (LP: #1763269)
- net/mlx5e: Fix int overflow
  * apparmor bug fixes for bionic (LP: #1763427)
- apparmor: fix logging of the existence test for signals
- apparmor: make signal label match work when matching stacked labels
- apparmor: audit unknown signal numbers
- apparmor: fix memory leak on buffer on error exit path
- apparmor: fix mediation of prlimit
  * dangling symlinks to loaded apparmor policy (LP: #1755563) // apparmor bug
fixes for bionic (LP: #1763427)
- apparmor: fix dangling symlinks to policy rawdata after replacement
  * [OPAL] Assert fail:
core/mem_region.c:447:lock_held_by_me(>free_list_lock)
(LP: #1762913)
- powerpc/watchdog: remove arch_trigger_cpumask_backtrace
  * [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
(LP: #1762928)
- powerpc/tm: Fix endianness flip on trap
  * Add support for RT5660 codec based sound cards on Baytrail (LP: #1657674)
- SAUCE: (no-up) ASoC: Intel: Support machine driver for RT5660 on Baytrail
- SAUCE: (no-up) ASoC: rt5660: Add ACPI support
- SAUCE: (no-up): ASoC: Intel: bytcr-rt5660: Add MCLK, quirks
- [Config] CONFIG_SND_SOC_INTEL_BYTCR_RT5660_MACH=m, CONFIG_SND_SOC_RT5660=m
  * /dev/ipmi enumeration flaky on Cavium Sabre nodes (LP: #1762812)
- i2c: xlp9xx: return ENXIO on slave address NACK
- i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly
- i2c: xlp9xx: Check for Bus state before every transfer
- i2c: xlp9xx: Handle NACK on DATA properly
  * [18.04 FEAT]

[Bug 1765497] Re: linux-gcp: 4.15.0-1004.4 -proposed tracker

2018-04-23 Thread Launchpad Bug Tracker

*** This bug is a duplicate of bug 1766026 ***
https://bugs.launchpad.net/bugs/1766026

This bug was fixed in the package linux-gcp - 4.15.0-1005.5

---
linux-gcp (4.15.0-1005.5) bionic; urgency=medium

  * linux-gcp: 4.15.0-1005.5 -proposed tracker (LP: #1766026)

  [ Ubuntu: 4.15.0-19.20 ]

  * linux: 4.15.0-19.20 -proposed tracker (LP: #1766021)
  * Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers (LP: #1765232)
- Revert "blk-mq: simplify queue mapping & schedule with each possisble CPU"
- Revert "genirq/affinity: assign vectors to all possible CPUs"

linux-gcp (4.15.0-1004.4) bionic; urgency=medium

  * linux-gcp: 4.15.0-1004.4 -proposed tracker (LP: #1765497)

  [ Ubuntu: 4.15.0-18.19 ]

  * linux: 4.15.0-18.19 -proposed tracker (LP: #1765490)
  * [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel:
meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
(LP: #1765429)
- powerpc/pseries: Fix clearing of security feature flags
  * signing: only install a signed kernel (LP: #1764794)
- [Packaging] update to Debian like control scripts
- [Packaging] switch to triggers for postinst.d postrm.d handling
- [Packaging] signing -- switch to raw-signing tarballs
- [Packaging] signing -- switch to linux-image as signed when available
- [Config] signing -- enable Opal signing for ppc64el
- [Packaging] printenv -- add signing options
  * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154)
- [Packaging] signing -- add support for signing Opal kernel binaries
  * Please cherrypick s390 unwind fix (LP: #1765083)
- s390/compat: fix setup_frame32
  * Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L]
[ipr] (LP: #1751813)
- d-i: move ipr to storage-core-modules on ppc64el
  * drivers/gpu/drm/bridge/adv7511/adv7511.ko missing (LP: #1764816)
- SAUCE: (no-up) rename the adv7511 drm driver to adv7511_drm
  * Miscellaneous Ubuntu changes
- [Packaging] Add linux-oem to rebuild test blacklist.

  [ Ubuntu: 4.15.0-17.18 ]

  * linux: 4.15.0-17.18 -proposed tracker (LP: #1764498)
  * Eventual OOM with profile reloads (LP: #1750594)
- SAUCE: apparmor: fix memory leak when duplicate profile load

  [ Ubuntu: 4.15.0-16.17 ]

  * linux: 4.15.0-16.17 -proposed tracker (LP: #1763785)
  * [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed (LP: #1757346)
- [Config]: Set CONFIG_PINCTRL_CANNONLAKE=y
  * [Ubuntu 18.04] USB Type-C test failed on GLK (LP: #1758797)
- SAUCE: usb: typec: ucsi: Increase command completion timeout value
  * Fix trying to "push" an already active pool VP (LP: #1763386)
- SAUCE: powerpc/xive: Fix trying to "push" an already active pool VP
  * hisi_sas: Revert and replace SAUCE patches w/ upstream (LP: #1762824)
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to
  userspace"
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES"
- scsi: hisi_sas: modify some register config for hip08
- scsi: hisi_sas: add v3 hw MODULE_DEVICE_TABLE()
  * Realtek card reader - RTS5243 [VEN_10EC_5260] (LP: #1737673)
- misc: rtsx: Move Realtek Card Reader Driver to misc
- updateconfigs for Realtek Card Reader Driver
- misc: rtsx: Add support for RTS5260
- misc: rtsx: Fix symbol clashes
  * Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in
./include/linux/net_dim.h (LP: #1763269)
- net/mlx5e: Fix int overflow
  * apparmor bug fixes for bionic (LP: #1763427)
- apparmor: fix logging of the existence test for signals
- apparmor: make signal label match work when matching stacked labels
- apparmor: audit unknown signal numbers
- apparmor: fix memory leak on buffer on error exit path
- apparmor: fix mediation of prlimit
  * dangling symlinks to loaded apparmor policy (LP: #1755563) // apparmor bug
fixes for bionic (LP: #1763427)
- apparmor: fix dangling symlinks to policy rawdata after replacement
  * [OPAL] Assert fail:
core/mem_region.c:447:lock_held_by_me(>free_list_lock)
(LP: #1762913)
- powerpc/watchdog: remove arch_trigger_cpumask_backtrace
  * [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
(LP: #1762928)
- powerpc/tm: Fix endianness flip on trap
  * Add support for RT5660 codec based sound cards on Baytrail (LP: #1657674)
- SAUCE: (no-up) ASoC: Intel: Support machine driver for RT5660 on Baytrail
- SAUCE: (no-up) ASoC: rt5660: Add ACPI support
- SAUCE: (no-up): ASoC: Intel: bytcr-rt5660: Add MCLK, quirks
- [Config] CONFIG_SND_SOC_INTEL_BYTCR_RT5660_MACH=m, CONFIG_SND_SOC_RT5660=m
  * /dev/ipmi enumeration flaky on Cavium Sabre nodes (LP: #1762812)
- i2c: xlp9xx: return ENXIO on slave address NACK
- i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly
- i2c: xlp9xx: Check for Bus state before every transfer
- i2c: xlp9xx: Handle NACK on DATA properly
  * [18.04 FEAT] Add kvm_stat from

[Bug 1766026] Re: linux-gcp: 4.15.0-1005.5 -proposed tracker

2018-04-23 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-gcp - 4.15.0-1005.5

---
linux-gcp (4.15.0-1005.5) bionic; urgency=medium

  * linux-gcp: 4.15.0-1005.5 -proposed tracker (LP: #1766026)

  [ Ubuntu: 4.15.0-19.20 ]

  * linux: 4.15.0-19.20 -proposed tracker (LP: #1766021)
  * Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers (LP: #1765232)
- Revert "blk-mq: simplify queue mapping & schedule with each possisble CPU"
- Revert "genirq/affinity: assign vectors to all possible CPUs"

linux-gcp (4.15.0-1004.4) bionic; urgency=medium

  * linux-gcp: 4.15.0-1004.4 -proposed tracker (LP: #1765497)

  [ Ubuntu: 4.15.0-18.19 ]

  * linux: 4.15.0-18.19 -proposed tracker (LP: #1765490)
  * [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel:
meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
(LP: #1765429)
- powerpc/pseries: Fix clearing of security feature flags
  * signing: only install a signed kernel (LP: #1764794)
- [Packaging] update to Debian like control scripts
- [Packaging] switch to triggers for postinst.d postrm.d handling
- [Packaging] signing -- switch to raw-signing tarballs
- [Packaging] signing -- switch to linux-image as signed when available
- [Config] signing -- enable Opal signing for ppc64el
- [Packaging] printenv -- add signing options
  * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154)
- [Packaging] signing -- add support for signing Opal kernel binaries
  * Please cherrypick s390 unwind fix (LP: #1765083)
- s390/compat: fix setup_frame32
  * Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L]
[ipr] (LP: #1751813)
- d-i: move ipr to storage-core-modules on ppc64el
  * drivers/gpu/drm/bridge/adv7511/adv7511.ko missing (LP: #1764816)
- SAUCE: (no-up) rename the adv7511 drm driver to adv7511_drm
  * Miscellaneous Ubuntu changes
- [Packaging] Add linux-oem to rebuild test blacklist.

  [ Ubuntu: 4.15.0-17.18 ]

  * linux: 4.15.0-17.18 -proposed tracker (LP: #1764498)
  * Eventual OOM with profile reloads (LP: #1750594)
- SAUCE: apparmor: fix memory leak when duplicate profile load

  [ Ubuntu: 4.15.0-16.17 ]

  * linux: 4.15.0-16.17 -proposed tracker (LP: #1763785)
  * [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed (LP: #1757346)
- [Config]: Set CONFIG_PINCTRL_CANNONLAKE=y
  * [Ubuntu 18.04] USB Type-C test failed on GLK (LP: #1758797)
- SAUCE: usb: typec: ucsi: Increase command completion timeout value
  * Fix trying to "push" an already active pool VP (LP: #1763386)
- SAUCE: powerpc/xive: Fix trying to "push" an already active pool VP
  * hisi_sas: Revert and replace SAUCE patches w/ upstream (LP: #1762824)
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to
  userspace"
- Revert "UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES"
- scsi: hisi_sas: modify some register config for hip08
- scsi: hisi_sas: add v3 hw MODULE_DEVICE_TABLE()
  * Realtek card reader - RTS5243 [VEN_10EC_5260] (LP: #1737673)
- misc: rtsx: Move Realtek Card Reader Driver to misc
- updateconfigs for Realtek Card Reader Driver
- misc: rtsx: Add support for RTS5260
- misc: rtsx: Fix symbol clashes
  * Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in
./include/linux/net_dim.h (LP: #1763269)
- net/mlx5e: Fix int overflow
  * apparmor bug fixes for bionic (LP: #1763427)
- apparmor: fix logging of the existence test for signals
- apparmor: make signal label match work when matching stacked labels
- apparmor: audit unknown signal numbers
- apparmor: fix memory leak on buffer on error exit path
- apparmor: fix mediation of prlimit
  * dangling symlinks to loaded apparmor policy (LP: #1755563) // apparmor bug
fixes for bionic (LP: #1763427)
- apparmor: fix dangling symlinks to policy rawdata after replacement
  * [OPAL] Assert fail:
core/mem_region.c:447:lock_held_by_me(>free_list_lock)
(LP: #1762913)
- powerpc/watchdog: remove arch_trigger_cpumask_backtrace
  * [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
(LP: #1762928)
- powerpc/tm: Fix endianness flip on trap
  * Add support for RT5660 codec based sound cards on Baytrail (LP: #1657674)
- SAUCE: (no-up) ASoC: Intel: Support machine driver for RT5660 on Baytrail
- SAUCE: (no-up) ASoC: rt5660: Add ACPI support
- SAUCE: (no-up): ASoC: Intel: bytcr-rt5660: Add MCLK, quirks
- [Config] CONFIG_SND_SOC_INTEL_BYTCR_RT5660_MACH=m, CONFIG_SND_SOC_RT5660=m
  * /dev/ipmi enumeration flaky on Cavium Sabre nodes (LP: #1762812)
- i2c: xlp9xx: return ENXIO on slave address NACK
- i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly
- i2c: xlp9xx: Check for Bus state before every transfer
- i2c: xlp9xx: Handle NACK on DATA properly
  * [18.04 FEAT] Add kvm_stat from kernel tree (LP: #1734130)
- tools/kvm_stat: simplify the sortkey function
-

[Bug 1766477] [NEW] Chang one of two front mics on a lenovo thinkcentre machine

2018-04-23 Thread Hui Wang

Public bug reported:

Image: sutton-hamming-xenial-amd64-20180323-51.iso
BIOS Version: M1VKT04A
Platform: P330-1/P330-2
CPU: Intel(R) Xeon(R) E-2124G CPU @ 3.40GHz

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1760764 sutton

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

** Tags added: originate-from-1760764 sutton

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766477

Title:
  Chang one of two front mics on a lenovo thinkcentre machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766477/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

2018-04-23 Thread Daniel van Vugt

** Description changed:

  [Impact]
  
  * Xwayland is failing frequently (not crashing), which triggers a crash
- in gnome-shell because gnome-shell doesn't know how to survive without
- Xwayland.
+ in gnome-shell because gnome-shell doesn't know how to survive after
+ Xwayland has reset itself.
  
  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.
  
  * This affects Xorg sessions too, because the gdm login screen itself is
  a Wayland session. And Xorg users will see the problem dialog after they
  have logged into a Xorg session.
  
  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and annoying
  error dialogs at least. It does not fix the root causes that remain in
  Xwayland, but this is considered acceptable because there really isn't a
  bug in gnome-shell here other than it doesn't know how to survive
  without a connection to Xwayland.
  
  * For users of Xorg sessions, like bionic default, this is a full fix as
  Xorg users will never get an Xwayland instance after logging in. And
  hence no Xwayland bugs.
  
  [Test Case]
  
  * Just install bionic, use it lightly and reboot a few times.
  
  * Observe crash files are left in /var/crash and problem report dialogs
  after logging in.
  
  [Regression Potential]
  
  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit. For
  Xorg users this should be invisible as the affected login screen
  restarts automatically.
  
  [Other Info]
  
  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.
  
  -
  
  *** This is a duplicate of bug 1505409, but is being kept separate so as
  to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***
  
  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
  
  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

** Description changed:

  [Impact]
  
  * Xwayland is failing frequently (not crashing), which triggers a crash
  in gnome-shell because gnome-shell doesn't know how to survive after
  Xwayland has reset itself.
  
  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.
  
  * This affects Xorg sessions too, because the gdm login screen itself is
  a Wayland session. And Xorg users will see the problem dialog after they
  have logged into a Xorg session.
  
  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and annoying
  error dialogs at least. It does not fix the root causes that remain in
  Xwayland, but this is considered acceptable because there really isn't a
  bug in gnome-shell here other than it doesn't know how to survive
  without a connection to Xwayland.
  
  * For users of Xorg sessions, like bionic default, this is a full fix as
  Xorg users will never get an Xwayland instance after logging in. And
- hence no Xwayland bugs.
+ hence the Xwayland bugs are irrelevant.
  
  [Test Case]
  
  * Just install bionic, use it lightly and reboot a few times.
  
  * Observe crash files are left in /var/crash and problem report dialogs
  after logging in.
  
  [Regression Potential]
  
  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a

[Bug 1766398] Re: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

2018-04-23 Thread Hui Wang

** Description changed:

+ [Impact]
+ On this Dell machine (codename: turtle bay), the microphone always shows up
+ in the sound-setting even there is no microphone plugged in.
  
- Additional information:
- SKU: TURTLEBAY-DVT2-C1/TURTLEBAY-DVT2-C2/TURTLEBAY-DVT2-C3
- BIOS: 0.3.0
- Manifest: dell-bto-xenial-turtle-bay-X29-20180323-18.iso
+ [Fix]
  
- Image: somerville-xenial-amd64-
+ Without this fix, the pin will be regarded as microphone, and the jack name
+ is "Mic Phantom", it is always on in the pulseaudio even nothing is plugged
+ into the jack. So the UI is confusing to users since the microphone always
+ shows up in the UI even there is no microphone plugged.
+ 
+ After adding this flag, the jack name is "Headset Mic Phantom", then
+ the pulseaudio can handle its detection correctly.
+ 
+ 
+ [Test Case]
+ After booting up the system, and without plugging anything in the audio combo
+ jack, there is nothing in the input tab of sound-setting, then plug a headset
+ in the jack, the what-did-you-plug-in dialogue pops up, users can select 
headset
+ mic from UI, and headset-mic shows up in the sound-setting, we can record 
sound
+ via headset-mic
+ 
+ 
+ [Regression Potential]
+ Very low, since this patch is specific for ALC255_FIXUP_DELL_HEADSET_MIC 
which is
+ only used by Dell precision 3630 by now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766398

Title:
  set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766398/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1002 matches

Mail list logo