from:"Øystein Alværvik"

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

2018-08-15 Thread Øystein Alværvik

I can confirm that the fix in the Cosmic kernel is sufficient. Will this
be backported to Bionic and Xenial HWE?

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  Systems with acpi-lpss can't do S3/S4 on Bionic.

  [Test]
  Users confirmed these patches work for them.

  [Fix]
  Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system
  sleep handling) applies quirks for both runtime and system suspend.
  This causes problems for some systems, so avoid using quirks on S3 and
  S4.

  [Regression Potential]
  Low. These patches are in upstream stable, and it brings back driver's
  old behavior.

  ===Original Bug Report===
  I have installed Kubuntu 18.04 on 3 different machines (my friend's and my 
own) with no suspend problems but my HP Pavilion 11 x360 does not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  Correct behaviour is -

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  What happens -

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  Checking the logs suggests that the machine believes it is in suspend
  mode sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

2018-07-30 Thread Øystein Alværvik

Confirmed that Rafael's patched kernel fixes the issue on an Asus
Zenbook UX303LA which exhibited the same problem that the OP described
(issue occured with at least 4.15 and 4.17) on Ubuntu 16.04. I tested
the suspend function with the patched kernel over two days.

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Kubuntu 18.04 on 3 different machines (my friend's
  and my own) with no suspend problems but my HP Pavilion 11 x360 does
  not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  
  Correct behaviour is - 

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  
  What happens - 

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  
  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  
  Checking the logs suggests that the machine believes it is in suspend mode 
sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na 
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

2018-05-01 Thread Øystein Alværvik

Oh, of course, you are right, Mr. Van Vugt.

I tested the linux-hwe kernel 4.13.0-40.45~16.04.1 from xenial-proposed,
and that kernel fixes the regression. This was, of course, tested under
Xenial.

Thank you again for your efforts! :-)

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

** Changed in: linux-hwe (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  [regression] Colour banding and artefacts appear system-wide on an
  Asus Zenbook UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Color dithering not working correctly because the graphics driver
  assumes the panel support 8bpc, but the panel only supports 6bpc.

  [Test]
  User reports the issue start appearing from v4.8-rc2.
  The issue is fixed with the patch.

  [Fix]
  Add a quirk to tell DRM that this panel only supports 6bpc.

  [Regression Potential]
  Low. This fix matches a very specific panel.

  === Original Bug Report ===
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp.
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

2018-04-27 Thread Øystein Alværvik

This regression does not affect Xenial, so the fix is redundant.

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

Title:
[regression] Colour banding and artefacts appear system-wide on an
Asus Zenbook UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released

Bug description:
=== SRU Justification ===
[Impact]
Color dithering not working correctly because the graphics driver
assumes the panel support 8bpc, but the panel only supports 6bpc.

[Test]
User reports the issue start appearing from v4.8-rc2.
The issue is fixed with the patch.

[Fix]
Add a quirk to tell DRM that this panel only supports 6bpc.

[Regression Potential]
Low. This fix matches a very specific panel.

=== Original Bug Report ===
- Ubuntu 18.04 (with updates as of 14 Feb 2018).
- Laptop: Asus Zenbook UX303
- CPU: Intel i5 4210U
- Graphics: Intel HD 4400

Problem description: Colour artefacts and banding in all apps.
Graphics, photos and videos display as though the colour range is
improperly configured.

See this photo of a 1080p video taken with a camera (poor quality, but
illustrates the issue): https://ubuntucommunity.s3-us-

east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

Look at the sky’s light colours. They display with smooth gradients on
Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
video with a smaller range of white colours. This is the most apparent
with either very dark or very light colours. Even on window titlebars
the banding is visible (displayed as lines with different shades of
grey/black).

Compared with a PrtSc shot of the same image:
https://i.imgur.com/VkOSCaQ.png

The artefacts are not present on PrtSc shots that are taken on Ubuntu
18.04 but viewed on a different system (16.04 and Windows).

Installing a previous kernel version fixes the issue completely. I
used UKUU Update Utility to install kernel 4.4 (the same that I use in
Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
18.04 everything displayed smoothly. So this indicates that the system
might be using a sub-optimal colour depth with the newer kernel?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified:
boot/vmlinuz-4.13.0-32-generic]
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ystein 1344 F pulseaudio
/dev/snd/controlC1: ystein 1344 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 11:25:43 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
InstallationDate: Installed on 2018-02-12 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:07dc Intel Corp.
Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-generic N/A
linux-backports-modules-4.13.0-32-generic N/A
linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX303LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net

[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

2018-03-23 Thread Øystein Alværvik

In *Bionic*, the kernel in proposed (4.15.0-13.14) and in release
(4.15.0-12.13) both fix this regression.

I won't test the fix on Artful; I don't have the system installed and I
don't want to spend the time since Artful won't be supported for very
long anyway (and this bug affects only very few users).

** Tags added: verification-done-bionic

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

Title:
[regression] Colour banding and artefacts appear system-wide on an
Asus Zenbook UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Released