[Kernel-packages] [Bug 2077265] Re: Screen freezes with kernel 6.8 (also "i915 driver attached, reenabling gpu turbo"), while kernel 6.5 still works

2024-09-06 Thread Ash
Update: I've updated to linux-generic-hwe-22.04 6.8.0-44 from "proposed"
and it has been running fine for about an hour now. I never got this
long with the 6.8.0-40 release.

It would always freeze between 5 and 10 minutes after booting, rarely it
would last up to 20 minutes.

I upgraded only linux-generic-hwe-22.04 (and its dependencies -image
-modules -headers -tools) to 6.8.0-44, I didn't update to the new linux-
firmware from "proposed". I rebooted to the new kernel and now its been
up for an hour. I've stress tested it with opening many python machine
learning projects simultaneously, watching many 4k videos with hardware
decoding and hardware video rendering simultaneously, and running 3D
rendering benchmarks back to back.

Its hard to say exactly what fixed it, there are hundreds of backported
fixes in 6.8.0-44. Personally I think it was something I/O related. In
the 6.8.0-40 kernel I would start seeing incoming and outgoing network
packets slowing down to a crawl, and files refusing to open in the
seconds just before the freeze.

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

Title:
  Screen freezes with kernel 6.8 (also "i915 driver attached, reenabling
  gpu turbo"), while kernel 6.5 still works

Status in linux-hwe-6.8 package in Ubuntu:
  Incomplete

Bug description:
  After a kernel update (on 2024-08-14, if I remember correctly), the Gnome 
desktop freezes, always.
  This happens sometimes already on the login screen (mouse pointer frozen, no 
keyboard input accepted).
  Sometimes it happens a few seconds or a few minutes after login.
  No further input possible.
  No change to a text console possible.
  When I disconnect the USB-mouse and reconnect it, the mouse LED remains dark.
  Seems that USB is frozen too.

  This happens with kernel: vmlinuz-6.8.0-40-generic

  When I boot the previous kernel: vmlinuz-6.5.0-45-generic, no freezes
  occur and all works well.

  I managed to switch to a text console before the freeze happened.
  The attached files were created in a text console as root and then 
transferred to a different computer in order to report the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2077265/+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 2077265] Re: Screen freezes with kernel 6.8 (also "i915 driver attached, reenabling gpu turbo"), while kernel 6.5 still works

2024-09-06 Thread Ash
Hi, I'm having this exact same issue.
It started when linux-generic-hwe-22.04 updated from "6.5.0-45-generic" to 
"6.8.0-40-generic" in mid-August.

I am using a Dell Precision 5470 Laptop, it is an Intel Core i9 with
integrated Iris Xe graphics. It has a discrete nVidia RTX A1000 GPU but
I usually have it disabled.

When booting with the 6.8.0 kernel, I will get this same freeze as OP
described usually within 5 to 10 minutes after booting. When it freezes,
both of my external displays are frozen, my USB mouse is frozen, USB
keyboard is unresponsive, laptop trackpad and laptop keyboard are
frozen. Plugging in a new USB device, (eg, another mouse) it does not
light up. Changing to a different background VT does not work.
CTRL+ALT+DELETE and other key combos do not work. Power button on the
laptop does nothing. Holding down the power button for 8 seconds to
force a power-off is the only way forward. I've monitored thermals and
the CPU and SSD are not getting hot before the freeze, or while frozen.

Checking the system journal after rebooting shows no errors or kernel
panics before the freeze or at the time of the freeze. I haven't tried
to SSH into the laptop while it is frozen, I doubt it would work because
I because I think the kernel is deadlocked.

I just noticed this afternoon there is a 6.8.0-44 in proposed, the changelog 
shows a whole tonne of kernel fixes backported from Noble so there's a good 
chance its fixed by one of those. I will try it tonight.
https://launchpad.net/ubuntu/+source/linux-hwe-6.8/6.8.0-44.44~22.04.1

Similarly, I saw on another bug report there is a new linux-firmware package in 
proposed that will fix some hardware errors associated with kernel 6.8.0 so I 
will try that too.
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.8/+bug/2078912

If one or both of those fix the problem, I will report back the
solution, otherwise, I will try some of the debugging options posted
above.

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

Title:
  Screen freezes with kernel 6.8 (also "i915 driver attached, reenabling
  gpu turbo"), while kernel 6.5 still works

Status in linux-hwe-6.8 package in Ubuntu:
  Incomplete

Bug description:
  After a kernel update (on 2024-08-14, if I remember correctly), the Gnome 
desktop freezes, always.
  This happens sometimes already on the login screen (mouse pointer frozen, no 
keyboard input accepted).
  Sometimes it happens a few seconds or a few minutes after login.
  No further input possible.
  No change to a text console possible.
  When I disconnect the USB-mouse and reconnect it, the mouse LED remains dark.
  Seems that USB is frozen too.

  This happens with kernel: vmlinuz-6.8.0-40-generic

  When I boot the previous kernel: vmlinuz-6.5.0-45-generic, no freezes
  occur and all works well.

  I managed to switch to a text console before the freeze happened.
  The attached files were created in a text console as root and then 
transferred to a different computer in order to report the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2077265/+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 1959113] Re: missing built-in disk encryption at install time

2023-10-02 Thread Roy Ash
** Also affects: linux-firmware-raspi (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: rpi-imager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  missing built-in disk encryption at install time

Status in Ubuntu:
  New
Status in linux-firmware-raspi package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in rpi-imager package in Ubuntu:
  New

Bug description:
  Is there a simple way to install Ubuntu on SD card for Raspberry Pi4
  with full disk encryption?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1959113/+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 1927037] [NEW] ath9k driver: miniPCIe Atheros AR93xx not recognized

2021-05-03 Thread Ash Wilson
Public bug reported:

Expected behavior:
Network adapter should be visible via `iw list`, `iwconfig`, and `ifconfig`.

Actual behavior:
Network adapter is visible in `lspci` and `lshw`, but not in `iw list`, 
`iwconfig`, or `ifconfig`

Details:
The Atheros network card is detected by the ath9k driver when installed into a 
machine with x86_64 architecture. When the same card is installed into a 
miniPCIe-to-PCIe adapter, then plugged into a Raspberry Pi CM4 IO breakout 
board, the network adapter can be seen via lspci and lshw but is not seen by 
iw, iwconfig, or ifconfig.

lspci:
ubuntu@ubuntu:~$ sudo lspci -v
00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 20) 
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 41
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: -0fff [size=4K]
Memory behind bridge: f800-f80f [size=1M]
Prefetchable memory behind bridge: [disabled]
Capabilities: [48] Power Management version 3
Capabilities: [ac] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [180] Vendor Specific Information: ID= Rev=0 Len=028 

Capabilities: [240] L1 PM Substates
Kernel driver in use: pcieport

01:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter 
(rev 01)
Subsystem: Qualcomm Atheros AR93xx Wireless Network Adapter
Flags: fast devsel, IRQ 255
Memory at 6 (64-bit, non-prefetchable) [disabled] [size=128K]
Expansion ROM at 60002 [virtual] [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00

-
lshw:
ubuntu@ubuntu:~$ sudo lshw -c net
  *-network UNCLAIMED   
   description: Network controller
   product: AR93xx Wireless Network Adapter
   vendor: Qualcomm Atheros
   physical id: 0
   bus info: pci@:01:00.0
   version: 01
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress cap_list
   configuration: latency=0
   resources: memory:6-60001 memory:60002-60002
  *-network
   description: Ethernet interface
   physical id: 1
   logical name: eth0
   serial: dc:a6:32:f4:69:36
   size: 1Gbit/s
   capacity: 1Gbit/s
   capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 
1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=bcmgenet 
driverversion=v2.0 duplex=full ip=REDACTED link=yes multicast=yes port=MII 
speed=1Gbit/s

-
iw list/iwconfig:
ubuntu@ubuntu:~$ iw list
ubuntu@ubuntu:~$ iwconfig
lono wireless extensions.

eth0  no wireless extensions.

-
ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-1034-raspi 5.4.0-1034.37
ProcVersionSignature: User Name 5.4.0-1034.37-raspi 5.4.101
Uname: Linux 5.4.0-1034-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: arm64
CasperMD5CheckResult: skip
Date: Tue May  4 02:59:25 2021
ImageMediaBuild: 20210201.1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 focal uec-images

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

Title:
  ath9k driver: miniPCIe Atheros AR93xx not recognized

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Expected behavior:
  Network adapter should be visible via `iw list`, `iwconfig`, and `ifconfig`.

  Actual behavior:
  Network adapter is visible in `lspci` and `lshw`, but not in `iw list`, 
`iwconfig`, or `ifconfig`

  Details:
  The Atheros network card is detected by the ath9k driver when installed into 
a machine with x86_64 architecture. When the same card is installed into a 
miniPCIe-to-PCIe adapter, then plugged into a Raspberry Pi CM4 IO breakout 
board, the network adapter can be seen via lspci and lshw but is not seen by 
iw, iwconfig, or ifconfig.

  lspci:
  ubuntu@ubuntu:~$ sudo lspci -v
  00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 20) 
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 41
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O 

[Kernel-packages] [Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

2020-09-18 Thread ash
That update hasn't fixed the bass on my ubuntu 20.04 install

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

Title:
  Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14

  Audio works and the volume seems reasonable however the audio is
  noticeably missing bass giving everything a high treble sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-ucm-conf 1.2.2-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:17:33 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-ucm-conf
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: linux
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

2020-09-03 Thread ash
That's great. Thank you for the update Hui Wang

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

Title:
  Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14

  Audio works and the volume seems reasonable however the audio is
  noticeably missing bass giving everything a high treble sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-ucm-conf 1.2.2-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:17:33 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-ucm-conf
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: linux
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

2020-07-05 Thread ash
At some point recently (there were some recent alsa updates which I
suspect were the culprit) this problem now also popped up on my fedora
32 installation.

Per Alejandro's suggestion this also fixed it on fedora 32

hda-verb /dev/snd/hwC0D0 0x17 SET_CONNECT_SEL 1

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

Title:
  Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14

  Audio works and the volume seems reasonable however the audio is
  noticeably missing bass giving everything a high treble sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-ucm-conf 1.2.2-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:17:33 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-ucm-conf
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: linux
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

2020-06-11 Thread ash
I switched to fedora 32 and can confirm no problem with the audio.

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

Title:
  Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal

Status in alsa-ucm-conf package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14

  Audio works and the volume seems reasonable however the audio is
  noticeably missing bass giving everything a high treble sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-ucm-conf 1.2.2-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 09:17:33 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-ucm-conf
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: linux
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen

2020-04-13 Thread ash
Hi Hui and Martin, I created a bug to track the bass speaker issue here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872108

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

Title:
  volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1
  Carbon 7th gen

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  There are 2 physical speakers on the X1 7th, and one is Bass speaker
  and connect to a DAC which doesn't have volume control on it.

  [Fix]
  adjust that speaker to connect to a DAC which has volume control
  capability.

  
  [Test Case]
  adjust the output volume from UI and play sound from speaker.

  
  [Regression Risk]
  Low, these change is specific to 2 lenovo machines.


  On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in
  speakers, the volume is either off or on, there's no gradation in
  volume when I move the slider up or down.

  If I enable Over-Amplification than there's gradation in volume when I
  turn the volume up past 100%, but not for 0-100%.

  This problem does not occur with a headset plugged into the 3.5mm
  jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:07:44 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+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 1554613]

2016-04-20 Thread ash
looks like a power management issues dating 8 months back, Also happened on the 
broadwell systems https://bugs.freedesktop.org/show_bug.cgi?id=91393.
This makes any linux system a pain to work because of this integrated gpu 
driver . Skylake has been out for 7 months and we still have problems

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

Title:
  screen flickering on XPS13 9350

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  see LP: #1552304

  does not affect 4.4.0-8
  affects 4.4.0-9 to 4.4.0-16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.11.12
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbonfort   1498 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Mar  8 09:57:12 2016
  HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e
  InstallationDate: Installed on 2016-01-07 (61 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-8-generic N/A
   linux-backports-modules-4.4.0-8-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1554613/+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 1560395] Re: [i915_bpo] Update i915 backport driver

2016-04-06 Thread ash
Can the latest changes from 4.6-rc2 be brought forward still to many
issues

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

Title:
  [i915_bpo] Update i915 backport driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Current snapshot of i915_bpo is based on drm-intel-next-2016-02-14
  tag, and it makes sense to update it to the latest tag leading to 4.6,
  which is drm-intel-next-fixes-2016-03-16:

  94669e6ba1ada13 drm/i915: Handle -ED EADLK in drm_atomic_commit from 
load-detect.
  0bbca274a31c236 drm/i915: Actually retry with bit-banging after GMBUS timeout
  2f791908a70e957 drm/i915: Fix bogus dig_port_map[] assignment for pre-HSW
  eda908967feecf7 drm/i915: Balance assert_rpm_wakelock_held() for 
!IS_ENABLED(CONFIG_PM)
  bd90123c4973821 drm/i915/skl: Fix power domain suspend sequence
  5790ff742b1feee drm/i915: Update DRIVER_DATE to 20160229
  2743179d955bd73 drm/i915: Execlists cannot pin a context without the object
  596c5923197b889 drm/i915: Reduce the pointer dance of i915_is_ggtt()
  1c7f4bca5a6f53c drm/i915: Rename vma->*_list to *_link for consistency
  135dc79efbc119e drm/i915: Balance assert_rpm_wakelock_held() for 
!IS_ENABLED(CONFIG_PM)
  99cf8ea16595ecf drm/i915/lrc: Only set RS ctx enable in ctx control reg if 
there is a RS
  715629190ef384a drm/i915/gen9: Set value of Indirect Context Offset based on 
gen version
  032b612e055ecc5 drm/i915: Remove update_sprite_watermarks.
  e8861675c5ccaf3 drm/i915: Kill off intel_crtc->atomic.wait_vblank, v6.
  33c8df89351709e drm/i915: Unify power domain handling.
  74bff5f92740a9d drm/i915: Pass crtc state to modeset_get_crtc_power_domains.
  6831f3e3c640ad4 drm/i915: Add for_each_pipe_masked()
  aae8ba844495473 drm/i915: Make sure pipe interrupts are processed before 
turning off power well on BDW+
  2230fde85cfff29 drm/i915: synchronize_irq() before turning off disp2d power 
well on VLV/CHV
  1ca993d237a587b drm/i915: Skip PIPESTAT reads from irq handler on VLV/CHV 
when power well is down
  9b18572e83bfd53 drm/i915/gen9: Verify and enforce dc6 state writes
  9b6f20984c5402a drm/i915/gen9: Check for DC state mismatch
  53188eb40121a13 drm/i915/skl: Ensure HW is powered during DDB HW state readout
  380bdff2d05b498 drm/i915/lvds: Ensure the HW is powered during HW state 
readout
  31feb61a688bd4b drm/i915/hdmi: Ensure the HW is powered during HW state 
readout
  fe97fd7eb872558 drm/i915/dsi: Ensure the HW is powered during HW state readout
  b81b801f8675838 drm/i915/dp: Ensure the HW is powered during HW state readout
  02f9f5e62a9b0a1 drm/i915: Ensure the HW is powered when accessing the CRC HW 
block
  d59410219ae396a drm/i915/ddi: Ensure the HW is powered during HW state readout
  7a6252c6bce1124 drm/i915/crt: Ensure the HW is powered during HW state readout
  5a24fab098d6f1a drm/i915: Ensure the HW is powered during HW access in 
assert_pipe
  bacd67d6a36c890 drm/i915: Ensure the HW is powered when disabling VGA
  013ef6cfc411bfe drm/i915/ibx: Ensure the HW is powered during PLL HW readout
  9fb84d5a9299ac6 drm/i915: Ensure the HW is powered during display pipe HW 
readout
  5af9a454769bb55 drm/i915: Add helper to get a display power ref if it was 
already enabled
  1e657ad7a48f1ce drm/i915/gen9: Write dc state debugmask bits only once
  5b076889f6239f8 drm/i915/gen9: Extend dmc debug mask to include cores
  779cb5d3ddd7295 drm/i915/gen9: Verify and enforce dc6 state writes
  832dba889e27487 drm/i915/gen9: Check for DC state mismatch
  a98ee79317b4091 drm/i915/fbc: enable FBC by default on HSW and BDW
  0f3a93d1b0cf23c drm/i915: drop unused i915.disable_vtd_wa module parameter
  57b63d00df0ded2 drm/i915: drop write perm from module params which don't 
support changing
  0aa8bdf25b16f5c drm/i915/dsi: Using the bpp value wrt the pixel format
  d6e3af5498390ae drm/i915/bxt: Remove DSP CLK_GATE programming for BXT
  4d800030238878c drm/i915/skl: Ensure HW is powered during DDB HW state readout
  dd75619853e4a28 drm/i915: Extract intel_encoder_has_connectors()
  e28661bd1acbdcb drm/i915: Use atomic state in intel_fb_initial_config.
  7bb4afb45879541 drm/i915: Use correct dpms for intel_enable_crt.
  0eadc62462afcfd drm/i915: Use atomic state in tv load detection.
  c8ecb2f162a6065 drm/i915: Use atomic state for load detect in crt.
  edde361711ef8f3 drm/i915: Use atomic state to obtain load detection crtc, v3.
  9b58e352b463f2f drm/i915: Enable PSR by default on Haswell and Broadwell.
  a38c274faad0ec6 drm/i915: Enable PSR by default on Valleyview and Cherryview.
  d94d6e87138588b drm/i915: Change i915.enable_psr parameter to use per 
platform default.
  69603dbb315fc7a i915: cast before shifting in i915_pte_count
  ecb2448218acf23 drm/i915/lvds: Ensure the HW is powered during HW state 
readout
  5b0921748c0b1d0 drm/i915/hdmi: Ensure the HW is powered

[Kernel-packages] [Bug 1560395] Re: [i915_bpo] Update i915 backport driver

2016-03-23 Thread ash
Will this be bacported for beta final for testing

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

Title:
  [i915_bpo] Update i915 backport driver

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Current snapshot of i915_bpo is based on drm-intel-next-2016-02-14
  tag, and it makes sense to update it to the latest tag leading to 4.6,
  which is drm-intel-next-fixes-2016-03-16:

  94669e6ba1ada13 drm/i915: Handle -ED EADLK in drm_atomic_commit from 
load-detect.
  0bbca274a31c236 drm/i915: Actually retry with bit-banging after GMBUS timeout
  2f791908a70e957 drm/i915: Fix bogus dig_port_map[] assignment for pre-HSW
  eda908967feecf7 drm/i915: Balance assert_rpm_wakelock_held() for 
!IS_ENABLED(CONFIG_PM)
  bd90123c4973821 drm/i915/skl: Fix power domain suspend sequence
  5790ff742b1feee drm/i915: Update DRIVER_DATE to 20160229
  2743179d955bd73 drm/i915: Execlists cannot pin a context without the object
  596c5923197b889 drm/i915: Reduce the pointer dance of i915_is_ggtt()
  1c7f4bca5a6f53c drm/i915: Rename vma->*_list to *_link for consistency
  135dc79efbc119e drm/i915: Balance assert_rpm_wakelock_held() for 
!IS_ENABLED(CONFIG_PM)
  99cf8ea16595ecf drm/i915/lrc: Only set RS ctx enable in ctx control reg if 
there is a RS
  715629190ef384a drm/i915/gen9: Set value of Indirect Context Offset based on 
gen version
  032b612e055ecc5 drm/i915: Remove update_sprite_watermarks.
  e8861675c5ccaf3 drm/i915: Kill off intel_crtc->atomic.wait_vblank, v6.
  33c8df89351709e drm/i915: Unify power domain handling.
  74bff5f92740a9d drm/i915: Pass crtc state to modeset_get_crtc_power_domains.
  6831f3e3c640ad4 drm/i915: Add for_each_pipe_masked()
  aae8ba844495473 drm/i915: Make sure pipe interrupts are processed before 
turning off power well on BDW+
  2230fde85cfff29 drm/i915: synchronize_irq() before turning off disp2d power 
well on VLV/CHV
  1ca993d237a587b drm/i915: Skip PIPESTAT reads from irq handler on VLV/CHV 
when power well is down
  9b18572e83bfd53 drm/i915/gen9: Verify and enforce dc6 state writes
  9b6f20984c5402a drm/i915/gen9: Check for DC state mismatch
  53188eb40121a13 drm/i915/skl: Ensure HW is powered during DDB HW state readout
  380bdff2d05b498 drm/i915/lvds: Ensure the HW is powered during HW state 
readout
  31feb61a688bd4b drm/i915/hdmi: Ensure the HW is powered during HW state 
readout
  fe97fd7eb872558 drm/i915/dsi: Ensure the HW is powered during HW state readout
  b81b801f8675838 drm/i915/dp: Ensure the HW is powered during HW state readout
  02f9f5e62a9b0a1 drm/i915: Ensure the HW is powered when accessing the CRC HW 
block
  d59410219ae396a drm/i915/ddi: Ensure the HW is powered during HW state readout
  7a6252c6bce1124 drm/i915/crt: Ensure the HW is powered during HW state readout
  5a24fab098d6f1a drm/i915: Ensure the HW is powered during HW access in 
assert_pipe
  bacd67d6a36c890 drm/i915: Ensure the HW is powered when disabling VGA
  013ef6cfc411bfe drm/i915/ibx: Ensure the HW is powered during PLL HW readout
  9fb84d5a9299ac6 drm/i915: Ensure the HW is powered during display pipe HW 
readout
  5af9a454769bb55 drm/i915: Add helper to get a display power ref if it was 
already enabled
  1e657ad7a48f1ce drm/i915/gen9: Write dc state debugmask bits only once
  5b076889f6239f8 drm/i915/gen9: Extend dmc debug mask to include cores
  779cb5d3ddd7295 drm/i915/gen9: Verify and enforce dc6 state writes
  832dba889e27487 drm/i915/gen9: Check for DC state mismatch
  a98ee79317b4091 drm/i915/fbc: enable FBC by default on HSW and BDW
  0f3a93d1b0cf23c drm/i915: drop unused i915.disable_vtd_wa module parameter
  57b63d00df0ded2 drm/i915: drop write perm from module params which don't 
support changing
  0aa8bdf25b16f5c drm/i915/dsi: Using the bpp value wrt the pixel format
  d6e3af5498390ae drm/i915/bxt: Remove DSP CLK_GATE programming for BXT
  4d800030238878c drm/i915/skl: Ensure HW is powered during DDB HW state readout
  dd75619853e4a28 drm/i915: Extract intel_encoder_has_connectors()
  e28661bd1acbdcb drm/i915: Use atomic state in intel_fb_initial_config.
  7bb4afb45879541 drm/i915: Use correct dpms for intel_enable_crt.
  0eadc62462afcfd drm/i915: Use atomic state in tv load detection.
  c8ecb2f162a6065 drm/i915: Use atomic state for load detect in crt.
  edde361711ef8f3 drm/i915: Use atomic state to obtain load detection crtc, v3.
  9b58e352b463f2f drm/i915: Enable PSR by default on Haswell and Broadwell.
  a38c274faad0ec6 drm/i915: Enable PSR by default on Valleyview and Cherryview.
  d94d6e87138588b drm/i915: Change i915.enable_psr parameter to use per 
platform default.
  69603dbb315fc7a i915: cast before shifting in i915_pte_count
  ecb2448218acf23 drm/i915/lvds: Ensure the HW is powered during HW state 
readout
  5b0921748c0b1d0 drm/i915/hdmi: Ensure the HW is powered during HW state 
readout
  3f3f42b8

[Kernel-packages] [Bug 1560395] Re: [i915_bpo] Update i915 backport driver

2016-03-23 Thread ash
It also be good idea to add the updated firmware

 http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=0a0c97667d0e80c56de8fd999d17bf2b553aab8f

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

Title:
  [i915_bpo] Update i915 backport driver

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Current snapshot of i915_bpo is based on drm-intel-next-2016-02-14
  tag, and it makes sense to update it to the latest tag leading to 4.6,
  which is drm-intel-next-fixes-2016-03-16:

  94669e6ba1ada13 drm/i915: Handle -ED EADLK in drm_atomic_commit from 
load-detect.
  0bbca274a31c236 drm/i915: Actually retry with bit-banging after GMBUS timeout
  2f791908a70e957 drm/i915: Fix bogus dig_port_map[] assignment for pre-HSW
  eda908967feecf7 drm/i915: Balance assert_rpm_wakelock_held() for 
!IS_ENABLED(CONFIG_PM)
  bd90123c4973821 drm/i915/skl: Fix power domain suspend sequence
  5790ff742b1feee drm/i915: Update DRIVER_DATE to 20160229
  2743179d955bd73 drm/i915: Execlists cannot pin a context without the object
  596c5923197b889 drm/i915: Reduce the pointer dance of i915_is_ggtt()
  1c7f4bca5a6f53c drm/i915: Rename vma->*_list to *_link for consistency
  135dc79efbc119e drm/i915: Balance assert_rpm_wakelock_held() for 
!IS_ENABLED(CONFIG_PM)
  99cf8ea16595ecf drm/i915/lrc: Only set RS ctx enable in ctx control reg if 
there is a RS
  715629190ef384a drm/i915/gen9: Set value of Indirect Context Offset based on 
gen version
  032b612e055ecc5 drm/i915: Remove update_sprite_watermarks.
  e8861675c5ccaf3 drm/i915: Kill off intel_crtc->atomic.wait_vblank, v6.
  33c8df89351709e drm/i915: Unify power domain handling.
  74bff5f92740a9d drm/i915: Pass crtc state to modeset_get_crtc_power_domains.
  6831f3e3c640ad4 drm/i915: Add for_each_pipe_masked()
  aae8ba844495473 drm/i915: Make sure pipe interrupts are processed before 
turning off power well on BDW+
  2230fde85cfff29 drm/i915: synchronize_irq() before turning off disp2d power 
well on VLV/CHV
  1ca993d237a587b drm/i915: Skip PIPESTAT reads from irq handler on VLV/CHV 
when power well is down
  9b18572e83bfd53 drm/i915/gen9: Verify and enforce dc6 state writes
  9b6f20984c5402a drm/i915/gen9: Check for DC state mismatch
  53188eb40121a13 drm/i915/skl: Ensure HW is powered during DDB HW state readout
  380bdff2d05b498 drm/i915/lvds: Ensure the HW is powered during HW state 
readout
  31feb61a688bd4b drm/i915/hdmi: Ensure the HW is powered during HW state 
readout
  fe97fd7eb872558 drm/i915/dsi: Ensure the HW is powered during HW state readout
  b81b801f8675838 drm/i915/dp: Ensure the HW is powered during HW state readout
  02f9f5e62a9b0a1 drm/i915: Ensure the HW is powered when accessing the CRC HW 
block
  d59410219ae396a drm/i915/ddi: Ensure the HW is powered during HW state readout
  7a6252c6bce1124 drm/i915/crt: Ensure the HW is powered during HW state readout
  5a24fab098d6f1a drm/i915: Ensure the HW is powered during HW access in 
assert_pipe
  bacd67d6a36c890 drm/i915: Ensure the HW is powered when disabling VGA
  013ef6cfc411bfe drm/i915/ibx: Ensure the HW is powered during PLL HW readout
  9fb84d5a9299ac6 drm/i915: Ensure the HW is powered during display pipe HW 
readout
  5af9a454769bb55 drm/i915: Add helper to get a display power ref if it was 
already enabled
  1e657ad7a48f1ce drm/i915/gen9: Write dc state debugmask bits only once
  5b076889f6239f8 drm/i915/gen9: Extend dmc debug mask to include cores
  779cb5d3ddd7295 drm/i915/gen9: Verify and enforce dc6 state writes
  832dba889e27487 drm/i915/gen9: Check for DC state mismatch
  a98ee79317b4091 drm/i915/fbc: enable FBC by default on HSW and BDW
  0f3a93d1b0cf23c drm/i915: drop unused i915.disable_vtd_wa module parameter
  57b63d00df0ded2 drm/i915: drop write perm from module params which don't 
support changing
  0aa8bdf25b16f5c drm/i915/dsi: Using the bpp value wrt the pixel format
  d6e3af5498390ae drm/i915/bxt: Remove DSP CLK_GATE programming for BXT
  4d800030238878c drm/i915/skl: Ensure HW is powered during DDB HW state readout
  dd75619853e4a28 drm/i915: Extract intel_encoder_has_connectors()
  e28661bd1acbdcb drm/i915: Use atomic state in intel_fb_initial_config.
  7bb4afb45879541 drm/i915: Use correct dpms for intel_enable_crt.
  0eadc62462afcfd drm/i915: Use atomic state in tv load detection.
  c8ecb2f162a6065 drm/i915: Use atomic state for load detect in crt.
  edde361711ef8f3 drm/i915: Use atomic state to obtain load detection crtc, v3.
  9b58e352b463f2f drm/i915: Enable PSR by default on Haswell and Broadwell.
  a38c274faad0ec6 drm/i915: Enable PSR by default on Valleyview and Cherryview.
  d94d6e87138588b drm/i915: Change i915.enable_psr parameter to use per 
platform default.
  69603dbb315fc7a i915: cast before shifting in i915_pte_count
  ecb2448218acf23 drm/i915/lvds: Ensure the HW is