Re: [Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

I booted the 4.17rc1 kernel.

In order to see output I connected an old TV to the DVI output, and that 
output was successfully detected (through an DVI-HDMI adapter, if that 
matters).

The output of /sys/class/drm/card0-HDMI-A-1 in this case:

dpms: Off

enabled: disabled

modes: (empty)

status: disconnected


I then tried switching which monitor was connected to which port. 
Interestingly, in this case both the Dell U2415 and the old TV could 
show output successfully.

// David

On 2018-05-02 19:50, Harry Wentland wrote:
> Thanks, mind posting the same for the non-working kernel? I'm curious if the 
> problem is
> 1) we don't detect the display
> 2) we don't enable the display
> 3) we enable the display but wrong
>

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

Re: [Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

I'm not sure if you asked for the contents of these files from a working 
or non-working kernel, but I'll take the working kernel since that's 
obviously a lot easier.

The monitor, Dell U2415, is connected via its input source "HDMI (MHL) 
2". The monitor name "DELL U2415" shows up in the edid file.

status: connected

enabled: enabled

dpms: On

modes:

1920x1200
1920x1080
1920x1080
1920x1080i
1920x1080i
1920x1080
1920x1080i
1920x1080
1920x1080
1920x1080
1920x1080
1920x1080
1600x1200
1280x1024
1280x1024
1152x864
1280x720
1280x720
1280x720
1024x768
1024x768
800x600
800x600
720x576
720x576i
720x480
720x480
720x480i
720x480i
640x480
640x480
640x480
720x400

// David

On 2018-05-02 16:11, Harry Wentland wrote:
> Is it HDMI from the board to HDMI on the monitor? I'd like to rule out
> any use of an adapter or HDMI-to-DVI cable.
>
> What monitor is this?
>
> Is the monitor detected?
>
> What do you see in the 'status', 'enabled', 'dpms', and 'modes' files in
> /sys/class/drm/card0-HDMI-A-1/ ?
>

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

Re: [Kernel-packages] [Bug 1761751] Re: [REGRESSION] drm/amd/dc: Add dc display driver (v2)

[David Henningsson]

I don't think it is the same bug. I have a card with HDMI and DVI 
connectors (XFX RX 460). The HDMI connector is connected to the monitor, 
the DVI connector is unplugged.

// David

On 2018-04-30 17:40, Harry Wentland wrote:
> Replied on the ticket.
>
> If this is about non-functioning LVDS or VGA I'm aware of it and trying
> to find time to find a good solution.
>
> Harry
>
> On 2018-04-30 11:14 AM, Joseph Salisbury wrote:
>> Hi Harry,
>>
>> A kernel bug report was opened against Ubuntu [0].  After a kernel
>> bisect, it was found the following commit introduced the bug:
>>
>>
>> commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c
>> Author: Harry Wentland 
>> Date:   Tue Sep 12 15:58:20 2017 -0400
>>
>>      drm/amd/dc: Add dc display driver (v2)
>>
>>
>> The regression was introduced as of v4.15-rc1 and still exists in
>> current mainline.  The commit does not need to be reverted to resolve
>> the bug.  Disabling the CONFIG_DRM_AMD_DC_PRE_VEGA option makes the bug
>> go away.
>> 
>> I was hoping to get your feedback, since you are the patch author.  Do
>> you think gathering any additional data will help diagnose this issue?
>> 
>>
>> Thanks,
>>
>> Joe
>>
>>
>> [0] http://pad.lv/1761751
>>

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 4.15.0-15-generic #16~lp1761751v2: Boots normally

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

The test kernel (4.15.0-15-generic #16~lp1761751) boots normally.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a
diff between the configs on v415-rc2 and v415-rc3 has lots of
differences, the most interesting being this one:


$ diff -u config-4.15.0-041500rc2-generic config-4.15.0-041500rc3-generic
/* ... snip ... */
@@ -5675,9 +5677,9 @@
 # Display Engine Configuration
 #
 CONFIG_DRM_AMD_DC=y
-# CONFIG_DRM_AMD_DC_PRE_VEGA is not set
+CONFIG_DRM_AMD_DC_PRE_VEGA=y
 # CONFIG_DRM_AMD_DC_FBC is not set
-# CONFIG_DRM_AMD_DC_DCN1_0 is not set
+CONFIG_DRM_AMD_DC_DCN1_0=y
 # CONFIG_DEBUG_KERNEL_DC is not set

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 3d7682af228fd78dc46bc: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 5fc62f6a139a7b06b027bf442cd4205619506f59: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 282ef4729195c8503f7101d574acfb5e7c8a8209: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Linux version 4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201804181224: Black screen

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

There's nothing graphics related here:

$ git log v4.15-rc2..a0da456bbf95d2a9294799bb --oneline
a0da456 net: phy-micrel: check return code in flp center function
c7799c0 tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()
cfac7f8 tcp/dccp: block bh before arming time_wait timer
b484d8a Merge branch 'sctp-prsctp-chunk-fixes'
779edd7 sctp: do not abandon the other frags in unsent outq if one msg has 
outstanding frags
e5f6129 sctp: abandon the whole msg if one part of a fragmented message is 
abandoned
d30fc51 sctp: only update outstanding_bytes for transmitted queue when doing 
prsctp_prune
6fef90c net: dsa: bcm_sf2: Set correct CHAIN_ID and slice number mask
f859b4a sit: update frag_off info
3016dad tcp: remove buggy call to tcp_v6_restore_cb()
90a6ec8 act_sample: get rid of tcf_sample_cleanup_rcu()
6c9257a Merge tag 'rxrpc-fixes-20171129' of 
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs
1c08ac0 net: stmmac: dwmac-sun8i: fix allwinner,leds-active-low handling
f8821f9 skbuff: Grammar s/are can/can/, s/change/changes/
a154f8e net: mvpp2: allocate zeroed tx descriptors
282ef47 rxrpc: Fix variable overwrite
5fc62f6 rxrpc: Fix ACK generation from the connection event processor
3d7682a rxrpc: Clean up whitespace

Yet I have double checked that, according /var/log/kern.log,

 - I booted this kernel:

Apr 18 13:18:29 david-desktop kernel: [0.00] Linux version
4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #20180417120

 - I got black screen and the following message:

Apr 18 13:18:29 david-desktop kernel: [1.667490] [drm] Cannot find
any crtc or sizes


And when I last booted this kernel:

Apr 17 06:17:34 david-desktop kernel: [0.00] Linux version
4.15.0-041500rc2-generic (kernel@gloin) (gcc version 7.2.0 (Ubuntu
7.2.0-8ubuntu3)) #201712031230 SMP Sun Dec 3 17:32:03 UTC 2017

...it works just fine.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel a0da456bbf95d2a9294799bb05c61bfb24736bb7: Black screen.

This is starting to feel a bit fishy but maybe git knows what it's
doing. :-)

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel af57b7fffaf74ff337e479abb19026d72065673b: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 2391f0b4808e3d5af348324d69f5f45c56a26836: Black screen.

Kernel 4.17-rc1: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

> I built the first test kernel, up to the following commit:

You mean the second test kernel, I presume?

Kernel 6a5e05a47b6cb8e59bfad351444322b1e4012326: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 4.15rc2+78d9b048446c3c0a83313444fb706f8f3bccdae7: Black screen.

Note: I installed the linux-image-...-generic deb only as the header
ones seemed to require libssl1.1...?

Anyway, I did some research on my own as well.

First, I had a look at the commits between 4.15rc2 and 4.15rc3. The only
one I could see being relevant is this one:

commit a703c55004e1c5076d57e43771b3e7796ea0
Author: Daniel Vetter 
Date:   Mon Dec 4 21:48:18 2017 +0100

drm: safely free connectors from connector_iter

...it seems relevant because the error I get is "Cannot find any crtc or
sizes", and the code emitting this error message (in
drivers/gpu/drm/drm_fb_helper.c) deals with connectors.

This commit is then referenced in other commits later on as being
required to fix, but since 4.16 is "black screen" too those fixes seems
not have helped here.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

4.15.0-041500rc2-generic - Boots normally
4.15.0-041500rc3-generic - Black screen
4.15.0-041500rc4-generic - Not tested

So something between rc2 and rc3 it is then...

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ - Boots 
normally
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ - Boots 
normally
v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ - Black 
screen
v4.15-rc9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/ - Black 
screen
v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ - Black screen
v4.16-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ - Not tested

I'll try rc2, rc3 and rc4 next.

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Ok, so I found this message when trying to boot a faulty kernel without
workaround, if it helps:

[1.797127] [drm] Cannot find any crtc or sizes
[1.799000] [drm] Initialized amdgpu 3.23.0 20150101 for :23:00.0 on 
minor 0

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

** Description changed:

  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.
  
  It probably started during an upgrade this week or last week. As a start
  I'm blaming the Linux kernel since booting a 4.13 kernel works just
  fine.
  
  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
-  * linux-image-4.16.0-041600-generic (mainline kernel),
+  * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.
  
  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci as
  a start.
+ 
+ EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
+ parameters.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

** Description changed:

  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.
  
  It probably started during an upgrade this week or last week. As a start
  I'm blaming the Linux kernel since booting a 4.13 kernel works just
  fine.
  
- Known faulty kernel versions are: 
-  * linux-image-4.15.0-041500-generic (mainline kernel),
-  * linux-image-4.15.0-13-generic (Ubuntu kernel), 
-  * whatever comes with 18.04 daily live USB stick as of 20180404.
+ Known faulty kernel versions are:
+  * linux-image-4.15.0-041500-generic (mainline kernel),
+  * linux-image-4.16.0-041600-generic (mainline kernel),
+  * linux-image-4.15.0-13-generic (Ubuntu kernel),
+  * whatever comes with 18.04 daily live USB stick as of 20180404.
  
  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci as
  a start.

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  New

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+attachment/5104013/+files/lspci.txt

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  New

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are: 
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel), 
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] [NEW] Black screen on 18.04 + AMD RX460

[David Henningsson]

Public bug reported:

I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.

It probably started during an upgrade this week or last week. As a start
I'm blaming the Linux kernel since booting a 4.13 kernel works just
fine.

Known faulty kernel versions are: 
 * linux-image-4.15.0-041500-generic (mainline kernel),
 * linux-image-4.15.0-13-generic (Ubuntu kernel), 
 * whatever comes with 18.04 daily live USB stick as of 20180404.

Not sure how to best collect logs and system information for you since
I'm not used to debugging black screens, so I'm just attaching lspci as
a start.

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

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

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  New

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are: 
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel), 
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

** Description changed:

+ Note: Current workaround is to add pci=noaer to your kernel command
+ line:
+ 
+ 1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
+ GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
+ 2) run "sudo update-grub"
+ 3) reboot
+ 
+ 
+ 
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens after
  reboot.
  
  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
- [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
+ [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
- [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
+ [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
-  /dev/snd/controlC0:  david  1502 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
+  /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-19-generic N/A
-  linux-backports-modules-4.2.0-19-generic  N/A
-  linux-firmware1.153
+  linux-restricted-modules-4.2.0-19-generic N/A
+  linux-backports-modules-4.2.0-19-generic  N/A
+  linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: 

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

Btw, I reported mine upstream long ago and got response from upstream
that "I've thought about this problem a bit, but realistically I don't
have time to do the fix I'd like to do /.../ Anybody else who is
interested should feel free to take a crack at it."

See http://permalink.gmane.org/gmane.linux.kernel.pci/48697

Also some googling finds me a few other reports with very similar
symptoms, e g:

https://bugzilla.kernel.org/show_bug.cgi?id=111601

https://lkml.org/lkml/2015/9/2/573


** Bug watch added: Linux Kernel Bug Tracker #111601
   http://bugzilla.kernel.org/show_bug.cgi?id=111601

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

Out of curiousity, do all of you have the combination of Skylake +
RTL8723BE, and second, do you experience (as I do) that wifi doesn't
work very well (often loses connections etc)?

...as the errors seem to indicate some kind of physical error between
the Skylake/Sunrise Point host controller and the wifi card.

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1548844] Re: Inspiron 13-7359: rfkill button has no effect

[David Henningsson]

Hi and thanks for spotting! My BIOS has been updated now.

1) Dmidecode now shows:

01.06.00
02/25/2016

2) The hotkey still does not work, but now there is a message in dmesg
when you press it:

dell_wmi: Unknown key with scancode 0xe008 pressed

or

dell_wmi: Unknown key 0xe008 pressed

The former is with upstream 4.5rc5, the latter with Ubuntu's
4.4.0-11-generic.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Inspiron 13-7359: rfkill button has no effect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Nothing happens when the button to enable/disable rfkill (a k a
  "airplane mode" or "wifi/bluetooth disable") is pressed.

  Most other buttons seems to work according to evtest although some of
  them has no effect (and the "switch video mode" button generates
  Alt-P). Some of the buttons generate messages like:

  [  335.755925] dell_wmi: Unknown WMI event type 0x00: 0xe00c
  [  335.755928] dell_wmi: Unknown WMI event type 0x00: 0x3

  ...but the rfkill button is not one of them.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1809 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 23 15:26:41 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548844/+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 1549660] Re: Fix speaker volume on a Dell machine

[David Henningsson]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

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

Title:
  Fix speaker volume on a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  On one of the machines we enable, we found that the actual speaker
  volume did not always correspond to the volume set in alsamixer.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549660/+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 1549660] Re: [PATCH] ALSA: hda - Fixup speaker pass-through control for nid 0x14 on ALC225

[David Henningsson]

On 2016-02-25 09:29, Takashi Iwai wrote:
> On Thu, 25 Feb 2016 09:13:21 +0100,
> David Henningsson wrote:
>>
>> On one of the machines we enable, we found that the actual speaker volume
>> did not always correspond to the volume set in alsamixer. This patch
>> fixes that problem.
>>
>> This patch was orginally written by Kailang @ Realtek, I've rebased it
>> to fit sound git master.
>>
>> BugLink: https://bugs.launchpad.net/bugs/1549660
>> Co-Authored-By: Kailang <kail...@realtek.com>
>> Signed-off-by: David Henningsson <david.hennings...@canonical.com>
>
> This conflicts with the latest for-linus branch right after I applied
> another fixup addition.  Could you again rebase to for-linus branch?

Ok, done now. Let me know when it's pushed out. Thanks!

> Also, I guess it deserves Cc to stable?

I guess so too, so added in v2. I'm always a bit scared to do so when
  1) we deal with machines that are not released yet
  2) there are verbs in there which only Kailang knows the true meaning 
of...


>
>
> thanks,
>
> Takashi
>
>> ---
>>   sound/pci/hda/patch_realtek.c | 23 +--
>>   1 file changed, 21 insertions(+), 2 deletions(-)
>>
>> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
>> index efd4980..ab353b0 100644
>> --- a/sound/pci/hda/patch_realtek.c
>> +++ b/sound/pci/hda/patch_realtek.c
>> @@ -3801,6 +3801,10 @@ static void alc_headset_mode_mic_in(struct hda_codec 
>> *codec, hda_nid_t hp_pin,
>>
>>   static void alc_headset_mode_default(struct hda_codec *codec)
>>   {
>> +static struct coef_fw coef0225[] = {
>> +UPDATE_COEF(0x45, 0x3f<<10, 0x34<<10),
>> +{}
>> +};
>>  static struct coef_fw coef0255[] = {
>>  WRITE_COEF(0x45, 0xc089),
>>  WRITE_COEF(0x45, 0xc489),
>> @@ -3842,6 +3846,9 @@ static void alc_headset_mode_default(struct hda_codec 
>> *codec)
>>  };
>>
>>  switch (codec->core.vendor_id) {
>> +case 0x10ec0225:
>> +alc_process_coef_fw(codec, coef0225);
>> +break;
>>  case 0x10ec0255:
>>  case 0x10ec0256:
>>  alc_process_coef_fw(codec, coef0255);
>> @@ -4749,6 +4756,7 @@ enum {
>>  ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE,
>>  ALC293_FIXUP_LENOVO_SPK_NOISE,
>>  ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY,
>> +ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
>>   };
>>
>>   static const struct hda_fixup alc269_fixups[] = {
>> @@ -5368,6 +5376,17 @@ static const struct hda_fixup alc269_fixups[] = {
>>  .type = HDA_FIXUP_FUNC,
>>  .v.func = alc233_fixup_lenovo_line2_mic_hotkey,
>>  },
>> +[ALC225_FIXUP_DELL1_MIC_NO_PRESENCE] = {
>> +.type = HDA_FIXUP_VERBS,
>> +.v.verbs = (const struct hda_verb[]) {
>> +/* Disable pass-through path for FRONT 14h */
>> +{ 0x20, AC_VERB_SET_COEF_INDEX, 0x36 },
>> +{ 0x20, AC_VERB_SET_PROC_COEF, 0x57d7 },
>> +{}
>> +},
>> +.chained = true,
>> +.chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE
>> +},
>>   };
>>
>>   static const struct snd_pci_quirk alc269_fixup_tbl[] = {
>> @@ -5638,10 +5657,10 @@ static const struct hda_model_fixup 
>> alc269_fixup_models[] = {
>>  {0x21, 0x03211020}
>>
>>   static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = {
>> -SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
>> ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
>> +SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
>> ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
>>  ALC225_STANDARD_PINS,
>>  {0x14, 0x901701a0}),
>> -SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
>> ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
>> +SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
>> ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
>>  ALC225_STANDARD_PINS,
>>  {0x14, 0x901701b0}),
>>  SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, "Dell", 
>> ALC255_FIXUP_DELL2_MIC_NO_PRESENCE,
>> --
>> 1.9.1
>>
>

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

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

Title:
  Fix speaker volume on a Dell machine

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

Bug description:
  On one of the machines we enable, we found that the actual speaker
  volume did not always correspond to the volume set in alsamixer.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549660/+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 1549660] [PATCH v2] ALSA: hda - Fixup speaker pass-through control for nid 0x14 on ALC225

[David Henningsson]

On one of the machines we enable, we found that the actual speaker volume
did not always correspond to the volume set in alsamixer. This patch
fixes that problem.

This patch was orginally written by Kailang @ Realtek, I've rebased it
to fit sound git master.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1549660
Co-Authored-By: Kailang <kail...@realtek.com>
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/patch_realtek.c | 23 +--
 1 file changed, 21 insertions(+), 2 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 72fa58d..7fded69 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -3801,6 +3801,10 @@ static void alc_headset_mode_mic_in(struct hda_codec 
*codec, hda_nid_t hp_pin,
 
 static void alc_headset_mode_default(struct hda_codec *codec)
 {
+   static struct coef_fw coef0225[] = {
+   UPDATE_COEF(0x45, 0x3f<<10, 0x34<<10),
+   {}
+   };
static struct coef_fw coef0255[] = {
WRITE_COEF(0x45, 0xc089),
WRITE_COEF(0x45, 0xc489),
@@ -3842,6 +3846,9 @@ static void alc_headset_mode_default(struct hda_codec 
*codec)
};
 
switch (codec->core.vendor_id) {
+   case 0x10ec0225:
+   alc_process_coef_fw(codec, coef0225);
+   break;
case 0x10ec0255:
case 0x10ec0256:
alc_process_coef_fw(codec, coef0255);
@@ -4750,6 +4757,7 @@ enum {
ALC293_FIXUP_LENOVO_SPK_NOISE,
ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY,
ALC255_FIXUP_DELL_SPK_NOISE,
+   ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
 };
 
 static const struct hda_fixup alc269_fixups[] = {
@@ -5375,6 +5383,17 @@ static const struct hda_fixup alc269_fixups[] = {
.chained = true,
.chain_id = ALC255_FIXUP_DELL1_MIC_NO_PRESENCE
},
+   [ALC225_FIXUP_DELL1_MIC_NO_PRESENCE] = {
+   .type = HDA_FIXUP_VERBS,
+   .v.verbs = (const struct hda_verb[]) {
+   /* Disable pass-through path for FRONT 14h */
+   { 0x20, AC_VERB_SET_COEF_INDEX, 0x36 },
+   { 0x20, AC_VERB_SET_PROC_COEF, 0x57d7 },
+   {}
+   },
+   .chained = true,
+   .chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE
+   },
 };
 
 static const struct snd_pci_quirk alc269_fixup_tbl[] = {
@@ -5646,10 +5665,10 @@ static const struct hda_model_fixup 
alc269_fixup_models[] = {
{0x21, 0x03211020}
 
 static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = {
-   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
+   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC225_STANDARD_PINS,
{0x14, 0x901701a0}),
-   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
+   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC225_STANDARD_PINS,
{0x14, 0x901701b0}),
SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, "Dell", 
ALC255_FIXUP_DELL2_MIC_NO_PRESENCE,
-- 
1.9.1

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

Title:
  Fix speaker volume on a Dell machine

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

Bug description:
  On one of the machines we enable, we found that the actual speaker
  volume did not always correspond to the volume set in alsamixer.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549660/+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 1549660] [PATCH] ALSA: hda - Fixup speaker pass-through control for nid 0x14 on ALC225

[David Henningsson]

On one of the machines we enable, we found that the actual speaker volume
did not always correspond to the volume set in alsamixer. This patch
fixes that problem.

This patch was orginally written by Kailang @ Realtek, I've rebased it
to fit sound git master.

BugLink: https://bugs.launchpad.net/bugs/1549660
Co-Authored-By: Kailang <kail...@realtek.com>
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/patch_realtek.c | 23 +--
 1 file changed, 21 insertions(+), 2 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index efd4980..ab353b0 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -3801,6 +3801,10 @@ static void alc_headset_mode_mic_in(struct hda_codec 
*codec, hda_nid_t hp_pin,
 
 static void alc_headset_mode_default(struct hda_codec *codec)
 {
+   static struct coef_fw coef0225[] = {
+   UPDATE_COEF(0x45, 0x3f<<10, 0x34<<10),
+   {}
+   };
static struct coef_fw coef0255[] = {
WRITE_COEF(0x45, 0xc089),
WRITE_COEF(0x45, 0xc489),
@@ -3842,6 +3846,9 @@ static void alc_headset_mode_default(struct hda_codec 
*codec)
};
 
switch (codec->core.vendor_id) {
+   case 0x10ec0225:
+   alc_process_coef_fw(codec, coef0225);
+   break;
case 0x10ec0255:
case 0x10ec0256:
alc_process_coef_fw(codec, coef0255);
@@ -4749,6 +4756,7 @@ enum {
ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE,
ALC293_FIXUP_LENOVO_SPK_NOISE,
ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY,
+   ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
 };
 
 static const struct hda_fixup alc269_fixups[] = {
@@ -5368,6 +5376,17 @@ static const struct hda_fixup alc269_fixups[] = {
.type = HDA_FIXUP_FUNC,
.v.func = alc233_fixup_lenovo_line2_mic_hotkey,
},
+   [ALC225_FIXUP_DELL1_MIC_NO_PRESENCE] = {
+   .type = HDA_FIXUP_VERBS,
+   .v.verbs = (const struct hda_verb[]) {
+   /* Disable pass-through path for FRONT 14h */
+   { 0x20, AC_VERB_SET_COEF_INDEX, 0x36 },
+   { 0x20, AC_VERB_SET_PROC_COEF, 0x57d7 },
+   {}
+   },
+   .chained = true,
+   .chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE
+   },
 };
 
 static const struct snd_pci_quirk alc269_fixup_tbl[] = {
@@ -5638,10 +5657,10 @@ static const struct hda_model_fixup 
alc269_fixup_models[] = {
{0x21, 0x03211020}
 
 static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = {
-   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
+   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC225_STANDARD_PINS,
{0x14, 0x901701a0}),
-   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC269_FIXUP_DELL1_MIC_NO_PRESENCE,
+   SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", 
ALC225_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC225_STANDARD_PINS,
{0x14, 0x901701b0}),
SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, "Dell", 
ALC255_FIXUP_DELL2_MIC_NO_PRESENCE,
-- 
1.9.1

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

Title:
  Fix speaker volume on a Dell machine

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

Bug description:
  On one of the machines we enable, we found that the actual speaker
  volume did not always correspond to the volume set in alsamixer.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549660/+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 1549660] [NEW] Fix speaker volume on a Dell machine

[David Henningsson]

Public bug reported:

On one of the machines we enable, we found that the actual speaker
volume did not always correspond to the volume set in alsamixer.

This bug is for tracking purposes; please do not triage.

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

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

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

Title:
  Fix speaker volume on a Dell machine

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

Bug description:
  On one of the machines we enable, we found that the actual speaker
  volume did not always correspond to the volume set in alsamixer.

  This bug is for tracking purposes; please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549660/+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 1548844] Re: Inspiron 13-7359: rfkill button has no effect

[David Henningsson]

Verified with mainline kernel  4.5.0-040500rc5-generic, problem present
there as well.

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

Title:
  Inspiron 13-7359: rfkill button has no effect

Status in linux package in Ubuntu:
  New

Bug description:
  Nothing happens when the button to enable/disable rfkill (a k a
  "airplane mode" or "wifi/bluetooth disable") is pressed.

  Most other buttons seems to work according to evtest although some of
  them has no effect (and the "switch video mode" button generates
  Alt-P). Some of the buttons generate messages like:

  [  335.755925] dell_wmi: Unknown WMI event type 0x00: 0xe00c
  [  335.755928] dell_wmi: Unknown WMI event type 0x00: 0x3

  ...but the rfkill button is not one of them.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1809 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 23 15:26:41 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548844/+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 1548844] [NEW] Inspiron 13-7359: rfkill button has no effect

[David Henningsson]

Public bug reported:

Nothing happens when the button to enable/disable rfkill (a k a
"airplane mode" or "wifi/bluetooth disable") is pressed.

Most other buttons seems to work according to evtest although some of
them has no effect (and the "switch video mode" button generates Alt-P).
Some of the buttons generate messages like:

[  335.755925] dell_wmi: Unknown WMI event type 0x00: 0xe00c
[  335.755928] dell_wmi: Unknown WMI event type 0x00: 0x3

...but the rfkill button is not one of them.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-6-generic 4.4.0-6.21
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  david  1809 F pulseaudio
CurrentDesktop: Unity
Date: Tue Feb 23 15:26:41 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
InstallationDate: Installed on 2015-11-28 (87 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
MachineType: Dell Inc. Inspiron 13-7359
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-6-generic N/A
 linux-backports-modules-4.4.0-6-generic  N/A
 linux-firmware   1.156
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0NT3WX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 13-7359
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug 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/1548844

Title:
  Inspiron 13-7359: rfkill button has no effect

Status in linux package in Ubuntu:
  New

Bug description:
  Nothing happens when the button to enable/disable rfkill (a k a
  "airplane mode" or "wifi/bluetooth disable") is pressed.

  Most other buttons seems to work according to evtest although some of
  them has no effect (and the "switch video mode" button generates
  Alt-P). Some of the buttons generate messages like:

  [  335.755925] dell_wmi: Unknown WMI event type 0x00: 0xe00c
  [  335.755928] dell_wmi: Unknown WMI event type 0x00: 0x3

  ...but the rfkill button is not one of them.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1809 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 23 15:26:41 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548844/+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 1540511] [PATCH] [xenial] (upstream) HID: multitouch: fix input mode switching on some Elan panels

[David Henningsson]

From: Benjamin Tissoires <benjamin.tissoi...@redhat.com>

as reported by https://bugzilla.kernel.org/show_bug.cgi?id=108481

This bug reports mentions 6d4f5440 ("HID: multitouch: Fetch feature
reports on demand for Win8 devices") as the origin of the problem but this
commit actually masked 2 firmware bugs that are annihilating each other:

The report descriptor declares two features in reports 3 and 5:

0x05, 0x0d,// Usage Page (Digitizers) 318
0x09, 0x0e,// Usage (Device Configuration)320
0xa1, 0x01,// Collection (Application)322
0x85, 0x03,//  Report ID (3)  324
0x09, 0x22,//  Usage (Finger) 326
0xa1, 0x00,//  Collection (Physical)  328
0x09, 0x52,//   Usage (Inputmode) 330
0x15, 0x00,//   Logical Minimum (0)   332
0x25, 0x0a,//   Logical Maximum (10)  334
0x75, 0x08,//   Report Size (8)   336
0x95, 0x02,//   Report Count (2)  338
0xb1, 0x02,//   Feature (Data,Var,Abs)340
0xc0,  //  End Collection 342
0x09, 0x22,//  Usage (Finger) 343
0xa1, 0x00,//  Collection (Physical)  345
0x85, 0x05,//   Report ID (5) 347
0x09, 0x57,//   Usage (Surface Switch)349
0x09, 0x58,//   Usage (Button Switch) 351
0x15, 0x00,//   Logical Minimum (0)   353
0x75, 0x01,//   Report Size (1)   355
0x95, 0x02,//   Report Count (2)  357
0x25, 0x03,//   Logical Maximum (3)   359
0xb1, 0x02,//   Feature (Data,Var,Abs)361
0x95, 0x0e,//   Report Count (14) 363
0xb1, 0x03,//   Feature (Cnst,Var,Abs)365
0xc0,  //  End Collection 367

The report ID 3 presents 2 input mode features, while only the first one
is handled by the device. Given that we did not checked if one was
previously assigned, we were dealing with the ignored featured and we
should never have been able to switch this panel into the multitouch mode.

However, the firmware presents an other bugs which allowed 6d4f5440
to counteract the faulty report descriptor. When we request the values
of the feature 5, the firmware answers "03 03 00". The fields are correct
but the report id is wrong. Before 6d4f5440, we retrieved all the features
and injected them in the system. So when we called report 5, we injected
in the system the report 3 with the values "03 00".
Setting the second input mode to 03 in this report changed it to "03 03"
and the touchpad switched to the mt mode. We could have set anything
in the second field because the actual value (the first 03 in this report)
was given by the query of report ID 5.

To sum up: 2 bugs in the firmware were hiding that we were accessing the
wrong feature.

Signed-off-by: Benjamin Tissoires <benjamin.tissoi...@redhat.com>
Signed-off-by: Jiri Kosina <jkos...@suse.cz>

BugLink: https://bugs.launchpad.net/bugs/1540511
(cherry picked from commit 73e7d63efb4d774883a338997943bfa59e127085)
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 drivers/hid/hid-multitouch.c | 15 +--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
index 351ddd2..4ee7716 100644
--- a/drivers/hid/hid-multitouch.c
+++ b/drivers/hid/hid-multitouch.c
@@ -357,8 +357,19 @@ static void mt_feature_mapping(struct hid_device *hdev,
break;
}
 
-   td->inputmode = field->report->id;
-   td->inputmode_index = usage->usage_index;
+   if (td->inputmode < 0) {
+   td->inputmode = field->report->id;
+   td->inputmode_index = usage->usage_index;
+   } else {
+   /*
+* Some elan panels wrongly declare 2 input mode
+* features, and silently ignore when we set the
+* value in the second field. Skip the second feature
+* and hope for the best.
+*/
+   dev_info(>dev,
+"Ignoring the extra HID_DG_INPUTMODE\n");
+   }
 
break;
case

[Kernel-packages] [Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

https://bugzilla.kernel.org/show_bug.cgi?id=108481

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+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 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

Ok, I've now built and tested a kernel with 4.4 + the below commit and
can confirm that this commit fixes the touchpad issue for me.

commit 8a7fa6187191f005d4b6d29913de6e128cc778e2
Author: Benjamin Tissoires 
Date:   Tue Dec 1 12:41:38 2015 +0100

HID: multitouch: fix input mode switching on some Elan panels


** Bug watch added: Linux Kernel Bug Tracker #108481
   http://bugzilla.kernel.org/show_bug.cgi?id=108481

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+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 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

it bisect start
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old: [1289ace5b4f70f1e68ce785735b82c7e483de863] Merge tag 'scsi-misc' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
git bisect old 1289ace5b4f70f1e68ce785735b82c7e483de863
# new: [984065055e6e39f8dd812529e11922374bd39352] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect new 984065055e6e39f8dd812529e11922374bd39352
# new: [a016af2e70bfca23f2f5de7d8708157b86ea374d] Merge tag 'sound-4.5-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
git bisect new a016af2e70bfca23f2f5de7d8708157b86ea374d
# new: [d45187aaf0e256d23da2f7694a7826524499aa31] Merge branch 'dmi-for-linus' 
of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging
git bisect new d45187aaf0e256d23da2f7694a7826524499aa31
# new: [c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67] Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid
git bisect new c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67
# old: [5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05] Merge tag 
'devicetree-for-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
git bisect old 5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05
# old: [63f729cb4aa9a224cfd6bb35eab6b4556c29115d] Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
git bisect old 63f729cb4aa9a224cfd6bb35eab6b4556c29115d
# old: [210c7c1750fdf769647d1d526c9ea34c412c9eee] NFS: Use wait_on_atomic_t() 
for unlock after readahead
git bisect old 210c7c1750fdf769647d1d526c9ea34c412c9eee

Looked through remaining commits, I'm going to try this one next, looks
promising:

commit 73e7d63efb4d774883a338997943bfa59e127085
Author: Benjamin Tissoires 
Date:   Tue Dec 1 12:41:38 2015 +0100

HID: multitouch: fix input mode switching on some Elan panels

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+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 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

Tested kernels so far:

4.3.0-7 ubuntu - good (touchpad working)
4.5.0-040500rc3 - good (touchpad working)
4.4.0-4 ubuntu - bad (touchpad not working)
4.4.1-040401 - bad (touchpad not working)
4.5.0-040500rc1 - good (touchpad working)

Looks like a temporary regression in 4.4 - maybe we can bisect between
4.4 and 4.5rc1 to see if it's something we can backport?

** Tags added: kernel-fixed-upstream

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+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 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

A few more commits...

# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old: [1289ace5b4f70f1e68ce785735b82c7e483de863] Merge tag 'scsi-misc' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
git bisect old 1289ace5b4f70f1e68ce785735b82c7e483de863
# new: [984065055e6e39f8dd812529e11922374bd39352] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect new 984065055e6e39f8dd812529e11922374bd39352
# new: [a016af2e70bfca23f2f5de7d8708157b86ea374d] Merge tag 'sound-4.5-rc1' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
git bisect new a016af2e70bfca23f2f5de7d8708157b86ea374d
# new: [d45187aaf0e256d23da2f7694a7826524499aa31] Merge branch 'dmi-for-linus' 
of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging
git bisect new d45187aaf0e256d23da2f7694a7826524499aa31
# new: [c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67] Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid
git bisect new c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67
# old: [5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05] Merge tag 
'devicetree-for-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
git bisect old 5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+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 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

I'm working on it, here's the result so far:

$ git bisect log
git bisect start
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old: [1289ace5b4f70f1e68ce785735b82c7e483de863] Merge tag 'scsi-misc' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
git bisect old 1289ace5b4f70f1e68ce785735b82c7e483de863
# new: [984065055e6e39f8dd812529e11922374bd39352] Merge branch 'drm-next' of 
git://people.freedesktop.org/~airlied/linux
git bisect new 984065055e6e39f8dd812529e11922374bd39352

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+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 1540406] [NEW] warning: file-aligned section .text extends beyond end of file

[David Henningsson]

Public bug reported:

When running a dist-upgrade, I received the following warning:

Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  1 15:58:45 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-28 (65 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  warning: file-aligned section .text extends beyond end of file

Status in linux-signed package in Ubuntu:
  New

Bug description:
  When running a dist-upgrade, I received the following warning:

  Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
  warning: file-aligned section .text extends beyond end of file
  warning: checksum areas are greater than image size. Invalid section table?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:58:45 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+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 1540511] [NEW] Touchpad not working (4.3 -> 4.4 regression)

[David Henningsson]

Public bug reported:

When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
working. When booting 4.3 kernels, the touchpad is works.

Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
What happens instead: nothing.

I've tried an upstream 4.4 kernel; problem is present there as well.

I've booted with pci=noaer due to another bug that would otherwise spam
dmesg. Removing it does not fix the problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-2-generic 4.4.0-2.16
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  david  1759 F pulseaudio
CurrentDesktop: Unity
Date: Mon Feb  1 18:49:25 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
InstallationDate: Installed on 2015-11-28 (65 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
MachineType: Dell Inc. Inspiron 13-7359
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-2-generic N/A
 linux-backports-modules-4.4.0-2-generic  N/A
 linux-firmware   1.155
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0NT3WX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 13-7359
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug xenial

** Description changed:

  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.
  
  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.
+ 
+ I've tried an upstream 4.4 kernel; problem is present there as well.
+ 
+ I've booted with pci=noaer due to another bug that would otherwise spam
+ dmesg. Removing it does not fix the problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  david  1759 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-2-generic N/A
-  linux-backports-modules-4.4.0-2-generic  N/A
-  linux-firmware   1.155
+  linux-restricted-modules-4.4.0-2-generic N/A
+  linux-backports-modules-4.4.0-2-generic  N/A
+  linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 

[Kernel-packages] [Bug 1540406] Re: warning: file-aligned section .text extends beyond end of file

[David Henningsson]

** Description changed:

  When running a dist-upgrade, I received the following warning:
  
  Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
  warning: file-aligned section .text extends beyond end of file
  warning: checksum areas are greater than image size. Invalid section table?
+ 
+ Note: I've tried booting the kernel with dmesg enabled, it seems to boot
+ just fine. See https://launchpadlibrarian.net/235948033/CurrentDmesg.txt
+ for when I booted it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:58:45 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  warning: file-aligned section .text extends beyond end of file

Status in linux-signed package in Ubuntu:
  New

Bug description:
  When running a dist-upgrade, I received the following warning:

  Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
  warning: file-aligned section .text extends beyond end of file
  warning: checksum areas are greater than image size. Invalid section table?

  Note: I've tried booting the kernel with dmesg enabled, it seems to
  boot just fine. See
  https://launchpadlibrarian.net/235948033/CurrentDmesg.txt for when I
  booted it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:58:45 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+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 1529624] Re: Lenovo E50-80 inverted microphone not detected properly

[David Henningsson]

Inform userspace that one channel of the internal mic has reversed
polarity, so it does not attempt to add both channels together and
end up with silence.

Cc: sta...@vger.kernel.org
Reported-by: Andrzej Mendel <andrzej.men...@gmail.com>
Alsa-info: 
http://www.alsa-project.org/db/?f=3088f82a0cf977855f92af9db8ad406c04f71efa
BugLink: https://bugs.launchpad.net/bugs/1529624
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/patch_realtek.c | 8 
 1 file changed, 8 insertions(+)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 3a89d82..2fdda51 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -4666,6 +4666,7 @@ enum {
ALC290_FIXUP_SUBWOOFER,
ALC290_FIXUP_SUBWOOFER_HSJACK,
ALC269_FIXUP_THINKPAD_ACPI,
+   ALC269_FIXUP_DMIC_THINKPAD_ACPI,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC255_FIXUP_DELL2_MIC_NO_PRESENCE,
ALC255_FIXUP_HEADSET_MODE,
@@ -5103,6 +5104,12 @@ static const struct hda_fixup alc269_fixups[] = {
.type = HDA_FIXUP_FUNC,
.v.func = hda_fixup_thinkpad_acpi,
},
+   [ALC269_FIXUP_DMIC_THINKPAD_ACPI] = {
+   .type = HDA_FIXUP_FUNC,
+   .v.func = alc_fixup_inv_dmic,
+   .chained = true,
+   .chain_id = ALC269_FIXUP_THINKPAD_ACPI,
+   },
[ALC255_FIXUP_DELL1_MIC_NO_PRESENCE] = {
.type = HDA_FIXUP_PINS,
.v.pins = (const struct hda_pintbl[]) {
@@ -5457,6 +5464,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x17aa, 0x2226, "ThinkPad X250", 
ALC292_FIXUP_TPT440_DOCK),
SND_PCI_QUIRK(0x17aa, 0x2233, "Thinkpad", 
ALC293_FIXUP_LENOVO_SPK_NOISE),
SND_PCI_QUIRK(0x17aa, 0x30bb, "ThinkCentre AIO", 
ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY),
+   SND_PCI_QUIRK(0x17aa, 0x3902, "Lenovo E50-80", 
ALC269_FIXUP_DMIC_THINKPAD_ACPI),
SND_PCI_QUIRK(0x17aa, 0x3977, "IdeaPad S210", ALC283_FIXUP_INT_MIC),
SND_PCI_QUIRK(0x17aa, 0x3978, "IdeaPad Y410P", ALC269_FIXUP_NO_SHUTUP),
SND_PCI_QUIRK(0x17aa, 0x5013, "Thinkpad", 
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
-- 
1.9.1


** Changed in: alsa-driver (Ubuntu)
   Status: New => In Progress

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: David Henningsson (diwic) => (unassigned)

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

Title:
  Lenovo E50-80 inverted microphone not detected properly

Status in linux package in Ubuntu:
  In Progress

Bug description:
  System: Lenovo E50-80 with Ubuntu 15.10. Tested with both kernel
  4.2.0-22-generic from official repos and 4.4.0-040400rc6-generic from
  Mainline Kernel repo.

  Alsa information: http://www.alsa-
  project.org/db/?f=3088f82a0cf977855f92af9db8ad406c04f71efa

  Internal microphone does not pick up sound by default. When I mute one
  channel, it works (this is not a good workaround since some
  application, such as Facebook Messenger, unmute both channels and set
  them to the same level automatically).

  Adding model=inv-dmic to snd-hda-intel module options does not change
  a thing.

  Hope that helps, tell me if you need more info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529624/+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 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

** Bug watch removed: Linux Kernel Bug Tracker #109691
   http://bugzilla.kernel.org/show_bug.cgi?id=109691

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

Hi,

Indeed booting with pci=noaer (as suggested in the other bug) works 
around this issue as well. I'll use that for the time being.

Thanks for working on it!

// David

On 2015-12-29 16:58, Bjorn Helgaas wrote:
> On Fri, Dec 18, 2015 at 11:30:33AM +0100, David Henningsson wrote:
>> Hi Linux PCI maintainers,
>>
>> My dmesg gets filled with a few lines repeated over and over again:
>>
>> pcieport :00:1c.0: AER: Corrected error received: id=00e0
>> pcieport :00:1c.0: can't find device of ID00e0
>> pcieport :00:1c.0: AER: Corrected error received: id=00e0
>> pcieport :00:1c.0: PCIe Bus Error: severity=Corrected,
>> type=Physical Layer, id=00e0(Receiver ID)
>> pcieport :00:1c.0:   device [8086:9d14] error
>> status/mask=0001/2000
>> pcieport :00:1c.0:[ 0] Receiver Error
>>
>> This happens 10-30 times per second (!), so dmesg fills up quickly.
>> The bug is present in both vanilla and Ubuntu kernels.
>
> This is a pretty obvious bug in our AER code.  We normally clear
> correctable errors by writing the PCI_ERR_COR_STATUS register in
> handle_error_source().  The execution path looks like this:
>
>aer_isr_one_error
>  aer_print_port_info
>  if (find_source_device())
>aer_process_err_devices
>  handle_error_source
>pci_write_config_dword(dev, PCI_ERR_COR_STATUS, ...)
>
> In this case, find_source_device() printed "can't find device of
> ID00e0" [sic] and returned false, so we don't call
> aer_process_err_devices().  The error is never cleared, so
> we discover it again and again.
>
> I'll work on fixing this.  Incidentally, there's another report
> with similar symptoms here:
>
>https://bugzilla.kernel.org/show_bug.cgi?id=109691
>
> Bjorn
>

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic


** Bug watch added: Linux Kernel Bug Tracker #109691
   http://bugzilla.kernel.org/show_bug.cgi?id=109691

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
 

[Kernel-packages] [Bug 1526330] [NEW] Fix mic-in mode for a few Dell laptops

[David Henningsson]

Public bug reported:

This is bug is for tracking purposes only, please do not triage.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

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

Title:
  Fix mic-in mode for a few Dell laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1526330/+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 1526330] [PATCH] ALSA: hda - Fix headphone mic input on a few Dell ALC293 machines

[David Henningsson]

These laptops support both headphone, headset and mic modes
for the 3.5mm jack.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1526330
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/patch_realtek.c | 17 -
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 8dd2ac1..b745a72 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -4606,6 +4606,7 @@ enum {
ALC288_FIXUP_DISABLE_AAMIX,
ALC292_FIXUP_DELL_E7X,
ALC292_FIXUP_DISABLE_AAMIX,
+   ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK,
ALC298_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC275_FIXUP_DELL_XPS,
ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE,
@@ -5169,6 +5170,12 @@ static const struct hda_fixup alc269_fixups[] = {
.chained = true,
.chain_id = ALC269_FIXUP_DELL2_MIC_NO_PRESENCE
},
+   [ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK] = {
+   .type = HDA_FIXUP_FUNC,
+   .v.func = alc_fixup_disable_aamix,
+   .chained = true,
+   .chain_id = ALC293_FIXUP_DELL1_MIC_NO_PRESENCE
+   },
[ALC292_FIXUP_DELL_E7X] = {
.type = HDA_FIXUP_FUNC,
.v.func = alc_fixup_dell_xps13,
@@ -5247,11 +5254,11 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1028, 0x06c7, "Dell", 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x06d9, "Dell", 
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x06da, "Dell", 
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
-   SND_PCI_QUIRK(0x1028, 0x06db, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
-   SND_PCI_QUIRK(0x1028, 0x06dd, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
-   SND_PCI_QUIRK(0x1028, 0x06de, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
-   SND_PCI_QUIRK(0x1028, 0x06df, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
-   SND_PCI_QUIRK(0x1028, 0x06e0, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
+   SND_PCI_QUIRK(0x1028, 0x06db, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
+   SND_PCI_QUIRK(0x1028, 0x06dd, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
+   SND_PCI_QUIRK(0x1028, 0x06de, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
+   SND_PCI_QUIRK(0x1028, 0x06df, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
+   SND_PCI_QUIRK(0x1028, 0x06e0, "Dell", 
ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK),
SND_PCI_QUIRK(0x1028, 0x0704, "Dell XPS 13", 
ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE),
SND_PCI_QUIRK(0x1028, 0x164a, "Dell", 
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x164b, "Dell", 
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
-- 
1.9.1

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

Title:
  Fix mic-in mode for a few Dell laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1526330/+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 1526330] Re: Fix mic-in mode for a few Dell laptops

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Fix mic-in mode for a few Dell laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This is bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1526330/+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 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

The spam rate is 150 lines per second. With ~80 characters per line,
that's about 50 MB per hour. As a very rough measure.

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1523232] Re: Packard Bell DOTS inverted internal microphone

[David Henningsson]

> Otherwise, the modules are not installed with a message saying that
they are included since 3.99 kernel (not sure of the version as I didn't
save the results)

Oops, a problem with the DKMS packaging. Thanks for the heads up, will
be fixed in the next build.

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

Title:
  Packard Bell DOTS inverted internal microphone

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  As stated in 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978,
  I attached the alsa-info txt to this bug for the Packard Bell DOTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523232/+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 1523232] Re: Packard Bell DOTS inverted internal microphone

[David Henningsson]

On the internal mic of the Packard Bell DOTS, one channel
has an inverted signal. Add a quirk to fix this up.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1523232
Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/patch_realtek.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 9bedf7c..ebc5362 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -6409,6 +6409,7 @@ static const struct hda_fixup alc662_fixups[] = {
 static const struct snd_pci_quirk alc662_fixup_tbl[] = {
SND_PCI_QUIRK(0x1019, 0x9087, "ECS", ALC662_FIXUP_ASUS_MODE2),
SND_PCI_QUIRK(0x1025, 0x022f, "Acer Aspire One", ALC662_FIXUP_INV_DMIC),
+   SND_PCI_QUIRK(0x1025, 0x0241, "Packard Bell DOTS", 
ALC662_FIXUP_INV_DMIC),
SND_PCI_QUIRK(0x1025, 0x0308, "Acer Aspire 8942G", ALC662_FIXUP_ASPIRE),
SND_PCI_QUIRK(0x1025, 0x031c, "Gateway NV79", ALC662_FIXUP_SKU_IGNORE),
SND_PCI_QUIRK(0x1025, 0x0349, "eMachines eM250", ALC662_FIXUP_INV_DMIC),
-- 
1.9.1


** Changed in: alsa-driver (Ubuntu)
   Status: New => In Progress

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Packard Bell DOTS inverted internal microphone

Status in linux package in Ubuntu:
  In Progress

Bug description:
  As stated in 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978,
  I attached the alsa-info txt to this bug for the Packard Bell DOTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523232/+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 1523232] Re: Packard Bell DOTS inverted internal microphone

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Packard Bell DOTS inverted internal microphone

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  As stated in 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978,
  I attached the alsa-info txt to this bug for the Packard Bell DOTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523232/+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 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

I've tried upgrading BIOS to 1.2.0 (latest version on Dell website) and
also with the v4.4-rc3-wily kernel. The dmesg is still spammed with the
same error.

** Tags added: kernel-bug-exists-upstream

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+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 1521173] [NEW] AER: Corrected error received: id=00e0

[David Henningsson]

Public bug reported:

My dmesg gets completely spammed with the following messages appearing
over and over again. It stops after one s3 cycle; it only happens after
reboot.

[ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
[ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
[ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
[ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
[ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
[ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
[ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
[ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
[ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
[ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
[ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
[ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
[ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
[ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
 /dev/snd/controlC0:  david  1502 F pulseaudio
CurrentDesktop: Unity
Date: Mon Nov 30 13:19:00 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
InstallationDate: Installed on 2015-11-28 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
MachineType: Dell Inc. Inspiron 13-7359
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-19-generic N/A
 linux-backports-modules-4.2.0-19-generic  N/A
 linux-firmware1.153
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.00.00
dmi.board.name: 0NT3WX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 13-7359
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug 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/1521173

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  

[Kernel-packages] [Bug 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)

[David Henningsson]

Well, if you have an external mic plugged in, that overrides the
internal mic and uses the external one instead.

Double-check that you don't have an external mic plugged in, and if you
still see a problem, please attach an alsa-info (
https://wiki.ubuntu.com/Audio/AlsaInfo ) with the DKMS installed (and no
external mic plugged in).

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

Title:
  Lenovo G50-80 - Inverted Internal microphone (phase inversion)

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Can confirm the bug on Lenovo g50-80.

  Alsa-hda-dkms package doesn't help (there is no "Inverted Internal
  Mic" entry in alsamixer after reboot).

  Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but
  it doesn't help.

  Workaround "mute right channel" works but can it be fixed permanently
  (I don't want to manually mute right mic channel every time I use
  skype)?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   nikola 1819 F...m pulseaudio
   /dev/snd/controlC1:  nikola 1819 F pulseaudio
   /dev/snd/controlC0:  nikola 1819 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 10 15:31:56 2015
  InstallationDate: Installed on 2015-10-06 (3 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN72WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80L0
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+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 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)

[David Henningsson]

You should get notifications in this bug when that's about to happen.
I'd say everything from 2 weeks to 2 months depending on SRU cycle
timing.

Meanwhile using the DKMS packages (
https://www.ubuntu.com/Audio/UpgradingAlsa/DKMS ) should fix your issue.

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

Title:
  Lenovo G50-80 - Inverted Internal microphone (phase inversion)

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Can confirm the bug on Lenovo g50-80.

  Alsa-hda-dkms package doesn't help (there is no "Inverted Internal
  Mic" entry in alsamixer after reboot).

  Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but
  it doesn't help.

  Workaround "mute right channel" works but can it be fixed permanently
  (I don't want to manually mute right mic channel every time I use
  skype)?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   nikola 1819 F...m pulseaudio
   /dev/snd/controlC1:  nikola 1819 F pulseaudio
   /dev/snd/controlC0:  nikola 1819 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 10 15:31:56 2015
  InstallationDate: Installed on 2015-10-06 (3 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN72WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80L0
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+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 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)

[David Henningsson]

** Changed in: alsa-driver (Ubuntu)
   Status: New => In Progress

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Lenovo G50-80 - Inverted Internal microphone (phase inversion)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Can confirm the bug on Lenovo g50-80.

  Alsa-hda-dkms package doesn't help (there is no "Inverted Internal
  Mic" entry in alsamixer after reboot).

  Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but
  it doesn't help.

  Workaround "mute right channel" works but can it be fixed permanently
  (I don't want to manually mute right mic channel every time I use
  skype)?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   nikola 1819 F...m pulseaudio
   /dev/snd/controlC1:  nikola 1819 F pulseaudio
   /dev/snd/controlC0:  nikola 1819 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 10 15:31:56 2015
  InstallationDate: Installed on 2015-10-06 (3 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN72WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80L0
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+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 1504778] Re: Lenovo G50-80 - Inverted Internal microphone (phase inversion)

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Lenovo G50-80 - Inverted Internal microphone (phase inversion)

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Can confirm the bug on Lenovo g50-80.

  Alsa-hda-dkms package doesn't help (there is no "Inverted Internal
  Mic" entry in alsamixer after reboot).

  Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but
  it doesn't help.

  Workaround "mute right channel" works but can it be fixed permanently
  (I don't want to manually mute right mic channel every time I use
  skype)?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   nikola 1819 F...m pulseaudio
   /dev/snd/controlC1:  nikola 1819 F pulseaudio
   /dev/snd/controlC0:  nikola 1819 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 10 15:31:56 2015
  InstallationDate: Installed on 2015-10-06 (3 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN72WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.name: 80L0
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504778/+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 1398277] Re: [Feature] Skylake audio support (HD/HDMI/DP audio)

[David Henningsson]

Hi Tim and thanks for taking care of it so far - for consistency, would
you mind adding two more:

commit d5f362a7b977bdfaf8a955f3d604a29267bd5464
Author: David Henningsson <david.hennings...@canonical.com>
Date:   Thu Sep 3 11:51:35 2015 +0200

drm/i915: Add locks around audio component bind/unbind

And:

commit f0675d4a8ed9d3e863ff611561ee0944969a2784
Author: David Henningsson <david.hennings...@canonical.com>
Date:   Thu Sep 3 11:51:34 2015 +0200

drm/i915: Drop port_mst_index parameter from pin/eld callback


that brings us more in line with both 4.3 as well as in 3.19. (Because 
upstream made a mistake, the four patches we have in 3.19 corresponds to the 
six pointed out by Xiong and me.)

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

Title:
  [Feature] Skylake audio support (HD/HDMI/DP audio)

Status in intel:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Support for Skylake audio (HD/HDMI/DP audio)

  Upstream status:
  Alpha – Done （ww 03）
  Beta – Done (ww12)
  PV – Done (ww23)

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1398277/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

[David Henningsson]

>From a private bug:

I have verified kernel 3.19.0-29.31~14.04.1 on , this issue
is fixed. The HDMI audio device is available and works fine.

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1490895/+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 1490895] Re: Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

[David Henningsson]

> On Skylake platform I encounter shutdown hang without HDMI plug issue 
 > the system stop at "init: wait-for-state (plymouth-shutdown lightdm)"
 > Log attached

Thanks for testing. Can you confirm that this is an actual regression
with the patch set, i e, that it does not happen with the previous 3.19
kernel ( 3.19.0-28.30 )?

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] Re: [UBUNTU (3.19) PATCH 0/4] i915 to call HDA on HDMI hotplug

[David Henningsson]

On 2015-09-01 21:38, Brad Figg wrote:
> On Tue, Sep 01, 2015 at 12:04:05PM +0200, David Henningsson wrote:
>> This is a patch set fixing a long-standing bug for some Haswell, Broadwell 
>> and most Skylake machines.
>>
>> When the HDA audio controller is in D3, a hotplug event (i e, HDMI or 
>> DisplayPort being plugged in) fails to wake up the audio side so it never 
>> registers that something has happened.
>>
>> By having the i915 driver call directly into the hda driver, the HDA driver 
>> is always notified that an HDMI hotplug event has happened.
>>
>> I've been trying to get this through upstream, but it has been slower than 
>> usual due to it touching both the i915 and HDA subsystems, and ideally I 
>> wanted it in there first, but I don't think OEM wants to miss another SRU 
>> cycle. So this is on its way in upstream, but not there yet. The patches 
>> here are based on v5 of my patch set, and v4 were both reviewed by Jani 
>> Nikula and Takashi Iwai.
>>
>> Now, I've tested the upstream version, but I've just backported this to 3.19 
>> without any testing. I could use Timo's assistance here so we coordinate 
>> testing this with other i915 changes for the next SRU cycle. And I could use 
>> Timo's help to make sure this applies equally to i915 and i915_bpo.
>>
>> BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895
> I want to see some positive test results in the bug before I'm going to
> take this.

Me too. :-)

Once Timo has a finished build (and I've provided him with a version 
that actually compiles, *ahem*), could Anthony help assign people to 
help us test it? It would be very nice if we could have this tested on 
more than one of (Skylake / Broadwell / Haswell).

@Anthony, if you look at the duplicates for bug 1490895 (e g, 1383997) I 
think you'll quickly understand what all of this is about.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1383997] Re: HDMI audio hot-plug detection does not work well with laptop running on battery with 14.04

[David Henningsson]

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

** This bug has been marked a duplicate of bug 1490895
   Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

Title:
  HDMI audio hot-plug detection does not work well with laptop running
  on battery with 14.04

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

Bug description:
  CID: 201307-14037 Dell Vostro 5470

  There is no HDMI audio output option available when you connect the
  HDMI monitor (with speaker) to this system.

  Verified with cold plug, still no luck.

  However, HDMI audio could be detected with cold plug on 12.04.4 (3.11
  kernel) stock Ubuntu, tested with LiveUSB

  Alsa-info:
  http://www.alsa-project.org/db/?f=8e5ccdaae7aa4b3a05862385b902f824be65f0bd

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1589 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1589 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Tue Oct 21 22:44:45 2014
  HibernationDevice: RESUME=UUID=420e55c0-b179-44d6-93d7-82393cdeec68
  InstallationDate: Installed on 2014-10-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Vostro 5470
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=a975e1af-1e52-4f17-8e69-190b4dc36b48 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: White Tip Mountain
  dmi.board.vendor: Intel Corp.
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd08/23/2013:svnDellInc.:pnVostro5470:pvr:rvnIntelCorp.:rnWhiteTipMountain:rvrFAB3:cvnIntelCorporation:ct9:cvr0.1:
  dmi.product.name: Vostro 5470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1383997/+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 1433891] Re: [Lenovo E?50 I+A] There is no 'HDMI / DisplayPort' selection in output tab of Sound Setting when plug in HDMI cable on the port.

[David Henningsson]

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

** This bug is no longer a duplicate of bug 1383997
   HDMI audio hot-plug detection does not work well with laptop running on 
battery with 14.04
** This bug has been marked a duplicate of bug 1490895
   Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

Title:
  [Lenovo E?50 I+A] There is no 'HDMI / DisplayPort' selection in output
  tab of Sound Setting when plug in HDMI cable on the port.

Status in HWE Next:
  New
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201411-16167 Lenovo E550 (I+A) with 14.04.2 (utopic)
  CID : 201409-15790 Lenovo E450 (I+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450.
  2. Connect HDMI cable.
  3. Navigate to System setting -> Sound -> output, observe the result.
  4. Un-plug HDMI cable, then install fglrx.
  5. Reboot system.
  6. Connect HDMI cable.
  7. Navigate to System setting -> Sound -> output, observe the result.

  Expected result:
  Step 3 and 7, there should be a 'HDMI / DisplayPort' selection in output tab

  Actual result:
  There is no 'HDMI / DisplayPort' selection in output tab

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: 
boot/vmlinuz-3.16.0-30-generic]
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 02:03:48 2015
  InstallationDate: Installed on 2015-03-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1433891/+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 1393701] Re: [Dell Inspiron 3442] HDMI audio hotplug detection is not working on 14.04.1

[David Henningsson]

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

** This bug is no longer a duplicate of bug 1383997
   HDMI audio hot-plug detection does not work well with laptop running on 
battery with 14.04
** This bug has been marked a duplicate of bug 1490895
   Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

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

Title:
  [Dell Inspiron 3442] HDMI audio hotplug detection is not working on
  14.04.1

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

Bug description:
  CID: 201402-14675 Dell Inspiron 3442

  The HDMI audio detection does not work on this system with 14.04 +
  update (3.13.0-39)

  Steps:
  1. Install 14.04 + update (3.13.0-39), boot to desktop
  2. Connect an external monitor to the HDMI port

  Expected result:
  * External display available, HDMI audio output option available

  Actual result:
  * Only the external display will be available, no HDMI audio output.

  Debugging info:
  It works with cold-plug.
  Also, if you play a wav file by using "aplay -D hdmi:HDMI,0 test.wav" 
command, it will make the output option available in "Sound Settings"

  ubuntu@201402-14675:~$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  Adding "options snd-hda-intel jackpoll_ms=500" into  /etc/modprobe.d
  /alsa-base.conf as stated in [1] could make the detection work with
  hotplug.

  Alsa-info: http://www.alsa-
  project.org/db/?f=a3e7fabf6a0c1e35d511e610dfdbe7b9d2b305f6

  [1]
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383997/comments/5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-39-generic 3.13.0-39.66
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1527 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1527 F pulseaudio
   /dev/snd/pcmC1D0c:   ubuntu 1527 F...m pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Tue Nov 18 02:54:12 2014
  HibernationDevice: RESUME=UUID=6a176ac4-beb1-4a03-99e6-fd6b53e8b230
  InstallationDate: Installed on 2014-11-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3442
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=e3da6884-4737-4003-b0ae-efab9daa5157 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-39-generic N/A
   linux-backports-modules-3.13.0-39-generic  N/A
   linux-firmware 1.127.8
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 00G010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd02/24/2014:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn00G010:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3442
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1393701/+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 1490895] [UBUNTU (3.19) PATCH 0/4] i915 to call HDA on HDMI hotplug

[David Henningsson]

This is a patch set fixing a long-standing bug for some Haswell,
Broadwell and most Skylake machines.

When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
DisplayPort being plugged in) fails to wake up the audio side so it
never registers that something has happened.

By having the i915 driver call directly into the hda driver, the HDA
driver is always notified that an HDMI hotplug event has happened.

I've been trying to get this through upstream, but it has been slower
than usual due to it touching both the i915 and HDA subsystems, and
ideally I wanted it in there first, but I don't think OEM wants to miss
another SRU cycle. So this is on its way in upstream, but not there yet.
The patches here are based on v5 of my patch set, and v4 were both
reviewed by Jani Nikula and Takashi Iwai.

Now, I've tested the upstream version, but I've just backported this to
3.19 without any testing. I could use Timo's assistance here so we
coordinate testing this with other i915 changes for the next SRU cycle.
And I could use Timo's help to make sure this applies equally to i915
and i915_bpo.

BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895

David Henningsson (4):
  drm/i915: Add audio pin sense / ELD callback
  drm/i915: Call audio pin/ELD notify function
  ALSA: hda - allow codecs to access the i915 pin/ELD callback
  ALSA: hda - Wake the codec up on pin/ELD notify events

 drivers/gpu/drm/i915/i915_drv.h|  1 +
 drivers/gpu/drm/i915/intel_audio.c | 27 ---
 include/drm/i915_component.h   | 16 
 sound/pci/hda/hda_i915.c   | 10 ++
 sound/pci/hda/hda_intel.h  |  5 +
 sound/pci/hda/patch_hdmi.c | 21 -
 6 files changed, 76 insertions(+), 4 deletions(-)

-- 
1.9.1

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] [PATCH 1/4] drm/i915: Add audio pin sense / ELD callback

[David Henningsson]

This callback will be called by the i915 driver to notify the hda
driver that its HDMI information needs to be refreshed, i e,
that audio output is now available (or unavailable) - usually as a
result of a monitor being plugged in (or unplugged).

Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 include/drm/i915_component.h | 16 
 1 file changed, 16 insertions(+)

diff --git a/include/drm/i915_component.h b/include/drm/i915_component.h
index c9a8b64..c0f4d45 100644
--- a/include/drm/i915_component.h
+++ b/include/drm/i915_component.h
@@ -34,6 +34,22 @@ struct i915_audio_component {
void (*codec_wake_override)(struct device *, bool enable);
int (*get_cdclk_freq)(struct device *);
} *ops;
+
+   const struct i915_audio_component_audio_ops {
+   /**
+* @audio_ptr:
+*
+* Pointer to pass when calling pin_eld_notify.
+*/
+   void *audio_ptr;
+   /**
+* @pin_eld_notify:
+*
+* Called from i915 driver, notifying the HDA driver that
+* pin sense and/or ELD information has changed.
+*/
+   void (*pin_eld_notify)(void *audio_ptr, int port);
+   } *audio_ops;
 };
 
 #endif /* _I915_COMPONENT_H_ */
-- 
1.9.1

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] [PATCH 2/4] drm/i915: Call audio pin/ELD notify function

[David Henningsson]

When the audio codec is enabled or disabled, notify the audio driver.
This will enable the audio driver to get the notification at all times
(even when audio is in different powersave states).

Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 drivers/gpu/drm/i915/i915_drv.h|  1 +
 drivers/gpu/drm/i915/intel_audio.c | 27 ---
 2 files changed, 25 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index e437bb0..146ef60 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -1700,6 +1700,7 @@ struct drm_i915_private {
struct drm_property *force_audio_property;
 
/* hda/i915 audio component */
+   struct i915_audio_component *audio_component;
bool audio_component_registered;
 
uint32_t hw_context_size;
diff --git a/drivers/gpu/drm/i915/intel_audio.c 
b/drivers/gpu/drm/i915/intel_audio.c
index 530f0d6..3348e60 100644
--- a/drivers/gpu/drm/i915/intel_audio.c
+++ b/drivers/gpu/drm/i915/intel_audio.c
@@ -404,6 +404,9 @@ void intel_audio_codec_enable(struct intel_encoder 
*intel_encoder)
struct drm_connector *connector;
struct drm_device *dev = encoder->dev;
struct drm_i915_private *dev_priv = dev->dev_private;
+   struct i915_audio_component *acomp = dev_priv->audio_component;
+   struct intel_digital_port *intel_dig_port = enc_to_dig_port(encoder);
+   enum port port = intel_dig_port->port;
 
connector = drm_select_eld(encoder, mode);
if (!connector)
@@ -424,6 +427,9 @@ void intel_audio_codec_enable(struct intel_encoder 
*intel_encoder)
 
if (dev_priv->display.audio_codec_enable)
dev_priv->display.audio_codec_enable(connector, intel_encoder, 
mode);
+
+   if (acomp && acomp->audio_ops && acomp->audio_ops->pin_eld_notify)
+   acomp->audio_ops->pin_eld_notify(acomp->audio_ops->audio_ptr, 
(int) port);
 }
 
 /**
@@ -433,13 +439,20 @@ void intel_audio_codec_enable(struct intel_encoder 
*intel_encoder)
  * The disable sequences must be performed before disabling the transcoder or
  * port.
  */
-void intel_audio_codec_disable(struct intel_encoder *encoder)
+void intel_audio_codec_disable(struct intel_encoder *intel_encoder)
 {
-   struct drm_device *dev = encoder->base.dev;
+   struct drm_encoder *encoder = _encoder->base;
+   struct drm_device *dev = encoder->dev;
struct drm_i915_private *dev_priv = dev->dev_private;
+   struct i915_audio_component *acomp = dev_priv->audio_component;
+   struct intel_digital_port *intel_dig_port = enc_to_dig_port(encoder);
+   enum port port = intel_dig_port->port;
 
if (dev_priv->display.audio_codec_disable)
-   dev_priv->display.audio_codec_disable(encoder);
+   dev_priv->display.audio_codec_disable(intel_encoder);
+
+   if (acomp && acomp->audio_ops && acomp->audio_ops->pin_eld_notify)
+   acomp->audio_ops->pin_eld_notify(acomp->audio_ops->audio_ptr, 
(int) port);
 }
 
 /**
@@ -529,12 +542,16 @@ static int i915_audio_component_bind(struct device 
*i915_dev,
 struct device *hda_dev, void *data)
 {
struct i915_audio_component *acomp = data;
+   struct drm_i915_private *dev_priv = dev_to_i915(i915_dev);
 
if (WARN_ON(acomp->ops || acomp->dev))
return -EEXIST;
 
+   drm_modeset_lock_all(dev_priv->dev);
acomp->ops = _audio_component_ops;
acomp->dev = i915_dev;
+   dev_priv->audio_component = acomp;
+   drm_modeset_unlock_all(dev_priv->dev);
 
return 0;
 }
@@ -543,9 +560,13 @@ static void i915_audio_component_unbind(struct device 
*i915_dev,
struct device *hda_dev, void *data)
 {
struct i915_audio_component *acomp = data;
+   struct drm_i915_private *dev_priv = dev_to_i915(i915_dev);
 
+   drm_modeset_lock_all(dev_priv->dev);
acomp->ops = NULL;
acomp->dev = NULL;
+   dev_priv->audio_component = NULL;
+   drm_modeset_unlock_all(dev_priv->dev);
 }
 
 static const struct component_ops i915_audio_component_bind_ops = {
-- 
1.9.1

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  B

[Kernel-packages] [Bug 1490895] [PATCH 3/4] ALSA: hda - allow codecs to access the i915 pin/ELD callback

[David Henningsson]

This lets the interested codec be notified when an i915 pin/ELD
event happens.

Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/hda_i915.c  | 10 ++
 sound/pci/hda/hda_intel.h |  5 +
 2 files changed, 15 insertions(+)

diff --git a/sound/pci/hda/hda_i915.c b/sound/pci/hda/hda_i915.c
index aec8a0e..b6eadf1 100644
--- a/sound/pci/hda/hda_i915.c
+++ b/sound/pci/hda/hda_i915.c
@@ -108,6 +108,16 @@ void haswell_set_bclk(struct hda_intel *hda)
azx_writew(>chip, EM5, bclk_n);
 }
 
+int snd_hdac_i915_register_notifier(const struct 
i915_audio_component_audio_ops *aops)
+{
+   if (WARN_ON(!hdac_acomp))
+   return -ENODEV;
+
+   hdac_acomp->audio_ops = aops;
+   return 0;
+}
+EXPORT_SYMBOL_GPL(snd_hdac_i915_register_notifier);
+
 static int hda_component_master_bind(struct device *dev)
 {
struct snd_card *card = dev_get_drvdata(dev);
diff --git a/sound/pci/hda/hda_intel.h b/sound/pci/hda/hda_intel.h
index 51cd664..51b940c 100644
--- a/sound/pci/hda/hda_intel.h
+++ b/sound/pci/hda/hda_intel.h
@@ -54,6 +54,7 @@ void haswell_set_bclk(struct hda_intel *hda);
 int hda_i915_init(struct hda_intel *hda);
 int hda_i915_init_bpo(struct hda_intel *hda);
 int hda_i915_exit(struct hda_intel *hda);
+int snd_hdac_i915_register_notifier(const struct 
i915_audio_component_audio_ops *);
 #else
 static inline int hda_set_codec_wakeup(struct hda_intel *hda, bool enable)
 {
@@ -80,6 +81,10 @@ static inline int hda_i915_exit_bpo(void)
 {
return 0;
 }
+static inline int snd_hdac_i915_register_notifier(const struct 
i915_audio_component_audio_ops *)
+{
+   return -ENODEV;
+}
 #endif
 
 #endif
-- 
1.9.1

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] [PATCH 4/4] ALSA: hda - Wake the codec up on pin/ELD notify events

[David Henningsson]

Whenever there is an event from the i915 driver, wake the codec
and recheck plug/unplug + ELD status.

This fixes the issue with lost unsol events in power save mode,
the codec and controller can now sleep in D3 and still know when
the HDMI monitor has been connected.

Right now, this might mean we get two callbacks from the same event,
one from the unsol event and one from the i915 driver, but this is
not harmful and can be optimised away in a later patch.

Signed-off-by: David Henningsson <david.hennings...@canonical.com>
---
 sound/pci/hda/patch_hdmi.c | 21 -
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
index b422e40..8fe466b 100644
--- a/sound/pci/hda/patch_hdmi.c
+++ b/sound/pci/hda/patch_hdmi.c
@@ -40,6 +40,7 @@
 #include "hda_codec.h"
 #include "hda_local.h"
 #include "hda_jack.h"
+#include "hda_intel.h"
 
 static bool static_hdmi_pcm;
 module_param(static_hdmi_pcm, bool, 0644);
@@ -145,6 +146,9 @@ struct hdmi_spec {
 */
struct hda_multi_out multiout;
struct hda_pcm_stream pcm_playback;
+
+   /* i915/powerwell (Haswell+/Valleyview+) specific */
+   struct i915_audio_component_audio_ops i915_audio_ops;
 };
 
 
@@ -2201,6 +2205,9 @@ static void generic_hdmi_free(struct hda_codec *codec)
struct hdmi_spec *spec = codec->spec;
int pin_idx;
 
+   if (is_haswell_plus(codec) || is_valleyview_plus(codec))
+   snd_hdac_i915_register_notifier(NULL);
+
for (pin_idx = 0; pin_idx < spec->num_pins; pin_idx++) {
struct hdmi_spec_per_pin *per_pin = get_pin(spec, pin_idx);
 
@@ -2327,6 +2334,14 @@ static void haswell_set_power_state(struct hda_codec 
*codec, hda_nid_t fg,
snd_hda_codec_set_power_to_all(codec, fg, power_state);
 }
 
+static void intel_pin_eld_notify(void *audio_ptr, int port)
+{
+   struct hda_codec *codec = audio_ptr;
+   int pin_nid = port + 0x04;
+
+   check_presence_and_report(codec, pin_nid);
+}
+
 static int patch_generic_hdmi(struct hda_codec *codec)
 {
struct hdmi_spec *spec;
@@ -2344,8 +2359,12 @@ static int patch_generic_hdmi(struct hda_codec *codec)
intel_haswell_fixup_enable_dp12(codec);
}
 
-   if (is_haswell_plus(codec) || is_valleyview_plus(codec))
+   if (is_haswell_plus(codec) || is_valleyview_plus(codec)) {
codec->depop_delay = 0;
+   spec->i915_audio_ops.audio_ptr = codec;
+   spec->i915_audio_ops.pin_eld_notify = intel_pin_eld_notify;
+   snd_hdac_i915_register_notifier(>i915_audio_ops);
+   }
 
if (hdmi_parse_codec(codec) < 0) {
codec->spec = NULL;
-- 
1.9.1

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1490895] [NEW] Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

[David Henningsson]

Public bug reported:

This is a long-standing bug for some Haswell, Broadwell and most Skylake
machines.

When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
DisplayPort being plugged in) fails to wake up the audio side so it
never registers that something has happened.

By having the i915 driver call directly into the hda driver, the HDA
driver is always notified that an HDMI hotplug event has happened.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

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

Title:
  Skylake/Broadwell/Haswell: No HDMI audio jack detection in D3

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a long-standing bug for some Haswell, Broadwell and most
  Skylake machines.

  When the HDA audio controller is in D3, a hotplug event (i e, HDMI or
  DisplayPort being plugged in) fails to wake up the audio side so it
  never registers that something has happened.

  By having the i915 driver call directly into the hda driver, the HDA
  driver is always notified that an HDMI hotplug event has happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490895/+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 1487345] Re: Noises from CX20722 codec after reboot

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Noises from CX20722 codec after reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is meant for tracking purposes. Please do not triage.

  On shutdown/reboot of CX20722, first shut down all EAPDs, then
  shut down the afg node to D3.

  Failure to do so can lead to spurious noises from the internal speaker
  directly after reboot (and before the codec is reinitialized again, such as 
in BIOS setup or GRUB menus).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1487345/+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 1487345] [NEW] Noises from CX20722 codec after reboot

[David Henningsson]

Public bug reported:

This bug is meant for tracking purposes. Please do not triage.

On shutdown/reboot of CX20722, first shut down all EAPDs, then
shut down the afg node to D3.

Failure to do so can lead to spurious noises from the internal speaker
directly after reboot (and before the codec is reinitialized again, such as in 
BIOS setup or GRUB menus).

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Description changed:

  This bug is meant for tracking purposes. Please do not triage.
+ 
+ On shutdown/reboot of CX20722, first shut down all EAPDs, then
+ shut down the afg node to D3.
+ 
+ Failure to do so can lead to spurious noises from the internal speaker
+ directly after reboot (and before the codec is reinitialized again, such as 
in BIOS setup or GRUB menus).

** Changed in: linux (Ubuntu)
   Status: New = In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

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

Title:
  Noises from CX20722 codec after reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is meant for tracking purposes. Please do not triage.

  On shutdown/reboot of CX20722, first shut down all EAPDs, then
  shut down the afg node to D3.

  Failure to do so can lead to spurious noises from the internal speaker
  directly after reboot (and before the codec is reinitialized again, such as 
in BIOS setup or GRUB menus).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1487345/+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 1487345] [PATCH] ALSA: hda - Shutdown CX20722 on reboot/free to avoid spurious noises

[David Henningsson]

On shutdown/reboot of CX20722, first shut down all EAPDs, then
shut down the afg node to D3.

Failure to do so can lead to spurious noises from the internal speaker
directly after reboot (and before the codec is reinitialized again, i e
in BIOS setup or GRUB menus).

BugLink: https://bugs.launchpad.net/bugs/1487345
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_conexant.c | 23 ++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/sound/pci/hda/patch_conexant.c b/sound/pci/hda/patch_conexant.c
index f788a91..ca03c40 100644
--- a/sound/pci/hda/patch_conexant.c
+++ b/sound/pci/hda/patch_conexant.c
@@ -200,12 +200,33 @@ static int cx_auto_init(struct hda_codec *codec)
return 0;
 }
 
-#define cx_auto_free   snd_hda_gen_free
+static void cx_auto_reboot_notify(struct hda_codec *codec)
+{
+   struct conexant_spec *spec = codec-spec;
+
+   if (codec-core.vendor_id != 0x14f150f2)
+   return;
+
+   /* Turn the CX20722 codec into D3 to avoid spurious noises
+  from the internal speaker during (and after) reboot */
+   cx_auto_turn_eapd(codec, spec-num_eapds, spec-eapds, false);
+
+   snd_hda_codec_set_power_to_all(codec, codec-core.afg, AC_PWRST_D3);
+   snd_hda_codec_write(codec, codec-core.afg, 0,
+   AC_VERB_SET_POWER_STATE, AC_PWRST_D3);
+}
+
+static void cx_auto_free(struct hda_codec *codec)
+{
+   cx_auto_reboot_notify(codec);
+   snd_hda_gen_free(codec);
+}
 
 static const struct hda_codec_ops cx_auto_patch_ops = {
.build_controls = cx_auto_build_controls,
.build_pcms = snd_hda_gen_build_pcms,
.init = cx_auto_init,
+   .reboot_notify = cx_auto_reboot_notify,
.free = cx_auto_free,
.unsol_event = snd_hda_jack_unsol_event,
 #ifdef CONFIG_PM
-- 
1.9.1

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

Title:
  Noises from CX20722 codec after reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is meant for tracking purposes. Please do not triage.

  On shutdown/reboot of CX20722, first shut down all EAPDs, then
  shut down the afg node to D3.

  Failure to do so can lead to spurious noises from the internal speaker
  directly after reboot (and before the codec is reinitialized again, such as 
in BIOS setup or GRUB menus).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1487345/+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 1487345] Re: [PATCH] ALSA: hda - Shutdown CX20722 on reboot/free to avoid spurious noises

[David Henningsson]

On 2015-08-21 10:26, Takashi Iwai wrote:
 On Fri, 21 Aug 2015 09:42:35 +0200,
 David Henningsson wrote:

 On shutdown/reboot of CX20722, first shut down all EAPDs, then
 shut down the afg node to D3.

 Failure to do so can lead to spurious noises from the internal speaker
 directly after reboot (and before the codec is reinitialized again, i e
 in BIOS setup or GRUB menus).

 BugLink: https://bugs.launchpad.net/bugs/1487345
 Signed-off-by: David Henningsson david.hennings...@canonical.com

 It's worth for stable, right?

Right, just forgot it.



 Takashi

 ---
   sound/pci/hda/patch_conexant.c | 23 ++-
   1 file changed, 22 insertions(+), 1 deletion(-)

 diff --git a/sound/pci/hda/patch_conexant.c b/sound/pci/hda/patch_conexant.c
 index f788a91..ca03c40 100644
 --- a/sound/pci/hda/patch_conexant.c
 +++ b/sound/pci/hda/patch_conexant.c
 @@ -200,12 +200,33 @@ static int cx_auto_init(struct hda_codec *codec)
  return 0;
   }

 -#define cx_auto_freesnd_hda_gen_free
 +static void cx_auto_reboot_notify(struct hda_codec *codec)
 +{
 +struct conexant_spec *spec = codec-spec;
 +
 +if (codec-core.vendor_id != 0x14f150f2)
 +return;
 +
 +/* Turn the CX20722 codec into D3 to avoid spurious noises
 +   from the internal speaker during (and after) reboot */
 +cx_auto_turn_eapd(codec, spec-num_eapds, spec-eapds, false);
 +
 +snd_hda_codec_set_power_to_all(codec, codec-core.afg, AC_PWRST_D3);
 +snd_hda_codec_write(codec, codec-core.afg, 0,
 +AC_VERB_SET_POWER_STATE, AC_PWRST_D3);
 +}
 +
 +static void cx_auto_free(struct hda_codec *codec)
 +{
 +cx_auto_reboot_notify(codec);
 +snd_hda_gen_free(codec);
 +}

   static const struct hda_codec_ops cx_auto_patch_ops = {
  .build_controls = cx_auto_build_controls,
  .build_pcms = snd_hda_gen_build_pcms,
  .init = cx_auto_init,
 +.reboot_notify = cx_auto_reboot_notify,
  .free = cx_auto_free,
  .unsol_event = snd_hda_jack_unsol_event,
   #ifdef CONFIG_PM
 --
 1.9.1



-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

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

Title:
  Noises from CX20722 codec after reboot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is meant for tracking purposes. Please do not triage.

  On shutdown/reboot of CX20722, first shut down all EAPDs, then
  shut down the afg node to D3.

  Failure to do so can lead to spurious noises from the internal speaker
  directly after reboot (and before the codec is reinitialized again, such as 
in BIOS setup or GRUB menus).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1487345/+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 1477900] Re: Headset mic support for a Dell desktop machine

[David Henningsson]

Woodrow, did we ever get a quirk in for this one or not?

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

Title:
  Headset mic support for a Dell desktop machine

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

Bug description:
  When the headset was plugged in the Dell desktop, the mic of headset
  can't be detected and workable.

  Codec: Realtek ALC3234
  Vendor Id: 0x10ec0255
  Subsystem Id: 0x102806bb

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1477900/+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 1476987] [NEW] Headset mic support for a Dell machine

[David Henningsson]

Public bug reported:

This bug is used for tracking only, please do not triage.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New = In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

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

Title:
  Headset mic support for a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1476987/+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 1476987] Re: Headset mic support for a Dell machine

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Headset mic support for a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is used for tracking only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1476987/+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 1476987] [PATCH] ALSA: hda - Add headset mic pin quirk for a Dell device

[David Henningsson]

Without this patch, the headset mic will not work on this machine.

BugLink: https://bugs.launchpad.net/bugs/1476987
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_realtek.c | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index caba66b..11c8a74 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5463,6 +5463,17 @@ static const struct snd_hda_pin_quirk 
alc269_pin_fixup_tbl[] = {
{0x1d, 0x4071},
{0x21, 0x02211030}),
SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell, 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
+   {0x12, 0x4000},
+   {0x14, 0x90170130},
+   {0x17, 0x41f0},
+   {0x18, 0x41f0},
+   {0x19, 0x41f0},
+   {0x1a, 0x41f0},
+   {0x1b, 0x01014020},
+   {0x1d, 0x4054c029},
+   {0x1e, 0x41f0},
+   {0x21, 0x0221103f}),
+   SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell, 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
{0x12, 0x90a60160},
{0x14, 0x90170120},
{0x17, 0x90170140},
-- 
1.9.1

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

Title:
  Headset mic support for a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1476987/+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 1454975] Re: AMD Radeon HD 8570 / R7 240/340 OEM] [1002:6611] No DP audio with the open source driver

[David Henningsson]

** Changed in: hwe-next
   Status: New = Incomplete

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

Title:
  AMD Radeon HD 8570 / R7 240/340 OEM] [1002:6611] No DP audio with the
  open source driver

Status in HWE Next Project:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  CID: 201302-12679 Dell OptiPlex 9020

  There is no audio output available from the DisplayPort with the open source 
driver.
  There are two output options here in the Sound Settings: Analog Output and 
Speaker
  Non of them could make the DP audio device (the speaker on the monitor) work.

  Also, this is a desktop system, I can't hear anything with the Speaker
  option.

  Since we're unable to install the fglrx now, I will mark this one as a
  blocker.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-37-generic 3.16.0-37.51~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 13 23:52:37 2015
  InstallationDate: Installed on 2015-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1697 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1697 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=9201b911-af8a-4fe9-a8b1-544f1f394b6a
  InstallationDate: Installed on 2015-05-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9020
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic 
root=UUID=9d6f549c-046c-4193-b58e-5ee4df6c0e0b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-37-generic N/A
   linux-backports-modules-3.16.0-37-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.16.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454975/+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 1446517] Re: num_steps = 0 error on ALC256

[David Henningsson]

Comes from upstream stable, does not need verification.

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

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

Title:
  num_steps = 0 error on ALC256

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This bug is used for tracking, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446517/+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 1454235] Re: [PATCH] ALSA: hda - Disable Headphone Mic boost for ALC662

[David Henningsson]

On 2015-05-28 09:18, Takashi Iwai wrote:
 At Thu, 28 May 2015 09:15:46 +0200,
 David Henningsson wrote:

 When headphone mic boost is above zero, some 10 - 20 second delay
 might occur before the headphone mic is operational.
 Therefore disable the headphone mic boost control (recording gain is
 sufficient even without it).

 (Note: this patch is not about the headset mic, it's about the less
 common mic-in only mode.)

 BugLink: https://bugs.launchpad.net/bugs/1454235
 Suggested-by: Kailang Yang kail...@realtek.com
 Signed-off-by: David Henningsson david.hennings...@canonical.com
 ---
   sound/pci/hda/patch_realtek.c | 4 
   1 file changed, 4 insertions(+)

 diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
 index d0fa455..87605fc 100644
 --- a/sound/pci/hda/patch_realtek.c
 +++ b/sound/pci/hda/patch_realtek.c
 @@ -4240,6 +4240,10 @@ static void alc_fixup_headset_mode_alc662(struct 
 hda_codec *codec,
  if (action == HDA_FIXUP_ACT_PRE_PROBE) {
  spec-parse_flags |= HDA_PINCFG_HEADSET_MIC;
  spec-gen.hp_mic = 1; /* Mic-in is same pin as headphone */
 +
 +/* Disable boost for mic-in permanently */
 +snd_hda_codec_write(codec, 0x1b, 0, AC_VERB_SET_AMP_GAIN_MUTE, 
 0x7000);
 +snd_hda_override_wcaps(codec, 0x1b, get_wcaps(codec, 0x1b)  
 ~AC_WCAP_IN_AMP);

 Can we really hard-code NID 0x1b here...?

alc_fixup_headset_mode_alc662 is currently only called from a pin fixup 
quirk (via ALC662_FIXUP_DELL_MIC_NO_PRESENCE), and that pin quirk has 
headphone at 0x1b, so yes.

It would we better if we could make it more generic, but I think doing 
this at HDA_FIXUP_PROBE instead would be too late (the boost control, 
paths, etc, would already be created)...?

Do you have a better suggestion?

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

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

Title:
  Fix headset jack on two Dell machines

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454235/+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 1454235] [PATCH] ALSA: hda - Disable Headphone Mic boost for ALC662

[David Henningsson]

When headphone mic boost is above zero, some 10 - 20 second delay
might occur before the headphone mic is operational.
Therefore disable the headphone mic boost control (recording gain is
sufficient even without it).

(Note: this patch is not about the headset mic, it's about the less
common mic-in only mode.)

BugLink: https://bugs.launchpad.net/bugs/1454235
Suggested-by: Kailang Yang kail...@realtek.com
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_realtek.c | 5 +
 1 file changed, 5 insertions(+)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index d0fa455..da2d371 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -4240,6 +4240,11 @@ static void alc_fixup_headset_mode_alc662(struct 
hda_codec *codec,
if (action == HDA_FIXUP_ACT_PRE_PROBE) {
spec-parse_flags |= HDA_PINCFG_HEADSET_MIC;
spec-gen.hp_mic = 1; /* Mic-in is same pin as headphone */
+
+   /* Disable boost for mic-in permanently. (This code is only 
called
+  from quirks that guarantee that the headphone is at NID 
0x1b.) */
+   snd_hda_codec_write(codec, 0x1b, 0, AC_VERB_SET_AMP_GAIN_MUTE, 
0x7000);
+   snd_hda_override_wcaps(codec, 0x1b, get_wcaps(codec, 0x1b)  
~AC_WCAP_IN_AMP);
} else
alc_fixup_headset_mode(codec, fix, action);
 }
-- 
1.9.1

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

Title:
  Fix headset jack on two Dell machines

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454235/+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 1454235] Re: Fix headset jack on two Dell machines

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Fix headset jack on two Dell machines

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454235/+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 1454656] Re: Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  These codecs can be trivially supported by adding the relevant id:s to
  the right tables.

  X-HWE-Bug: Bug #1446932

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454656/+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 1454656] [PATCH] ALSA: hda - Add Conexant codecs CX20721, CX20722, CX20723 and CX20724

[David Henningsson]

This patch adds support for Conexant HD Audio codecs
CX20721, CX20722, CX20723 and CX20724.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1454656
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_conexant.c | 12 
 1 file changed, 12 insertions(+)

diff --git a/sound/pci/hda/patch_conexant.c b/sound/pci/hda/patch_conexant.c
index f8f0dfb..78b719b 100644
--- a/sound/pci/hda/patch_conexant.c
+++ b/sound/pci/hda/patch_conexant.c
@@ -968,6 +968,14 @@ static const struct hda_codec_preset 
snd_hda_preset_conexant[] = {
  .patch = patch_conexant_auto },
{ .id = 0x14f150b9, .name = CX20665,
  .patch = patch_conexant_auto },
+   { .id = 0x14f150f1, .name = CX20721,
+ .patch = patch_conexant_auto },
+   { .id = 0x14f150f2, .name = CX20722,
+ .patch = patch_conexant_auto },
+   { .id = 0x14f150f3, .name = CX20723,
+ .patch = patch_conexant_auto },
+   { .id = 0x14f150f4, .name = CX20724,
+ .patch = patch_conexant_auto },
{ .id = 0x14f1510f, .name = CX20751/2,
  .patch = patch_conexant_auto },
{ .id = 0x14f15110, .name = CX20751/2,
@@ -1002,6 +1010,10 @@ MODULE_ALIAS(snd-hda-codec-id:14f150ab);
 MODULE_ALIAS(snd-hda-codec-id:14f150ac);
 MODULE_ALIAS(snd-hda-codec-id:14f150b8);
 MODULE_ALIAS(snd-hda-codec-id:14f150b9);
+MODULE_ALIAS(snd-hda-codec-id:14f150f1);
+MODULE_ALIAS(snd-hda-codec-id:14f150f2);
+MODULE_ALIAS(snd-hda-codec-id:14f150f3);
+MODULE_ALIAS(snd-hda-codec-id:14f150f4);
 MODULE_ALIAS(snd-hda-codec-id:14f1510f);
 MODULE_ALIAS(snd-hda-codec-id:14f15110);
 MODULE_ALIAS(snd-hda-codec-id:14f15111);
-- 
1.9.1

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

Title:
  Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  These codecs can be trivially supported by adding the relevant id:s to
  the right tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454656/+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 1454656] [NEW] Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724

[David Henningsson]

Public bug reported:

These codecs can be trivially supported by adding the relevant id:s to
the right tables.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New = In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

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

Title:
  Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  These codecs can be trivially supported by adding the relevant id:s to
  the right tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454656/+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 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[David Henningsson]

JFTR, it seems that upstream has agreed to revert the _REV change for
4.1, and develop a quirk system for 4.2 that would enable us to stay on
HDA mode for as many kernels as we like:

http://mailman.alsa-project.org/pipermail/alsa-
devel/2015-May/091958.html

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

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Invalid
Status in HWE Next Project:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of Windows 2013, I2S mode is used for audio.

  A workaround is to pass acpi_os=!Windows 2013 as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep (audio|snd|INT3438)
  dmar: ACPI device INT3438:00 under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( - 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+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 1454235] [NEW] Fix headset jack on two Dell machines

[David Henningsson]

Public bug reported:

This bug is for tracking purposes. Please do not triage.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New = In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

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

Title:
  Fix headset jack on two Dell machines

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is for tracking purposes. Please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1454235/+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 1454235] [PATCH] ALSA: hda - Fix headset mic and mic-in for a Dell desktop

[David Henningsson]

ALC662 does not need any special verbs to change the jack functionality,
and enables mic in through the headphone jack mode by changing the
direction of the headphone pin node.

BugLink: https://bugs.launchpad.net/bugs/1454235
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_realtek.c | 46 ++-
 1 file changed, 45 insertions(+), 1 deletion(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index ce41271..30ec30f 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -3674,6 +3674,10 @@ static void alc_headset_mode_mic_in(struct hda_codec 
*codec, hda_nid_t hp_pin,
alc_process_coef_fw(codec, coef0293);
snd_hda_set_pin_ctl_cache(codec, mic_pin, PIN_VREF50);
break;
+   case 0x10ec0662:
+   snd_hda_set_pin_ctl_cache(codec, hp_pin, 0);
+   snd_hda_set_pin_ctl_cache(codec, mic_pin, PIN_VREF50);
+   break;
case 0x10ec0668:
alc_write_coef_idx(codec, 0x11, 0x0001);
snd_hda_set_pin_ctl_cache(codec, hp_pin, 0);
@@ -4012,7 +4016,7 @@ static void alc_update_headset_mode(struct hda_codec 
*codec)
if (new_headset_mode != ALC_HEADSET_MODE_MIC) {
snd_hda_set_pin_ctl_cache(codec, hp_pin,
  AC_PINCTL_OUT_EN | AC_PINCTL_HP_EN);
-   if (spec-headphone_mic_pin)
+   if (spec-headphone_mic_pin  spec-headphone_mic_pin != 
hp_pin)
snd_hda_set_pin_ctl_cache(codec, 
spec-headphone_mic_pin,
  PIN_VREFHIZ);
}
@@ -4215,6 +4219,18 @@ static void alc_fixup_dell_xps13(struct hda_codec *codec,
}
 }
 
+static void alc_fixup_headset_mode_alc662(struct hda_codec *codec,
+   const struct hda_fixup *fix, int action)
+{
+   struct alc_spec *spec = codec-spec;
+
+   if (action == HDA_FIXUP_ACT_PRE_PROBE) {
+   spec-parse_flags |= HDA_PINCFG_HEADSET_MIC;
+   spec-gen.hp_mic = 1; /* Mic-in is same pin as headphone */
+   } else
+   alc_fixup_headset_mode(codec, fix, action);
+}
+
 static void alc_fixup_headset_mode_alc668(struct hda_codec *codec,
const struct hda_fixup *fix, int action)
 {
@@ -6080,7 +6096,9 @@ enum {
ALC662_FIXUP_NO_JACK_DETECT,
ALC662_FIXUP_ZOTAC_Z68,
ALC662_FIXUP_INV_DMIC,
+   ALC662_FIXUP_DELL_MIC_NO_PRESENCE,
ALC668_FIXUP_DELL_MIC_NO_PRESENCE,
+   ALC662_FIXUP_HEADSET_MODE,
ALC668_FIXUP_HEADSET_MODE,
ALC662_FIXUP_BASS_MODE4_CHMAP,
ALC662_FIXUP_BASS_16,
@@ -6273,6 +6291,20 @@ static const struct hda_fixup alc662_fixups[] = {
.chained = true,
.chain_id = ALC668_FIXUP_DELL_MIC_NO_PRESENCE
},
+   [ALC662_FIXUP_DELL_MIC_NO_PRESENCE] = {
+   .type = HDA_FIXUP_PINS,
+   .v.pins = (const struct hda_pintbl[]) {
+   { 0x19, 0x03a1113c }, /* use as headset mic, without 
its own jack detect */
+   /* headphone mic by setting pin control of 0x1b 
(headphone out) to in + vref_50 */
+   { }
+   },
+   .chained = true,
+   .chain_id = ALC662_FIXUP_HEADSET_MODE
+   },
+   [ALC662_FIXUP_HEADSET_MODE] = {
+   .type = HDA_FIXUP_FUNC,
+   .v.func = alc_fixup_headset_mode_alc662,
+   },
[ALC668_FIXUP_DELL_MIC_NO_PRESENCE] = {
.type = HDA_FIXUP_PINS,
.v.pins = (const struct hda_pintbl[]) {
@@ -6432,6 +6464,18 @@ static const struct hda_model_fixup 
alc662_fixup_models[] = {
{0x1f, 0x41f0}
 
 static const struct snd_hda_pin_quirk alc662_pin_fixup_tbl[] = {
+   SND_HDA_PIN_QUIRK(0x10ec0662, 0x1028, Dell, 
ALC662_FIXUP_DELL_MIC_NO_PRESENCE,
+   {0x12, 0x4004c000},
+   {0x14, 0x01014010},
+   {0x15, 0x41f0},
+   {0x16, 0x41f0},
+   {0x18, 0x01a19020},
+   {0x19, 0x41f0},
+   {0x1a, 0x0181302f},
+   {0x1b, 0x0221401f},
+   {0x1c, 0x41f0},
+   {0x1d, 0x4054c601},
+   {0x1e, 0x41f0}),
SND_HDA_PIN_QUIRK(0x10ec0668, 0x1028, Dell, ALC668_FIXUP_AUTO_MUTE,
ALC668_STANDARD_PINS,
{0x12, 0x99a30130},
-- 
1.9.1

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

Title:
  Fix headset jack on two Dell machines

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is for tracking purposes. Please do not triage.

To manage notifications about this bug go

[Kernel-packages] [Bug 1452175] [PATCH] ALSA: hda - Add headset mic quirk for Dell Inspiron 5548

[David Henningsson]

This enables the headset microphone on Dell Inspiron 5548,
or at least some variants of it.

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1452175
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_realtek.c | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 4a0a238..37c2c9f 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5346,6 +5346,13 @@ static const struct snd_hda_pin_quirk 
alc269_pin_fixup_tbl[] = {
{0x17, 0x4000},
{0x1d, 0x4071},
{0x21, 0x02211050}),
+   SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell Inspiron 5548, 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
+   ALC255_STANDARD_PINS,
+   {0x12, 0x90a60180},
+   {0x14, 0x90170130},
+   {0x17, 0x4000},
+   {0x1d, 0x4071},
+   {0x21, 0x02211040}),
SND_HDA_PIN_QUIRK(0x10ec0256, 0x1028, Dell, 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC256_STANDARD_PINS,
{0x13, 0x4000}),
-- 
1.9.1

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

Title:
  Add headset mic some variants of Dell Inspiron 5548

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1452175/+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 1452175] Re: Add headset mic some variants of Dell Inspiron 5548

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Add headset mic some variants of Dell Inspiron 5548

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1452175/+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 1452175] [PATCH] ALSA: hda - Add headset mic quirk for Dell Inspiron 5548

[David Henningsson]

This enables the headset microphone on Dell Inspiron 5548,
or at least some variants of it.

Cc: sta...@kernel.org
BugLink: https://bugs.launchpad.net/bugs/1452175
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_realtek.c | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 06199e4..c5413e9 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5337,6 +5337,13 @@ static const struct snd_hda_pin_quirk 
alc269_pin_fixup_tbl[] = {
{0x17, 0x4000},
{0x1d, 0x4071},
{0x21, 0x02211050}),
+   SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell Inspiron 5548, 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
+   ALC255_STANDARD_PINS,
+   {0x12, 0x90a60180},
+   {0x14, 0x90170130},
+   {0x17, 0x4000},
+   {0x1d, 0x4071},
+   {0x21, 0x02211040}),
SND_HDA_PIN_QUIRK(0x10ec0256, 0x1028, Dell, 
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC256_STANDARD_PINS,
{0x13, 0x4000}),
-- 
1.9.1

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

Title:
  Add headset mic some variants of Dell Inspiron 5548

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1452175/+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 1452175] [NEW] Add headset mic some variants of Dell Inspiron 5548

[David Henningsson]

Public bug reported:

This bug is used for tracking purposes, please do not triage.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New = In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

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

Title:
  Add headset mic some variants of Dell Inspiron 5548

Status in HWE Next Project:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1452175/+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 1286021] Re: 2.1 surround support (userspace)

[David Henningsson]

** Also affects: alsa-lib (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  2.1 surround support (userspace)

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Trusty:
  New
Status in pulseaudio source package in Trusty:
  New

Bug description:
  2.1 surround should work as seamlessly as other surround options, such
  as 4.0, 5.1 and 7.1 work today.

  Alsa-lib and pulseaudio patches for 14.04 can be tested here:

  https://launchpad.net/~diwic/+archive/surround21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021/+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 1446517] [NEW] num_steps = 0 error on ALC256

[David Henningsson]

Public bug reported:

This bug is used for tracking, please do not triage.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

** Changed in: linux (Ubuntu)
   Status: New = In Progress

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

Title:
  num_steps = 0 error on ALC256

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446517/+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 1446517] [PATCH] ALSA: hda - fix num_steps = 0 error on ALC256

[David Henningsson]

The ALC256 does not have a mixer nid at 0x0b, and there's no
loopback path (the output pins are directly connected to the DACs).

This commit fixes an num_steps = 0 for NID=0xb (ctl = Beep Playback Volume)
error (and as a result, problems with amixer/alsamixer).

If there's pcbeep functionality, it certainly isn't controlled by setting an
amp on 0x0b, so disable beep functionality (at least for now).

Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446517
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
 sound/pci/hda/patch_realtek.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 231d0e4..03975d03 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5664,6 +5664,7 @@ static int patch_alc269(struct hda_codec *codec)
break;
case 0x10ec0256:
spec-codec_variant = ALC269_TYPE_ALC256;
+   spec-gen.mixer_nid = 0; /* ALC256 does not have any loopback 
mixer path */
break;
}
 
@@ -5677,8 +5678,8 @@ static int patch_alc269(struct hda_codec *codec)
if (err  0)
goto error;
 
-   if (!spec-gen.no_analog  spec-gen.beep_nid)
-   set_beep_amp(spec, 0x0b, 0x04, HDA_INPUT);
+   if (!spec-gen.no_analog  spec-gen.beep_nid  spec-gen.mixer_nid)
+   set_beep_amp(spec, spec-gen.mixer_nid, 0x04, HDA_INPUT);
 
codec-patch_ops = alc_patch_ops;
codec-patch_ops.stream_pm = snd_hda_gen_stream_pm;
-- 
1.9.1

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

Title:
  num_steps = 0 error on ALC256

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This bug is used for tracking, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446517/+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 1446517] Re: num_steps = 0 error on ALC256

[David Henningsson]

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  num_steps = 0 error on ALC256

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This bug is used for tracking, please do not triage.

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