[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Phidias]

https://wiki.ubuntu.com/KernelTeam/Newsletter/
My backport has been acked, and according to the news letter, it will be 
applied to Xenial and Yaketty master-next branch no later than Dec 16, and will 
be available in -proposed repo on Dec 25 (Merry Christmas!)

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1571530] Re: Need Alps upstream their new touchpad driver

[Phidias]

** Tags added: xenial

** Tags added: yakkety

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

Title:
  Need Alps upstream their new touchpad driver

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

Bug description:
  Some newer Alps touchpad isn't supported by current kernel therefore
  recognized as PS/2 mouse  and lost some key functions.

  From debug message we saw:
  alps_rpt_cmd: psmouse serio1: alps: E6 report: 00 00 64
  alps_rpt_cmd: psmouse serio1: alps: E7 report: 73 03 28
  alps_rpt_cmd: psmouse serio1: alps: EC report: 73 01 13
  alps_identify: psmouse serio1: alps: Likely not an ALPS touchpad: E7=73 03 
28, EC=73 01 13

  which is different with some Alps bugs reported before.

  Though we've already got drivers from Alps but it's not yet
  upstreamed, this bug is opened for tracking this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1571530/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Phidias]

I've backport the driver to Xenial and gonna send the patch set shortly,
hopefully it will be available in next kernel release.

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1641874] Re: Cursor doesn't move after multitouch on alps touchpad

[Phidias]

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

** This bug has been marked a duplicate of bug 1633321
   Fix alps driver for multitouch function.

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

Title:
  Cursor doesn't move after multitouch on alps touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  hid-alps has a bug which cause the issue after multitouch. In some
  cases it may also happened after closing lid (which triggers
  multitouch).

  There's already a fix in upstream and need to backport to Xenial and
  Yakkety:

  commit 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6
  Author: Masaki Ota <012ne...@gmail.com>
  Date:   Tue Sep 27 14:04:37 2016 +0900

  HID: alps: fix multitouch cursor issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1641874/+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 1632578] Re: Add support for KabeLake i219-LOM chips

[Phidias]

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

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

Title:
  Add support for KabeLake i219-LOM chips

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  There's a commit add device ids to support new i219 Lan-on-
  motherboard:

  commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
  e1000e: Initial support for KabeLake

  [Impact]

  Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
  [8086:15d8]. This patch only add device ids so no further regressions
  are expected.

  [Test]

  Though the commit log says it's "Initial support", but it's been
  successfully tested on multiple platforms and no further issues are
  spotted, so at the moment no further patches are needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1632578/+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 1643797] [NEW] System stalls when creating device node on booting

[Phidias]

Public bug reported:

We've found on some Apollo Lake system stalls for around 4 seconds on
function `wait_for_completion` when creating nodes in devtmpfs. With 70+
nodes created it can be stalled for 5+ minutes when booting.

With bisecting we've found the patch can fix this issue:

commit 0905f04eb21fc1c2e690bed5d0418a061d56c225
Author: Yuyang Du <yuyang...@intel.com>
AuthorDate: Thu Dec 17 07:34:27 2015 +0800
Commit: Ingo Molnar <mi...@kernel.org>
CommitDate: Wed Jan 6 11:06:29 2016 +0100

sched/fair: Fix new task's load avg removed from source CPU in
wake_up_new_task()

This patch can be clean picked, and shows positive result on multiple
Apollo Lake system. The patch is already in v4.5+ so Yakkety is not
affected.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
     Assignee: Phidias (phidias-chiang)
 Status: Incomplete


** Tags: originate-from-1610089 somerville xenial

** Tags added: originate-from-1610089 somerville

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

Title:
  System stalls when creating device node on booting

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

Bug description:
  We've found on some Apollo Lake system stalls for around 4 seconds on
  function `wait_for_completion` when creating nodes in devtmpfs. With
  70+ nodes created it can be stalled for 5+ minutes when booting.

  With bisecting we've found the patch can fix this issue:

  commit 0905f04eb21fc1c2e690bed5d0418a061d56c225
  Author: Yuyang Du <yuyang...@intel.com>
  AuthorDate: Thu Dec 17 07:34:27 2015 +0800
  Commit: Ingo Molnar <mi...@kernel.org>
  CommitDate: Wed Jan 6 11:06:29 2016 +0100

  sched/fair: Fix new task's load avg removed from source CPU in
  wake_up_new_task()

  This patch can be clean picked, and shows positive result on multiple
  Apollo Lake system. The patch is already in v4.5+ so Yakkety is not
  affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1643797/+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 1620979] Re: Hotkey doesn't work on HP x360

[Phidias]

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

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

Title:
  Hotkey doesn't work on HP x360

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When pinctrl-cherryview probing gpio device it clear interrupt mask and 
status, and in the later procedures the interrupt mask isn't set back 
correctly, leads to hotkeys fail.

  [Fix]
  Upstream fixes this in 4.8-rc3 by not clearing interrupt masks:

  commit bcb48cca23ec9852739e4a464307fa29515bbe48
  Author: Mika Westerberg 
  Date:   Mon Aug 22 14:42:52 2016 +0300

  pinctrl: cherryview: Do not mask all interrupts in probe

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1620979/+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 1641874] Re: Cursor doesn't move after multitouch on alps touchpad

[Phidias]

** Tags added: originate-from-1637414 somerville

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

Title:
  Cursor doesn't move after multitouch on alps touchpad

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

Bug description:
  hid-alps has a bug which cause the issue after multitouch. In some
  cases it may also happened after closing lid (which triggers
  multitouch).

  There's already a fix in upstream and need to backport to Xenial and
  Yakkety:

  commit 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6
  Author: Masaki Ota <012ne...@gmail.com>
  Date:   Tue Sep 27 14:04:37 2016 +0900

  HID: alps: fix multitouch cursor issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1641874/+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 1641874] [NEW] Cursor doesn't move after multitouch on alps touchpad

[Phidias]

Public bug reported:

hid-alps has a bug which cause the issue after multitouch. In some cases
it may also happened after closing lid (which triggers multitouch).

There's already a fix in upstream and need to backport to Xenial and
Yakkety:

commit 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6
Author: Masaki Ota <012ne...@gmail.com>
Date:   Tue Sep 27 14:04:37 2016 +0900

HID: alps: fix multitouch cursor issue

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: Incomplete


** Tags: originate-from-1637414 somerville xenial yakkety

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

Title:
  Cursor doesn't move after multitouch on alps touchpad

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

Bug description:
  hid-alps has a bug which cause the issue after multitouch. In some
  cases it may also happened after closing lid (which triggers
  multitouch).

  There's already a fix in upstream and need to backport to Xenial and
  Yakkety:

  commit 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6
  Author: Masaki Ota <012ne...@gmail.com>
  Date:   Tue Sep 27 14:04:37 2016 +0900

  HID: alps: fix multitouch cursor issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1641874/+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 1620979] Re: Hotkey doesn't work on HP x360

[Phidias]

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1620979

Title:
  Hotkey doesn't work on HP x360

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

Bug description:
  [Impact]
  When pinctrl-cherryview probing gpio device it clear interrupt mask and 
status, and in the later procedures the interrupt mask isn't set back 
correctly, leads to hotkeys fail.

  [Fix]
  Upstream fixes this in 4.8-rc3 by not clearing interrupt masks:

  commit bcb48cca23ec9852739e4a464307fa29515bbe48
  Author: Mika Westerberg 
  Date:   Mon Aug 22 14:42:52 2016 +0300

  pinctrl: cherryview: Do not mask all interrupts in probe

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1620979/+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 1632578] Re: Add support for KabeLake i219-LOM chips

[Phidias]

** Tags added: originate-from-1596773 somerville

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

Title:
  Add support for KabeLake i219-LOM chips

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

Bug description:
  There's a commit add device ids to support new i219 Lan-on-
  motherboard:

  commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
  e1000e: Initial support for KabeLake

  [Impact]

  Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
  [8086:15d8]. This patch only add device ids so no further regressions
  are expected.

  [Test]

  Though the commit log says it's "Initial support", but it's been
  successfully tested on multiple platforms and no further issues are
  spotted, so at the moment no further patches are needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1632578/+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 1632578] [NEW] Add support for KabeLake i219-LOM chips

[Phidias]

Public bug reported:

There's a commit add device ids to support new i219 Lan-on-motherboard:

commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
e1000e: Initial support for KabeLake

[Impact]

Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
[8086:15d8]. This patch only add device ids so no further regressions
are expected.

[Test]

Though the commit log says it's "Initial support", but it's been
successfully tested on multiple platforms and no further issues are
spotted, so at the moment no further patches are needed.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1632578

Title:
  Add support for KabeLake i219-LOM chips

Status in linux package in Ubuntu:
  New

Bug description:
  There's a commit add device ids to support new i219 Lan-on-
  motherboard:

  commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
  e1000e: Initial support for KabeLake

  [Impact]

  Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
  [8086:15d8]. This patch only add device ids so no further regressions
  are expected.

  [Test]

  Though the commit log says it's "Initial support", but it's been
  successfully tested on multiple platforms and no further issues are
  spotted, so at the moment no further patches are needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632578/+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 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

[Phidias]

linux-firmware on Xenial has been verified, it works well
linux-firmware: 1.157.4

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

Status in HWE Next:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Released

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1589905/+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 1622469] Re: New device ID for Kabypoint

[Phidias]

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

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

Title:
  New device ID for Kabypoint

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Intel has some new Kaby Lake platforms come with new Kaybpoint PCH,
  and need to backport the support to Xenial release.

  Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs 
following two patches:
  https://lkml.org/lkml/2016/7/4/403
  http://marc.info/?l=linux-i2c=146945783426903=2

  These patches only add some pid specific codes and it won't cause any
  regression in my opinion, so I think it's ok to backport them in
  advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1622469/+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 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

[Phidias]

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

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

Status in HWE Next:
  Triaged
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1589905/+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 1622469] Re: New device ID for Kabypoint

[Phidias]

** Tags added: intel originate-from-1591618

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

Title:
  New device ID for Kabypoint

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

Bug description:
  Intel has some new Kaby Lake platforms come with new Kaybpoint PCH,
  and need to backport the support to Xenial release.

  Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs 
following two patches:
  https://lkml.org/lkml/2016/7/4/403
  http://marc.info/?l=linux-i2c=146945783426903=2

  These patches only add some pid specific codes and it won't cause any
  regression in my opinion, so I think it's ok to backport them in
  advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1622469/+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 1622469] [NEW] New device ID for Kabypoint

[Phidias]

Public bug reported:

Intel has some new Kaby Lake platforms come with new Kaybpoint PCH, and
need to backport the support to Xenial release.

Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs 
following two patches:
https://lkml.org/lkml/2016/7/4/403
http://marc.info/?l=linux-i2c=146945783426903=2

These patches only add some pid specific codes and it won't cause any
regression in my opinion, so I think it's ok to backport them in
advance.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1622469

Title:
  New device ID for Kabypoint

Status in linux package in Ubuntu:
  New

Bug description:
  Intel has some new Kaby Lake platforms come with new Kaybpoint PCH,
  and need to backport the support to Xenial release.

  Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs 
following two patches:
  https://lkml.org/lkml/2016/7/4/403
  http://marc.info/?l=linux-i2c=146945783426903=2

  These patches only add some pid specific codes and it won't cause any
  regression in my opinion, so I think it's ok to backport them in
  advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622469/+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 1620979] [NEW] Hotkey doesn't work on HP x360

[Phidias]

Public bug reported:

[Impact]
When pinctrl-cherryview probing gpio device it clear interrupt mask and status, 
and in the later procedures the interrupt mask isn't set back correctly, leads 
to hotkeys fail.

[Fix]
Upstream fixes this in 4.8-rc3 by not clearing interrupt masks:

commit bcb48cca23ec9852739e4a464307fa29515bbe48
Author: Mika Westerberg <mika.westerb...@linux.intel.com>
Date:   Mon Aug 22 14:42:52 2016 +0300

pinctrl: cherryview: Do not mask all interrupts in probe

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: originate-from-1501600 stella xenial

** Tags added: originate-from-1501600 stella

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

Title:
  Hotkey doesn't work on HP x360

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

Bug description:
  [Impact]
  When pinctrl-cherryview probing gpio device it clear interrupt mask and 
status, and in the later procedures the interrupt mask isn't set back 
correctly, leads to hotkeys fail.

  [Fix]
  Upstream fixes this in 4.8-rc3 by not clearing interrupt masks:

  commit bcb48cca23ec9852739e4a464307fa29515bbe48
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date:   Mon Aug 22 14:42:52 2016 +0300

  pinctrl: cherryview: Do not mask all interrupts in probe

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1620979/+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 1616763] Re: System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]

[Phidias]

** Tags added: originate-from-1613555 somerville

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

Title:
  System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]

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

Bug description:
  Intel 8260 BT module can't pair to BT 4.0 keyboard or mouse. There's
  already a new firmware to fix this issue and has passed our test:

  commit a4bbc8112cc04fcc0e0861e8b72197b6cb83ab83
  Author: Tedd Ho-Jeong An 
  Date: Wed Jun 8 12:53:26 2016 -0700

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616763/+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 1616763] [NEW] System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]

[Phidias]

Public bug reported:

Intel 8260 BT module can't pair to BT 4.0 keyboard or mouse. There's
already a new firmware to fix this issue and has passed our test:

commit a4bbc8112cc04fcc0e0861e8b72197b6cb83ab83
Author: Tedd Ho-Jeong An <tedd...@intel.com>
Date: Wed Jun 8 12:53:26 2016 -0700

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: xenial

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

Title:
  System can't pair to bluetooth 4.0 keyboard/mouse [Intel 8260]

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Intel 8260 BT module can't pair to BT 4.0 keyboard or mouse. There's
  already a new firmware to fix this issue and has passed our test:

  commit a4bbc8112cc04fcc0e0861e8b72197b6cb83ab83
  Author: Tedd Ho-Jeong An <tedd...@intel.com>
  Date: Wed Jun 8 12:53:26 2016 -0700

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1616763/+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 1599071] Re: Add Intel 8265 Bluetooth firmware

[Phidias]

** Tags added: verification-done

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

Title:
  Add Intel 8265 Bluetooth firmware

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Intel 8265 Bluetooth kernel driver support will be added to Xenial and
  it also needs firmware not yet being merged into the package

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599071/+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 1599379] Re: Baytrail-I got black screen with HDMI output

[Phidias]

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

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

Title:
  Baytrail-I got black screen with HDMI output

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  Although the commit fff7660 fixes the issue, it still misses to probe
  HDMI port in some circumstance, therefore there's another commit
  (already merged):

  commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
  Author: Ville Syrjälä 
  CommitDate: Fri Jun 10 10:40:54 2016 +0300

  drm/i915: Check VBT for port presence in addition to the strap on
  VLV/CHV

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599379/+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 1593124] Re: Add proper palm detection support for MS Precision Touchpad

[Phidias]

@Seth,

I was waiting for pauljohn's feedback and now it looks actually fix the
problem so I'll change it to done, thanks :)

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

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

Title:
  Add proper  palm detection support for MS Precision Touchpad

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  The maintainer has provided a patch set to fix this issue and add
  proper palm detection support and the patch set has been merged. We
  also need to introduce this feature to Vivid at OEM's demands.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1599068] Re: Add support for Intel 8265 Bluetooth ([8087:0A2B])

[Phidias]

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

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

Title:
  Add support for Intel 8265 Bluetooth ([8087:0A2B])

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Backport supports for Intel 8265 Bluetooth from upstream

  The support is introduced in v4.7 so yakkety doesn't need this
  backport

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599068/+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 1593124] Re: Add proper palm detection support for MS Precision Touchpad

[Phidias]

@pauljohn:

I also tested on Precision 5510 with 4.4.0-34 after re-installing the
system, can't reproduce the issue. I also set PalmDetect to 1 (default
is 0), can't reproduce the issue either.

Don't think BIOS version affects this issue but can you provide the
information with `sudo dmidecode -s bios-version`? FYI we're using
01.02.10.

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

Title:
  Add proper  palm detection support for MS Precision Touchpad

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  The maintainer has provided a patch set to fix this issue and add
  proper palm detection support and the patch set has been merged. We
  also need to introduce this feature to Vivid at OEM's demands.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1606147] Re: [APL][SAUCE] Slow system response time due to a monitor bug

[Phidias]

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

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

Title:
  [APL][SAUCE] Slow system response time due to a monitor bug

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  We've found a bug on some Apollo Lake system makes it runs very slow.
  From upstream it is caused by following reason:

  "Monitored cached line may not wake up from mwait on certain Goldmont
  based CPUs. This patch will avoid calling
  current_set_polling_and_test() and thereby not set the TIF_ flag. The
  result is that we'll always send IPIs for wakeups."

  [Fix]

  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.

  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:

  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen 
  Date:   Thu Jun 2 17:19:27 2016 -0700

  x86/cpu/intel: Introduce macros for Intel family numbers

  This workaround checks CPU families and certain features, so no
  further regressions is expected

  [1]: https://lkml.org/lkml/2016/7/6/469

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1606147/+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 1606129] Re: [i915_bpo][APL][BXT] Add support for new Intel chip [8086:5a84]

[Phidias]

** Summary changed:

- [i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]
+ [i915_bpo][APL][BXT] Add support for new Intel chip [8086:5a84]

** Description changed:

- i915_bpo in Xenial doesn't support BXT graphic in Apollo Lake. We either
- got black screen or hardware acceleration doesn't work. There's a series
- of patches from up to v4.8 kernel need to be backported.
+ i915_bpo in Xenial doesn't support certain graphic chips which already
+ in used for OEM projects. We either got black screen or hardware
+ acceleration doesn't work. There's a series of patches from up to v4.8
+ kernel need to be backported.

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

Title:
  [i915_bpo][APL][BXT] Add support for new Intel chip [8086:5a84]

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

Bug description:
  i915_bpo in Xenial doesn't support certain graphic chips which already
  in used for OEM projects. We either got black screen or hardware
  acceleration doesn't work. There's a series of patches from up to v4.8
  kernel need to be backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1606129/+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 1606129] Re: [i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]

[Phidias]

** Tags added: originate-from-1602502 somerville

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

Title:
  [i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]

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

Bug description:
  i915_bpo in Xenial doesn't support BXT graphic in Apollo Lake. We
  either got black screen or hardware acceleration doesn't work. There's
  a series of patches from up to v4.8 kernel need to be backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1606129/+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 1606147] Re: [APL][SAUCE] System works slowly due to a monitor bug

[Phidias]

** Tags added: originate-from-1582486 somerville

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

Title:
  [APL][SAUCE] System works slowly due to a monitor bug

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

Bug description:
  [Impact]

  We've found a bug on some Apollo Lake system makes it runs very slow.
  From upstream it is caused by following reason:

  "Monitored cached line may not wake up from mwait on certain Goldmont
  based CPUs. This patch will avoid calling
  current_set_polling_and_test() and thereby not set the TIF_ flag. The
  result is that we'll always send IPIs for wakeups."

  [Fix]

  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.

  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:

  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen 
  Date:   Thu Jun 2 17:19:27 2016 -0700

  x86/cpu/intel: Introduce macros for Intel family numbers

  This workaround checks CPU families and certain features, so no
  further regressions is expected

  [1]: https://lkml.org/lkml/2016/7/6/469

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1606147/+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 1606147] Re: [APL][SAUCE] System works slowly due to a monitor bug

[Phidias]

** Description changed:

  [Impact]
  
  We've found a bug on some Apollo Lake system makes it runs very slow.
+ From upstream it is caused by following reason:
+ 
+ "Monitored cached line may not wake up from mwait on certain Goldmont
+ based CPUs. This patch will avoid calling current_set_polling_and_test()
+ and thereby not set the TIF_ flag. The result is that we'll always send
+ IPIs for wakeups."
  
  [Fix]
  
  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.
  
  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:
  
  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen 
  Date:   Thu Jun 2 17:19:27 2016 -0700
  
- x86/cpu/intel: Introduce macros for Intel family numbers
+ x86/cpu/intel: Introduce macros for Intel family numbers
  
  This workaround checks CPU families and certain features, so no further
  regressions is expected
  
  [1]: https://lkml.org/lkml/2016/7/6/469

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

Title:
  [APL][SAUCE] System works slowly due to a monitor bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  We've found a bug on some Apollo Lake system makes it runs very slow.
  From upstream it is caused by following reason:

  "Monitored cached line may not wake up from mwait on certain Goldmont
  based CPUs. This patch will avoid calling
  current_set_polling_and_test() and thereby not set the TIF_ flag. The
  result is that we'll always send IPIs for wakeups."

  [Fix]

  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.

  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:

  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen 
  Date:   Thu Jun 2 17:19:27 2016 -0700

  x86/cpu/intel: Introduce macros for Intel family numbers

  This workaround checks CPU families and certain features, so no
  further regressions is expected

  [1]: https://lkml.org/lkml/2016/7/6/469

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606147/+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 1606147] [NEW] [APL][SAUCE] System works slowly due to a monitor bug

[Phidias]

Public bug reported:

[Impact]

We've found a bug on some Apollo Lake system makes it runs very slow.

[Fix]

Upstream already provided a workaround[1] to fix this problem. This
patches haven't been merged in latest(v4.7) release but already in
linux-next.

To fix this issue in Xenial it also needs another commit introduces
macros use in the workaround:

commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
Author: Dave Hansen <d...@sr71.net>
Date:   Thu Jun 2 17:19:27 2016 -0700

x86/cpu/intel: Introduce macros for Intel family numbers

This workaround checks CPU families and certain features, so no further
regressions is expected

[1]: https://lkml.org/lkml/2016/7/6/469

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1606147

Title:
  [APL][SAUCE] System works slowly due to a monitor bug

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  We've found a bug on some Apollo Lake system makes it runs very slow.

  [Fix]

  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.

  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:

  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen <d...@sr71.net>
  Date:   Thu Jun 2 17:19:27 2016 -0700

  x86/cpu/intel: Introduce macros for Intel family numbers

  This workaround checks CPU families and certain features, so no
  further regressions is expected

  [1]: https://lkml.org/lkml/2016/7/6/469

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606147/+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 1606129] [NEW] [i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]

[Phidias]

Public bug reported:

i915_bpo in Xenial doesn't support BXT graphic in Apollo Lake. We either
got black screen or hardware acceleration doesn't work. There's a series
of patches from up to v4.8 kernel need to be backported.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Incomplete


** Tags: 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/1606129

Title:
  [i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i915_bpo in Xenial doesn't support BXT graphic in Apollo Lake. We
  either got black screen or hardware acceleration doesn't work. There's
  a series of patches from up to v4.8 kernel need to be backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606129/+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 1579984] Re: Dell dock MAC Address pass through doesn't work in Ubuntu

[Phidias]

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1579984

Title:
  Dell dock MAC Address pass through doesn't work in Ubuntu

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Dell systems with Type-C ports support a feature called "MAC address" pass 
through.
  This feature allows systems to set a persistent system MAC address to be used 
with the TB15, WD15 and Type-C ethernet adapter.

  More information is available here:
  http://www.dell.com/support/article/us/en/19/SLN301147/en

  This function works by a system specific MAC address (referred to as
  an auxiliary mac address) being programmed in the factory.  When the
  driver for the type-c ethernet (in dock or dongle) is loaded the MAC
  address is supposed to be overridden with this value.

  To enable this in Linux a kernel patch is needed.
  This has been submitted http://patchwork.ozlabs.org/patch/631759/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984/+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 1599379] Re: Baytrail-I got black screen with HDMI output

[Phidias]

** Description changed:

  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:
  
  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200
  
- drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV
+ drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV
  
  The issue has been reported to upstream [1] and the fix has been merged.
  
+ Although the commit fff7660 fixes the issue, it still misses to probe
+ HDMI port in some circumstance, therefore there's another commit
+ (already merged):
+ 
+ commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
+ Author: Ville Syrjälä 
+ CommitDate: Fri Jun 10 10:40:54 2016 +0300
+ 
+ drm/i915: Check VBT for port presence in addition to the strap on
+ VLV/CHV
+ 
  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

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

Title:
  Baytrail-I got black screen with HDMI output

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

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  Although the commit fff7660 fixes the issue, it still misses to probe
  HDMI port in some circumstance, therefore there's another commit
  (already merged):

  commit a5aac5ab876ad95b7f5e8d862afb07248ee9cae2
  Author: Ville Syrjälä 
  CommitDate: Fri Jun 10 10:40:54 2016 +0300

  drm/i915: Check VBT for port presence in addition to the strap on
  VLV/CHV

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599379/+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 1593124] Re: Add proper palm detection support for MS Precision Touchpad

[Phidias]

** Description changed:

  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't move
  at all (in our cases).
  
  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.
  
  We also contacted with Synaptics, and they provided a workaround to fix
  this issue. Not sure if the workaround will be upstreamed and needs to
  keep co-working with them.
  
  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.
  
+ The maintainer has provided a patch set to fix this issue and add proper
+ palm detection support and the patch set has been merged. We also need
+ to introduce this feature to Vivid at OEM's demands.
+ 
  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

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

Title:
  Add proper  palm detection support for MS Precision Touchpad

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  The maintainer has provided a patch set to fix this issue and add
  proper palm detection support and the patch set has been merged. We
  also need to introduce this feature to Vivid at OEM's demands.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1593124] Re: Add proper palm detection support for MS Precision Touchpad

[Phidias]

** Summary changed:

- Palm rejection for MS Precision Touchpad causes touchpad unusable
+ Add proper  palm detection support for MS Precision Touchpad

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

Title:
  Add proper  palm detection support for MS Precision Touchpad

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  The maintainer has provided a patch set to fix this issue and add
  proper palm detection support and the patch set has been merged. We
  also need to introduce this feature to Vivid at OEM's demands.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1593124] Re: Palm rejection for MS Precision Touchpad causes touchpad unusable

[Phidias]

** No longer affects: hwe-next/yakkety

** Tags added: 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/1593124

Title:
  Palm rejection for MS Precision Touchpad causes touchpad unusable

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1599379] Re: Baytrail-I got black screen with HDMI output

[Phidias]

** Tags added: originate-from-1578953 pre-certification

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

Title:
  Baytrail-I got black screen with HDMI output

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

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä 
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599379/+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 1599379] [NEW] Baytrail-I got black screen with HDMI output

[Phidias]

Public bug reported:

This issue happens with 4.0+ kernels. Bisecting shows following commit
cause the issue:

commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
Author: Ville Syrjälä <ville.syrj...@linux.intel.com>
Date: Fri Jan 9 14:21:14 2015 +0200

drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

The issue has been reported to upstream [1] and the fix has been merged.

[1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: Incomplete


** Tags: originate-from-1578953 pre-certification xenial

** Summary changed:

- Baytrail-T got black screen with HDMI output
+ Baytrail-I got black screen with HDMI output

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

Title:
  Baytrail-I got black screen with HDMI output

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

Bug description:
  This issue happens with 4.0+ kernels. Bisecting shows following commit
  cause the issue:

  commit d2182a660808d9053a605e3ebc8c46a323ec6e5d
  Author: Ville Syrjälä <ville.syrj...@linux.intel.com>
  Date: Fri Jan 9 14:21:14 2015 +0200

  drm/i915: Don't register HDMI connectors for eDP ports on VLV/CHV

  The issue has been reported to upstream [1] and the fix has been
  merged.

  [1]: https://bugs.freedesktop.org/show_bug.cgi?id=96288

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599379/+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 1599068] Re: Add support for Intel 8265 Bluetooth ([8087:0A2B])

[Phidias]

** Summary changed:

- Add support for Intel 8265 Bluetooth ([8087:0A2B])  support
+ Add support for Intel 8265 Bluetooth ([8087:0A2B])

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

Title:
  Add support for Intel 8265 Bluetooth ([8087:0A2B])

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

Bug description:
  Backport supports for Intel 8265 Bluetooth from upstream

  The support is introduced in v4.7 so yakkety doesn't need this
  backport

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599068/+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 1599071] [NEW] Add Intel 8265 Bluetooth firmware

[Phidias]

Public bug reported:

Intel 8265 Bluetooth kernel driver support will be added to Xenial and
it also needs firmware not yet being merged into the package

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

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: originate-from-1572814 somerville xenial

** Tags added: originate-from-1572814 somerville

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

Title:
  Add Intel 8265 Bluetooth firmware

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

Bug description:
  Intel 8265 Bluetooth kernel driver support will be added to Xenial and
  it also needs firmware not yet being merged into the package

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599071/+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 1599068] [NEW] Add support for Intel 8265 Bluetooth ([8087:0A2B]) support

[Phidias]

Public bug reported:

Backport supports for Intel 8265 Bluetooth from upstream

The support is introduced in v4.7 so yakkety doesn't need this backport

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: originate-from-1572814 somerville xenial

** Tags added: originate-from-1572814 somerville

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

Title:
  Add support for Intel 8265 Bluetooth ([8087:0A2B])  support

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

Bug description:
  Backport supports for Intel 8265 Bluetooth from upstream

  The support is introduced in v4.7 so yakkety doesn't need this
  backport

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1599068/+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 1593124] Re: Palm rejection for MS Precision Touchpad causes touchpad unusable

[Phidias]

** Changed in: hwe-next/yakkety
   Status: New => 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/1593124

Title:
  Palm rejection for MS Precision Touchpad causes touchpad unusable

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in HWE Next yakkety series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1484159] Re: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] is not supported

[Phidias]

linux-firmware-1.157.1 is verified with v4.4.0-22 kernel, new linux-
firmware works well

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

Title:
  Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042]
  is not supported

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Yakkety:
  Fix Released

Bug description:
  This card remains unsupported out-of-the-box by the ath10k_pci kernel
  module. At this point, it looks like kvalo's ath10k-firmware repo just
  needs to be pulled in.

  ---

  HOW TO GET THIS CARD TO WORK:

  I don't actually have this card, but AndyP was able to get this card
  to work by following my instructions, so I've written them here in a
  clearer format.

  1) Use a kernel that supports this card

  Support for this card is not present in kernel 4.2.  However, it was
  added at some point between then and kernel 4.4.  If you're running
  Ubuntu 16.04 LTS or above, your kernel is fine; skip to the next step.
  If you're running Ubuntu 15.10 or below, see
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
  newer kernel. Alternatively, you can use backports. This is a lot more
  work, but if you really need to keep using an older kernel for some
  reason, there are some guides to installing backports in the comments
  below.

  2) Get the latest firmware from https://github.com/kvalo/ath10k-
  firmware/archive/master.zip

   wget https://github.com/kvalo/ath10k-firmware/archive/master.zip

  3) Unzip the downloaded file. Inside the ath10k-firmware-master folder
  is a folder named QCA9377. Copy the QCA9377 folder to
  /lib/firmware/ath10k:

  unzip master.zip
  sudo cp -r ath10k-firmware-master/QCA9377/ /lib/firmware/ath10k/

  4) Run the following commands to rename the necessary firmware file:

  cd /lib/firmware/ath10k/QCA9377/hw1.0/
  sudo mv firmware-5.bin_WLAN.TF.1.0-00267-1 firmware-5.bin

  5) Reboot your computer. Run "lshw -C network" to see if your card is
  recognized. You can delete the files you downloaded earlier:

  cd ~
  rm master.zip
  rm -r ath10k-firmware-master/

  Please tell me if these instructions are working for you.

  The original bug description follows.
  ---

  Hi,
  Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux 
kernal. Please add support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-61-generic 3.13.0-61.100
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu14   1658 F pulseaudio
   /dev/snd/controlC1:  ubuntu14   1658 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 12 20:31:24 2015
  HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
  InstallationDate: Installed on 2015-08-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1588375] Re: [i915_bpo] Issues detecting HDMI

[Phidias]

3.19.0-61: Failed
3.19.0-62: Re-plug and change display mode multiple times, HDMI output works 
well

Set to verification-done

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

Title:
  [i915_bpo] Issues detecting HDMI

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This commit needs to be backported to i915_bpo on vivid kernel to fix
  HDMI detection issues on certain hw:

  commit 237ed86c693d8a8e4db476976aeb30df4deac74b
  Author: Sonika Jindal 
  Date:   Tue Sep 15 09:44:20 2015 +0530

  drm/i915: Check live status before reading edid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588375/+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 1593124] Re: Palm rejection for MS Precision Touchpad causes touchpad unusable

[Phidias]

** Tags added: originate-from-1580427 somerville

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

Title:
  Palm rejection for MS Precision Touchpad causes touchpad unusable

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

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1593124] [NEW] Palm rejection for MS Precision Touchpad causes touchpad unusable

[Phidias]

Public bug reported:

Sometimes touchpad doesn't work properly after palm is rejected. The
pointer either jumping around (described on bugzilla[1]) or doesn't move
at all (in our cases).

This problem is introduced with commit:
25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
rejection if device implements confidence usage), by reverting it the
touchpad can work properly.

We also contacted with Synaptics, and they provided a workaround to fix
this issue. Not sure if the workaround will be upstreamed and needs to
keep co-working with them.

Commit 25a84db applies to Xenial and Yakkety so only these two release
were affected.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: originate-from-1580427 somerville 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/1593124

Title:
  Palm rejection for MS Precision Touchpad causes touchpad unusable

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

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1593124/+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 1571530] Re: Need Alps upstream their new touchpad driver

[Phidias]

That's great, I'll backport the driver to our release as soon as it gets
in the mainline repo

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

Title:
  Need Alps upstream their new touchpad driver

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

Bug description:
  Some newer Alps touchpad isn't supported by current kernel therefore
  recognized as PS/2 mouse  and lost some key functions.

  From debug message we saw:
  alps_rpt_cmd: psmouse serio1: alps: E6 report: 00 00 64
  alps_rpt_cmd: psmouse serio1: alps: E7 report: 73 03 28
  alps_rpt_cmd: psmouse serio1: alps: EC report: 73 01 13
  alps_identify: psmouse serio1: alps: Likely not an ALPS touchpad: E7=73 03 
28, EC=73 01 13

  which is different with some Alps bugs reported before.

  Though we've already got drivers from Alps but it's not yet
  upstreamed, this bug is opened for tracking this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1571530/+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 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

[Phidias]

** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

Status in HWE Next:
  Triaged
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1589905/+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 1589905] [NEW] Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

[Phidias]

Public bug reported:

Firmware for this card isn't in the current linux-firmware package.
Latest upstream firmware is also tested but doesn't work either.

The only working firmware is extracted from Windows driver. By comparing
the md5sum, the only different file is ath10k/QCA6174/hw3.0/board.bin
(upstream is cb37c6, and Windows is df5ba1), we need Qualcomm to
upstream the file to fix this issue.

** Affects: hwe-next
 Importance: High
 Assignee: Phidias (phidias-chiang)
 Status: Triaged

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: dw1820b originate-from-1577657 somerville wily xenial

** Tags added: originate-from-1577657 somerville

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

Status in HWE Next:
  Triaged
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1589905/+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 1560835] Re: Enable multitouch function on precision touchpad for Vivid

[Phidias]

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

Title:
  Enable multitouch function on precision touchpad for Vivid

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

Bug description:
  [Impact]

  Multitouch feature is not enabled on some platforms with new Win8
  precision touchpad because it can't fetch the report from the device.
  In worst case it can even break the multitouch device.

  [Fix]

  There's one commit to fix this issue:
  commit 171202b6fee80d777d18bb8a53b3e4361d97f389
  Author: Mika Westerberg 
  Date:   Wed Oct 7 15:33:43 2015 +0300

  HID: multitouch: Fetch feature reports on demand for Win8 devices

  In addition, this commit may cause some issue on ELAN touchpad, and
  there's another commit to improve the fix:

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

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

  Both commits can be clean picked, and are already in Xenial.

  [Test]

  The patched Vivid kernel is tested on two platforms and both worked
  before and after suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1560835/+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 1562778] Re: I2C touchscreen init failed on HP X360

[Phidias]

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

Title:
  I2C touchscreen init failed on HP X360

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

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it depends on a patch to device core for adding
  BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick.

  For Xenial the touchscreen still works because the original patch is
  not reverted, and with the patch reverted the I2C touchscreen still
  works fine, so I'll skip Xenial for this patch.

  For Wily it also contains the revert patch as Vivid, but the I2C on
  X360 still works.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.2.0-34 (with revert patch already) -> OK
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1571530] [NEW] Need Alps upstream their new touchpad driver

[Phidias]

Public bug reported:

Some newer Alps touchpad isn't supported by current kernel therefore
recognized as PS/2 mouse  and lost some key functions.

>From debug message we saw:
alps_rpt_cmd: psmouse serio1: alps: E6 report: 00 00 64
alps_rpt_cmd: psmouse serio1: alps: E7 report: 73 03 28
alps_rpt_cmd: psmouse serio1: alps: EC report: 73 01 13
alps_identify: psmouse serio1: alps: Likely not an ALPS touchpad: E7=73 03 28, 
EC=73 01 13

which is different with some Alps bugs reported before.

Though we've already got drivers from Alps but it's not yet upstreamed,
this bug is opened for tracking this issue.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: Incomplete


** Tags: originate-from-1511647 somerville

** Tags added: originate-from-1511647 somerville

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

Title:
  Need Alps upstream their new touchpad driver

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

Bug description:
  Some newer Alps touchpad isn't supported by current kernel therefore
  recognized as PS/2 mouse  and lost some key functions.

  From debug message we saw:
  alps_rpt_cmd: psmouse serio1: alps: E6 report: 00 00 64
  alps_rpt_cmd: psmouse serio1: alps: E7 report: 73 03 28
  alps_rpt_cmd: psmouse serio1: alps: EC report: 73 01 13
  alps_identify: psmouse serio1: alps: Likely not an ALPS touchpad: E7=73 03 
28, EC=73 01 13

  which is different with some Alps bugs reported before.

  Though we've already got drivers from Alps but it's not yet
  upstreamed, this bug is opened for tracking this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1571530/+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 1562778] Re: I2C touchscreen init failed on HP X360

[Phidias]

** Description changed:

  [Impact]
  
  As title, after upgrading to latest Vivid kernel the touchscreen failed.
  After bisecting shows this revert cause the regression:
  
  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200
  
  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"
  
  [Fix]
  
  The reverted patch has had a revised version upstreamed:
  
  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200
  
  ACPI / LPSS: allow to use specific PM domain during ->probe()
  
  For Vivid it depends on a patch to device core for adding
  BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick.
  
  For Xenial the touchscreen still works because the original patch is not
  reverted, and with the patch reverted the I2C touchscreen still works
  fine, so I'll skip Xenial for this patch.
  
+ For Wily it also contains the revert patch as Vivid, but the I2C on X360
+ still works.
+ 
  [Test]
  
  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
+ 4.2.0-34 (with revert patch already) -> OK
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

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

Title:
  I2C touchscreen init failed on HP X360

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it depends on a patch to device core for adding
  BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick.

  For Xenial the touchscreen still works because the original patch is
  not reverted, and with the patch reverted the I2C touchscreen still
  works fine, so I'll skip Xenial for this patch.

  For Wily it also contains the revert patch as Vivid, but the I2C on
  X360 still works.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.2.0-34 (with revert patch already) -> OK
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1559918] Re: [Bug]SKL-H boot hang when c8+c9+c10 enabled by intel_idle driver

[Phidias]

** Tags added: originate-from-1550112 somerville

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

Title:
  [Bug]SKL-H boot hang when c8+c9+c10 enabled by intel_idle driver

Status in HWE Next:
  New
Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  System will hang immediately with 4.3 kernel above on SKL-H GT4 sdv.
  The workaround for this is intel_idle.max_cstate=6/7 boot option. 
  But intel_idle.max_cstate=8 will generate system hang 

  Bugzilla:
  https://bugzilla.kernel.org/show_bug.cgi?id=109081
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550194

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1559918/+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 1562778] Re: I2C touchscreen init failed on HP X360

[Phidias]

** Description changed:

  [Impact]
  
  As title, after upgrading to latest Vivid kernel the touchscreen failed.
  After bisecting shows this revert cause the regression:
  
  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200
  
  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"
  
  [Fix]
  
  The reverted patch has had a revised version upstreamed:
  
  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200
  
  ACPI / LPSS: allow to use specific PM domain during ->probe()
  
- For Vivid it's a simple clean pick (plus a one line change for header
- file).
+ For Vivid it depends on a patch to device core for adding
+ BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick.
  
  For Xenial the touchscreen still works because the original patch is not
  reverted, and with the patch reverted the I2C touchscreen still works
  fine, so I'll skip Xenial for this patch.
  
  [Test]
  
  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

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

Title:
  I2C touchscreen init failed on HP X360

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

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it depends on a patch to device core for adding
  BUS_NOTIFY_DRIVER_NOT_BOUND notification, both are clean cherry-pick.

  For Xenial the touchscreen still works because the original patch is
  not reverted, and with the patch reverted the I2C touchscreen still
  works fine, so I'll skip Xenial for this patch.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1562778] Re: I2C touchscreen init failed on HP X360

[Phidias]

** Description changed:

  [Impact]
  
  As title, after upgrading to latest Vivid kernel the touchscreen failed.
  After bisecting shows this revert cause the regression:
  
  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200
  
- Revert "ACPI / LPSS: allow to use specific PM domain during
+ Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"
  
  [Fix]
  
  The reverted patch has had a revised version upstreamed:
  
  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200
  
- ACPI / LPSS: allow to use specific PM domain during ->probe()
+ ACPI / LPSS: allow to use specific PM domain during ->probe()
  
  For Vivid it's a simple clean pick (plus a one line change for header
- file), but in Xenial the touchscreen still works because the original
- patch is not reverted. I'll firstly revert the patch than apply the new
- fix.
+ file).
+ 
+ For Xenial the touchscreen still works because the original patch is not
+ reverted, and with the patch reverted the I2C touchscreen still works
+ fine, so I'll skip Xenial for this patch.
  
  [Test]
  
  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.4.0-15 -> OK
- 4.4.0-15 + revert patch -> To Be Tested
- 4.4.0-15 + patches -> To Be Tested
+ 4.4.0-15 + revert patch -> OK
+ 4.4.0-15 + patches -> N/A

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

Title:
  I2C touchscreen init failed on HP X360

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

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it's a simple clean pick (plus a one line change for header
  file).

  For Xenial the touchscreen still works because the original patch is
  not reverted, and with the patch reverted the I2C touchscreen still
  works fine, so I'll skip Xenial for this patch.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> OK
  4.4.0-15 + patches -> N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1562778] Re: I2C touchscreen init failed on HP X360

[Phidias]

** Tags removed: 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/1562778

Title:
  I2C touchscreen init failed on HP X360

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

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko 
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko 
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it's a simple clean pick (plus a one line change for header
  file), but in Xenial the touchscreen still works because the original
  patch is not reverted. I'll firstly revert the patch than apply the
  new fix.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> To Be Tested
  4.4.0-15 + patches -> To Be Tested

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1562778] [NEW] I2C touchscreen init failed on HP X360

[Phidias]

Public bug reported:

[Impact]

As title, after upgrading to latest Vivid kernel the touchscreen failed.
After bisecting shows this revert cause the regression:

commit 95df597989f6f297db63dd8669656d10f5f48eb1
Author: Andy Shevchenko <andriy.shevche...@linux.intel.com>
Date: Fri Dec 4 23:49:18 2015 +0200

Revert "ACPI / LPSS: allow to use specific PM domain during
->probe()"

[Fix]

The reverted patch has had a revised version upstreamed:

commit de16d55206c5ce82ad44590b01718fbe2323853c
Author: Andy Shevchenko <andriy.shevche...@linux.intel.com>
Date:   Fri Dec 4 23:49:19 2015 +0200

ACPI / LPSS: allow to use specific PM domain during ->probe()

For Vivid it's a simple clean pick (plus a one line change for header
file), but in Xenial the touchscreen still works because the original
patch is not reverted. I'll firstly revert the patch than apply the new
fix.

[Test]

3.19.0-56 -> Failed
3.19.0-56 + patches -> OK (Including suspend)
4.4.0-15 -> OK
4.4.0-15 + revert patch -> To Be Tested
4.4.0-15 + patches -> To Be Tested

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: originate-from-1490411 stella vivid xenial

** Tags added: originate-from-1490411 stella

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

Title:
  I2C touchscreen init failed on HP X360

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

Bug description:
  [Impact]

  As title, after upgrading to latest Vivid kernel the touchscreen
  failed. After bisecting shows this revert cause the regression:

  commit 95df597989f6f297db63dd8669656d10f5f48eb1
  Author: Andy Shevchenko <andriy.shevche...@linux.intel.com>
  Date: Fri Dec 4 23:49:18 2015 +0200

  Revert "ACPI / LPSS: allow to use specific PM domain during
  ->probe()"

  [Fix]

  The reverted patch has had a revised version upstreamed:

  commit de16d55206c5ce82ad44590b01718fbe2323853c
  Author: Andy Shevchenko <andriy.shevche...@linux.intel.com>
  Date:   Fri Dec 4 23:49:19 2015 +0200

  ACPI / LPSS: allow to use specific PM domain during ->probe()

  For Vivid it's a simple clean pick (plus a one line change for header
  file), but in Xenial the touchscreen still works because the original
  patch is not reverted. I'll firstly revert the patch than apply the
  new fix.

  [Test]

  3.19.0-56 -> Failed
  3.19.0-56 + patches -> OK (Including suspend)
  4.4.0-15 -> OK
  4.4.0-15 + revert patch -> To Be Tested
  4.4.0-15 + patches -> To Be Tested

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1562778/+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 1560835] Re: Enable multitouch function on precision touchpad for Vivid

[Phidias]

** Description changed:

  [Impact]
  
  Multitouch feature is not enabled on some platforms with new Win8
  precision touchpad because it can't fetch the report from the device. In
  worst case it can even break the multitouch device.
  
  [Fix]
  
  There's one commit to fix this issue:
  commit 171202b6fee80d777d18bb8a53b3e4361d97f389
  Author: Mika Westerberg 
  Date:   Wed Oct 7 15:33:43 2015 +0300
  
- HID: multitouch: Fetch feature reports on demand for Win8 devices
+ HID: multitouch: Fetch feature reports on demand for Win8 devices
  
- In addition, this commit may cost some issue on ELAN touchpad, and
+ In addition, this commit may cause some issue on ELAN touchpad, and
  there's another commit to improve the fix:
  
  commit e47b1e449ea70d76c38a50c04cde60a72bc7ebde
  Author: Benjamin Tissoires 
  Date:   Tue Dec 1 12:41:38 2015 +0100
  
- HID: multitouch: fix input mode switching on some Elan panels
+ HID: multitouch: fix input mode switching on some Elan panels
  
  Both commits can be clean picked, and are already in Xenial.
  
  [Test]
  
  The patched Vivid kernel is tested on two platforms and both worked
  before and after suspend.

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

Title:
  Enable multitouch function on precision touchpad for Vivid

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

Bug description:
  [Impact]

  Multitouch feature is not enabled on some platforms with new Win8
  precision touchpad because it can't fetch the report from the device.
  In worst case it can even break the multitouch device.

  [Fix]

  There's one commit to fix this issue:
  commit 171202b6fee80d777d18bb8a53b3e4361d97f389
  Author: Mika Westerberg 
  Date:   Wed Oct 7 15:33:43 2015 +0300

  HID: multitouch: Fetch feature reports on demand for Win8 devices

  In addition, this commit may cause some issue on ELAN touchpad, and
  there's another commit to improve the fix:

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

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

  Both commits can be clean picked, and are already in Xenial.

  [Test]

  The patched Vivid kernel is tested on two platforms and both worked
  before and after suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1560835/+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 1560835] [NEW] Enable multitouch function on precision touchpad for Vivid

[Phidias]

Public bug reported:

[Impact]

Multitouch feature is not enabled on some platforms with new Win8
precision touchpad because it can't fetch the report from the device. In
worst case it can even break the multitouch device.

[Fix]

There's one commit to fix this issue:
commit 171202b6fee80d777d18bb8a53b3e4361d97f389
Author: Mika Westerberg <mika.westerb...@linux.intel.com>
Date:   Wed Oct 7 15:33:43 2015 +0300

HID: multitouch: Fetch feature reports on demand for Win8 devices

In addition, this commit may cost some issue on ELAN touchpad, and
there's another commit to improve the fix:

commit e47b1e449ea70d76c38a50c04cde60a72bc7ebde
Author: Benjamin Tissoires <benjamin.tissoi...@redhat.com>
Date:   Tue Dec 1 12:41:38 2015 +0100

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

Both commits can be clean picked, and are already in Xenial.

[Test]

The patched Vivid kernel is tested on two platforms and both worked
before and after suspend.

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

** Affects: linux (Ubuntu)
 Importance: Undecided
     Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1560835

Title:
  Enable multitouch function on precision touchpad for Vivid

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

Bug description:
  [Impact]

  Multitouch feature is not enabled on some platforms with new Win8
  precision touchpad because it can't fetch the report from the device.
  In worst case it can even break the multitouch device.

  [Fix]

  There's one commit to fix this issue:
  commit 171202b6fee80d777d18bb8a53b3e4361d97f389
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date:   Wed Oct 7 15:33:43 2015 +0300

  HID: multitouch: Fetch feature reports on demand for Win8 devices

  In addition, this commit may cost some issue on ELAN touchpad, and
  there's another commit to improve the fix:

  commit e47b1e449ea70d76c38a50c04cde60a72bc7ebde
  Author: Benjamin Tissoires <benjamin.tissoi...@redhat.com>
  Date:   Tue Dec 1 12:41:38 2015 +0100

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

  Both commits can be clean picked, and are already in Xenial.

  [Test]

  The patched Vivid kernel is tested on two platforms and both worked
  before and after suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1560835/+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 1535513] Re: Enable suspend function for i2c-hid device in Vivid

[Phidias]

3.19.0-52: 10/10 passed

Set to verification-done-vivid

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

Title:
  Enable suspend function for i2c-hid device in Vivid

Status in HWE Next:
  Fix Committed
Status in HWE Next vivid series:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

  Also, there is a racing condition in i2c-hid module which makes
  touchpad unusable when waking up.

  [Fix]
  This fix has two parts. First part is to enable the suspend/resume function 
in pinctrl-cherryview:

  commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
  Refs: [HEAD]
  Author: Mika Westerberg 
  Date: Thu Dec 4 12:32:50 2014 +0200

  pinctrl: cherryview: Save and restore pin configs over system
  sleep

  The second part is to eliminate the racing condition in i2c-hid:

  commit 9a327405014f4ef4cdad67a0686db82b9f23c62c 
  Author: Mika Westerberg 
  Date:   Mon Dec 21 15:26:31 2015 +0200

  HID: i2c-hid: Prevent sending reports from racing with device
  reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1535513/+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 1535513] Re: Enable suspend function for i2c-hid device in Vivid

[Phidias]

** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: hwe-next
 Assignee: (unassigned) => Phidias (phidias-chiang)

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

Title:
  Enable suspend function for i2c-hid device in Vivid

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

Bug description:
  [Impact]
  On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

  Also, there is a racing condition in i2c-hid module which makes
  touchpad unusable when waking up.

  [Fix]
  This fix has two parts. First part is to enable the suspend/resume function 
in pinctrl-cherryview:

  commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
  Refs: [HEAD]
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date: Thu Dec 4 12:32:50 2014 +0200

  pinctrl: cherryview: Save and restore pin configs over system
  sleep

  The second part is to eliminate the racing condition in i2c-hid:

  commit 9a327405014f4ef4cdad67a0686db82b9f23c62c 
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date:   Mon Dec 21 15:26:31 2015 +0200

  HID: i2c-hid: Prevent sending reports from racing with device
  reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1535513/+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 1518855] Re: Backport better suspend/resume function for pinctrl-cherryview

[Phidias]

A new bug is opened for this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535513


** Changed in: hwe-next
   Status: Triaged => Won't Fix

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

Title:
  Backport better suspend/resume function for pinctrl-cherryview

Status in HWE Next:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

  [Fix]
  There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview:

  commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
  Refs: [HEAD]
  Author: Mika Westerberg 
  Date: Thu Dec 4 12:32:50 2014 +0200

  pinctrl: cherryview: Save and restore pin configs over system sle

  which can be clean cherry-picked

  [Test]
  3.19.0-33 -> failed
  4.2-> passed
  4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test
  3.19.0-33 + patched module -> passed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1518855/+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 1535513] [NEW] Enable suspend function for i2c-hid device in Vivid

[Phidias]

Public bug reported:

[Impact]
On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

Also, there is a racing condition in i2c-hid module which makes touchpad
unusable when waking up.

[Fix]
This fix has two parts. First part is to enable the suspend/resume function in 
pinctrl-cherryview:

commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
Refs: [HEAD]
Author: Mika Westerberg <mika.westerb...@linux.intel.com>
Date: Thu Dec 4 12:32:50 2014 +0200

pinctrl: cherryview: Save and restore pin configs over system sleep

The second part is to eliminate the racing condition in i2c-hid:

commit 9a327405014f4ef4cdad67a0686db82b9f23c62c 
Author: Mika Westerberg <mika.westerb...@linux.intel.com>
Date:   Mon Dec 21 15:26:31 2015 +0200

HID: i2c-hid: Prevent sending reports from racing with device reset

** Affects: linux (Ubuntu)
 Importance: Undecided
     Assignee: Phidias (phidias-chiang)
 Status: Incomplete


** Tags: 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/1535513

Title:
  Enable suspend function for i2c-hid device in Vivid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

  Also, there is a racing condition in i2c-hid module which makes
  touchpad unusable when waking up.

  [Fix]
  This fix has two parts. First part is to enable the suspend/resume function 
in pinctrl-cherryview:

  commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
  Refs: [HEAD]
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date: Thu Dec 4 12:32:50 2014 +0200

  pinctrl: cherryview: Save and restore pin configs over system
  sleep

  The second part is to eliminate the racing condition in i2c-hid:

  commit 9a327405014f4ef4cdad67a0686db82b9f23c62c 
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date:   Mon Dec 21 15:26:31 2015 +0200

  HID: i2c-hid: Prevent sending reports from racing with device
  reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535513/+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 1518855] Re: Backport better suspend/resume function for pinctrl-cherryview

[Phidias]

This  SRU patch fix the problem that pinctrl-cherryview can't suspend which
make i2c touchpad unusable after S3.

But when I'm doing SRU verification I discovered that in about 1/5 time of S3,
the following error occurs:

[ 731.748182] i2c_hid i2c-DLL0725:01: i2c_hid_hwreset
  ...
  ...
[ 736.749017] i2c_hid i2c-DLL0725:01: failed to reset device.
[ 736.750015] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61
[ 736.750022] PM: Device i2c-DLL0725:01 failed to resume: error -61

and the touchpad dies, which didn't happen before with 60 runs of S3
test[1].

It appears to be a race condition in i2c-hid, and there's already a fix for 
this issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9a327405014f4ef4cdad67a0686db82b9f23c62c,
I've built a kernel to test this fix, and it works, no more error -61, and it 
pass 10/10 so far.

Please advice the next step, and sorry for the inconvenience.

[1]: The error message showed up in the test, but the touchpad still
works under i2c so was not considered critical.

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

Title:
  Backport better suspend/resume function for pinctrl-cherryview

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

  [Fix]
  There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview:

  commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
  Refs: [HEAD]
  Author: Mika Westerberg 
  Date: Thu Dec 4 12:32:50 2014 +0200

  pinctrl: cherryview: Save and restore pin configs over system sle

  which can be clean cherry-picked

  [Test]
  3.19.0-33 -> failed
  4.2-> passed
  4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test
  3.19.0-33 + patched module -> passed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1518855/+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 1526220] Re: [SKL] Disable display power well

[Phidias]

Fresh install Ubuntu 15.04:
Update kernel to 3.19.0-43 -> failed
Update kernel to 3.19.0-46 -> pass

The test is positive, change tag to verification-done-vivid

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

Title:
  [SKL] Disable display power well

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Triaged

Bug description:
  Display power well can cause issues like blank screen when logging in
  after resume from suspend, so it's best to disable it for now like
  upstream did in v4.4-rc1:

  commit 1b0e3a049efe471c399674fd954500ce97438d30
  Author: Imre Deak 
  Date:   Thu Nov 5 23:04:11 2015 +0200

  drm/i915/skl: disable display side power well support for now
  
  The display power well support on this platform is in a somewhat broken
  state atm, so disable it by default.
  
  This in effect will get rid of incorrect assert WARNs about the CSR/DMC
  firmware not being loaded during power well toggling. It also removes a
  problem during driver loading where a register is accessed while its
  backing power well is down, resulting in another WARN. Until we come up
  with the root cause of the second problem and the proper fix for both
  issues, keep all display side power wells on.
  
  Also clarify a bit the option description.
  
  Reported-by: Dave Airlie 
  Reference: 
http://mid.gmane.org/CAPM=9tyjbqjsbtka49crr6sykpnw7pq-fufznzz8y1snvvk...@mail.gmail.com
  Signed-off-by: Imre Deak 
  Reviewed-by: Ville Syrjälä 
  Link: 
http://patchwork.freedesktop.org/patch/msgid/1446757451-2777-1-git-send-email-imre.d...@intel.com
  Signed-off-by: Jani Nikula 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1526220/+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 1501580] Re: Workaround for dw_dmac causing random hang when booting

[Phidias]

At the moment I'll say no.

This issue doesn't happen anymore after firmware update on HP X360. I've
asked FE in Taipei to help downgrading the firmware last week,  so I can
verify some patches for dw_dmac, and hopefully can also fix the issue in
#6

If there are fixes for this issue, I'll open another bug to send SRU,
and revert this workaround.

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

Title:
  Workaround for dw_dmac causing random hang  when booting

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Vivid:
  Fix Released

Bug description:
  On HP X360, we've found dw_dmac hangs system when booting with very
  high fail rate (~80%). System can not turn power off when shutting
  down either if dw_dmac is loaded.

  The maintainer from Intel is proposing a patch to fix this issue, but
  won't be available until 4.3 or 4.4, and there're users already hit
  this problem[1], so we proposed a temporarily workaround to skip
  probing in dw_dmac by returning -ENODEV directly if DMI_PRODUCT_NAME
  matches HP X360 before the fix is ready.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=101271

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1501580/+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 1515503] Re: Need support for some buggy Synaptics RMI4 device

[Phidias]

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

Title:
  Need support for some buggy Synaptics RMI4 device

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Some RMI4 touchpad doesn't work properly even the probing returns no
  error. Further investigation shows the interrupt doesn't increase at
  all. There's already a public bug and the patch is already upstreamed:

  https://bugs.freedesktop.org/show_bug.cgi?id=91102

  [Fix]

  There's a fix contains in v4.3-rc1 and has already been tested:

  commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba
  Author: Andrew Duggan 
  AuthorDate: Thu Jul 16 17:14:00 2015 -0700
  Commit: Jiri Kosina 
  CommitDate: Fri Jul 17 11:29:53 2015 +0200

  HID: rmi: Set F01 interrupt enable register when not set

  Note:
So far the platform we encounter with this issue use GPIO interrupt, so it 
also needs 3.19.0-32 or Wily kernel to work too.

  [Test]

  1. Boot with v4.3-rc1 -> pass
  2. Boot with patched Vivid kernel -> pass
  3. Boot with patched Wily kernel -> pass

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1515503/+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 1515503] Re: Need support for some buggy Synaptics RMI4 device

[Phidias]

Re-install Vivid and Wily, the original kernel can't use touchpad. After
upgrading to proposed kernel, both versions' touchpad can work. Set to
verification-done

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

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

Title:
  Need support for some buggy Synaptics RMI4 device

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Some RMI4 touchpad doesn't work properly even the probing returns no
  error. Further investigation shows the interrupt doesn't increase at
  all. There's already a public bug and the patch is already upstreamed:

  https://bugs.freedesktop.org/show_bug.cgi?id=91102

  [Fix]

  There's a fix contains in v4.3-rc1 and has already been tested:

  commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba
  Author: Andrew Duggan 
  AuthorDate: Thu Jul 16 17:14:00 2015 -0700
  Commit: Jiri Kosina 
  CommitDate: Fri Jul 17 11:29:53 2015 +0200

  HID: rmi: Set F01 interrupt enable register when not set

  Note:
So far the platform we encounter with this issue use GPIO interrupt, so it 
also needs 3.19.0-32 or Wily kernel to work too.

  [Test]

  1. Boot with v4.3-rc1 -> pass
  2. Boot with patched Vivid kernel -> pass
  3. Boot with patched Wily kernel -> pass

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1515503/+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 1518855] [NEW] Backport better suspend/resume function for pinctrl-cherryview

[Phidias]

Public bug reported:

[Impact]
On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

[Fix]
There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview:

commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
Refs: [HEAD]
Author: Mika Westerberg <mika.westerb...@linux.intel.com>
Date: Thu Dec 4 12:32:50 2014 +0200

pinctrl: cherryview: Save and restore pin configs over system sle

which can be clean cherry-picked

[Test]
3.19.0-33 -> failed
4.2-> passed
4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test
3.19.0-33 + patched module -> passed

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1518855

Title:
  Backport better suspend/resume function for pinctrl-cherryview

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  On some platforms the touchpad relies on pinctrl devices to provide GPIO 
interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and 
will lose the config after suspend/resume, then touchpad can't be used.

  [Fix]
  There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview:

  commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e
  Refs: [HEAD]
  Author: Mika Westerberg <mika.westerb...@linux.intel.com>
  Date: Thu Dec 4 12:32:50 2014 +0200

  pinctrl: cherryview: Save and restore pin configs over system sle

  which can be clean cherry-picked

  [Test]
  3.19.0-33 -> failed
  4.2-> passed
  4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test
  3.19.0-33 + patched module -> passed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518855/+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 1515503] [NEW] Need support for some buggy Synaptics RMI4 device

[Phidias]

Public bug reported:

[Impact]

Some RMI4 touchpad doesn't work properly even the probing returns no
error. Further investigation shows the interrupt doesn't increase at
all. There's already a public bug and the patch is already upstreamed:

https://bugs.freedesktop.org/show_bug.cgi?id=91102

[Fix]

There's a fix contains in v4.3-rc1 and has already been tested:

commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba
Author: Andrew Duggan <adug...@synaptics.com>
AuthorDate: Thu Jul 16 17:14:00 2015 -0700
Commit: Jiri Kosina <jkos...@suse.com>
CommitDate: Fri Jul 17 11:29:53 2015 +0200

HID: rmi: Set F01 interrupt enable register when not set

Note:
  So far the platform we encounter with this issue use GPIO interrupt, so it 
also needs 3.19.0-32 or Wily kernel to work too.

[Test]

1. Boot with v4.3-rc1 -> pass
2. Boot with patched Vivid kernel -> pass
3. Boot with patched Wily kernel -> pass

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

** Affects: linux (Ubuntu)
 Importance: Undecided
     Assignee: Phidias (phidias-chiang)
 Status: Incomplete


** Tags: vivid wily

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

Title:
  Need support for some buggy Synaptics RMI4 device

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

Bug description:
  [Impact]

  Some RMI4 touchpad doesn't work properly even the probing returns no
  error. Further investigation shows the interrupt doesn't increase at
  all. There's already a public bug and the patch is already upstreamed:

  https://bugs.freedesktop.org/show_bug.cgi?id=91102

  [Fix]

  There's a fix contains in v4.3-rc1 and has already been tested:

  commit 9a98b3387e7bd9af5a6495b32e07d6f25071f4ba
  Author: Andrew Duggan <adug...@synaptics.com>
  AuthorDate: Thu Jul 16 17:14:00 2015 -0700
  Commit: Jiri Kosina <jkos...@suse.com>
  CommitDate: Fri Jul 17 11:29:53 2015 +0200

  HID: rmi: Set F01 interrupt enable register when not set

  Note:
So far the platform we encounter with this issue use GPIO interrupt, so it 
also needs 3.19.0-32 or Wily kernel to work too.

  [Test]

  1. Boot with v4.3-rc1 -> pass
  2. Boot with patched Vivid kernel -> pass
  3. Boot with patched Wily kernel -> pass

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1515503/+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 1501187] Re: Backport support for ACPI GPIO interrupts for i2c-hid devices

[Phidias]

Test:
1. Install proposed kernel
2. Check if touchscreen works -> pass
3. Test if touchscreen works after S3 -> pass

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

Title:
  Backport support for ACPI GPIO interrupts for i2c-hid devices

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

Bug description:
  [Impact]

  On some platforms HID over I2C uses GPIO interrupts instead of
  directly connected to the IO-APIC. Without ACPI GPIO interrupts
  support, i2c-hid can not find IRQ when probing the device, and shows
  the following message:

  i2c_hid i2c-SYNA7508:00: Could not register for SYNA7508:00 interrupt, irq = 
-1, ret = -22
  i2c_hid: probe of i2c-SYNA7508:00 failed with error -22

  So far we've found this issue on some SKL platforms, and one BSW
  platform.

  [Fix]

  There's a fix in mainline v4.1-rc1, which add the support for ACPI
  GPIO interrupts for i2c-hid module.

  Commit log is as follows:

  commit a485923efbb83056b7fb79e4fd2fee05c990ad5e
  Author: Mika Westerberg 
  Commit: Jiri Kosina 
  CommitDate: Tue Feb 24 20:53:30 2015 +0100

  HID: i2c-hid: Add support for ACPI GPIO interrupts

  [Test]

  1. Boot with 4.1-rc1 kernel and patched 3.19 kernel
  2. Both touchscreen should work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1501187/+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 1501580] Re: Workaround for dw_dmac causing random hang when booting

[Phidias]

Test:
1. Remove `blacklist dw_dmac` workaround
2. Install proposed kernel
3. Test if system hangs -> pass
4. Check if the message "HP X360 detected, skip probing" appears -> yes

Since in the patch it compares the product name in DMI string to decide
if to skip the dw_dmac probing, so no side-effect is expected.

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

Title:
  Workaround for dw_dmac causing random hang  when booting

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

Bug description:
  On HP X360, we've found dw_dmac hangs system when booting with very
  high fail rate (~80%). System can not turn power off when shutting
  down either if dw_dmac is loaded.

  The maintainer from Intel is proposing a patch to fix this issue, but
  won't be available until 4.3 or 4.4, and there're users already hit
  this problem[1], so we proposed a temporarily workaround to skip
  probing in dw_dmac by returning -ENODEV directly if DMI_PRODUCT_NAME
  matches HP X360 before the fix is ready.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=101271

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1501580/+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 1501187] Re: Backport support for ACPI GPIO interrupts for i2c-hid devices

[Phidias]

Test:
1. Remove `blacklist dw_dmac` workaround
2. Install proposed kernel
3. Test if system hangs -> pass
4. Check if the message "HP X360 detected, skip probing" appears -> yes

Since in the patch it compares the product name in DMI string to decide
if to skip the dw_dmac probing, so no side-effect is expected.

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

Title:
  Backport support for ACPI GPIO interrupts for i2c-hid devices

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

Bug description:
  [Impact]

  On some platforms HID over I2C uses GPIO interrupts instead of
  directly connected to the IO-APIC. Without ACPI GPIO interrupts
  support, i2c-hid can not find IRQ when probing the device, and shows
  the following message:

  i2c_hid i2c-SYNA7508:00: Could not register for SYNA7508:00 interrupt, irq = 
-1, ret = -22
  i2c_hid: probe of i2c-SYNA7508:00 failed with error -22

  So far we've found this issue on some SKL platforms, and one BSW
  platform.

  [Fix]

  There's a fix in mainline v4.1-rc1, which add the support for ACPI
  GPIO interrupts for i2c-hid module.

  Commit log is as follows:

  commit a485923efbb83056b7fb79e4fd2fee05c990ad5e
  Author: Mika Westerberg 
  Commit: Jiri Kosina 
  CommitDate: Tue Feb 24 20:53:30 2015 +0100

  HID: i2c-hid: Add support for ACPI GPIO interrupts

  [Test]

  1. Boot with 4.1-rc1 kernel and patched 3.19 kernel
  2. Both touchscreen should work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1501187/+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 1501187] Re: Backport support for ACPI GPIO interrupts for i2c-hid devices

[Phidias]

** Also 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/1501187

Title:
  Backport support for ACPI GPIO interrupts for i2c-hid devices

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

Bug description:
  [Impact]

  On some platforms HID over I2C uses GPIO interrupts instead of
  directly connected to the IO-APIC. Without ACPI GPIO interrupts
  support, i2c-hid can not find IRQ when probing the device, and shows
  the following message:

  i2c_hid i2c-SYNA7508:00: Could not register for SYNA7508:00 interrupt, irq = 
-1, ret = -22
  i2c_hid: probe of i2c-SYNA7508:00 failed with error -22

  So far we've found this issue on some SKL platforms, and one BSW
  platform.

  [Fix]

  There's a fix in mainline v4.1-rc1, which add the support for ACPI
  GPIO interrupts for i2c-hid module.

  Commit log is as follows:

  commit a485923efbb83056b7fb79e4fd2fee05c990ad5e
  Author: Mika Westerberg 
  Commit: Jiri Kosina 
  CommitDate: Tue Feb 24 20:53:30 2015 +0100

  HID: i2c-hid: Add support for ACPI GPIO interrupts

  [Test]

  1. Boot with 4.1-rc1 kernel and patched 3.19 kernel
  2. Both touchscreen should work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1501187/+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 1473880] Re: Backport Intel 8260 Wifi/BT drivers

[Phidias]

@pdf:
We're actually working on a backport module package for 3.19.0 kernel to 
include these drivers

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

Title:
  Backport Intel 8260 Wifi/BT drivers

Status in linux package in Ubuntu:
  Expired

Bug description:
  The drivers are now available in mainline 4.1 kernel and has been
  tested. Vivid currently doesn't support Intel 8260 Wifi/BT, and need
  to backport the drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473880/+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 1489292] Re: System cannot detect USB device in BAT mode

[Phidias]

** Changed in: hwe-next
   Status: Triaged => Fix Released

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

Title:
  System cannot detect USB device in BAT mode

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  On some Skylake-U platforms, if boots with battery only and has no USB
  device connect, after boot the USB port can't be used, even though the
  xHCI Host Controller doesn't report any error in dmesg. The USB device
  looks like doesn't turn on, LED on USB mouse or keyboard doesn't light
  up.

  [Fix]

  There's a fix in mainline v4.2-rc3, though it states the fix is for
  Braswell, but the uuid use in the commit can also be found on
  Skylake-U platforms.

  Commit log is as follows:

  commit c3c5819a350952439c3198aa46581f9e4c46557f
  Author: Mathias Nyman 
  Date:   Tue Jul 21 17:20:25 2015 +0300

  xhci: call BIOS workaround to enable runtime suspend on Intel
  Braswell

  Intel xhci hw that require XHCI_PME_STUCK quirk have as default disabled
  xhci from going to D3 state in runtime suspend. Driver needs to verify
  it can deal with the hw by calling an ACPI _DSM method to get D3 enabled.

  Signed-off-by: Mathias Nyman 
  Signed-off-by: Greg Kroah-Hartman 

  [Test]

  1. Install the patched kernel
  2. Boot with battery
  3. Insert a USB device (disk, keyboard, mouse), should work normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1489292/+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 1501580] Re: Workaround for dw_dmac causing random hang when booting

[Phidias]

** Also 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/1501580

Title:
  Workaround for dw_dmac causing random hang  when booting

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

Bug description:
  On HP X360, we've found dw_dmac hangs system when booting with very
  high fail rate (~80%). System can not turn power off when shutting
  down either if dw_dmac is loaded.

  The maintainer from Intel is proposing a patch to fix this issue, but
  won't be available until 4.3 or 4.4, and there're users already hit
  this problem[1], so we proposed a temporarily workaround to skip
  probing in dw_dmac by returning -ENODEV directly if DMI_PRODUCT_NAME
  matches HP X360 before the fix is ready.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=101271

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

[Phidias]

Test on TUSL4-E3-C3 (SKL) is done, the proposed kernel shows positive
result.

-- 
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 1489292] Re: System cannot detect USB device in BAT mode

[Phidias]

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

Title:
  System cannot detect USB device in BAT mode

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  On some Skylake-U platforms, if boots with battery only and has no USB
  device connect, after boot the USB port can't be used, even though the
  xHCI Host Controller doesn't report any error in dmesg. The USB device
  looks like doesn't turn on, LED on USB mouse or keyboard doesn't light
  up.

  [Fix]

  There's a fix in mainline v4.2-rc3, though it states the fix is for
  Braswell, but the uuid use in the commit can also be found on
  Skylake-U platforms.

  Commit log is as follows:

  commit c3c5819a350952439c3198aa46581f9e4c46557f
  Author: Mathias Nyman 
  Date:   Tue Jul 21 17:20:25 2015 +0300

  xhci: call BIOS workaround to enable runtime suspend on Intel
  Braswell

  Intel xhci hw that require XHCI_PME_STUCK quirk have as default disabled
  xhci from going to D3 state in runtime suspend. Driver needs to verify
  it can deal with the hw by calling an ACPI _DSM method to get D3 enabled.

  Signed-off-by: Mathias Nyman 
  Signed-off-by: Greg Kroah-Hartman 

  [Test]

  1. Install the patched kernel
  2. Boot with battery
  3. Insert a USB device (disk, keyboard, mouse), should work normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1489292/+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 1489292] [NEW] System cannot detect USB device in BAT mode

[Phidias]

Public bug reported:

[Impact]

On some Skylake-U platforms, if boots with battery only and has no USB
device connect, after boot the USB port can't be used, even though the
xHCI Host Controller doesn't report any error in dmesg. The USB device
looks like doesn't turn on, LED on USB mouse or keyboard doesn't light
up.

[Fix]

There's a fix in mainline v4.2-rc3, though it states the fix is for
Braswell, but the uuid use in the commit can also be found on Skylake-U
platforms.

Commit log is as follows:

commit c3c5819a350952439c3198aa46581f9e4c46557f
Author: Mathias Nyman mathias.ny...@linux.intel.com
Date:   Tue Jul 21 17:20:25 2015 +0300

xhci: call BIOS workaround to enable runtime suspend on Intel
Braswell

Intel xhci hw that require XHCI_PME_STUCK quirk have as default disabled
xhci from going to D3 state in runtime suspend. Driver needs to verify
it can deal with the hw by calling an ACPI _DSM method to get D3 enabled.

Signed-off-by: Mathias Nyman mathias.ny...@linux.intel.com
Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

[Test]

1. Install the patched kernel
2. Boot with battery
3. Insert a USB device (disk, keyboard, mouse), should work normally

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

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New


** Tags: 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/1489292

Title:
  System cannot detect USB device in BAT mode

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

Bug description:
  [Impact]

  On some Skylake-U platforms, if boots with battery only and has no USB
  device connect, after boot the USB port can't be used, even though the
  xHCI Host Controller doesn't report any error in dmesg. The USB device
  looks like doesn't turn on, LED on USB mouse or keyboard doesn't light
  up.

  [Fix]

  There's a fix in mainline v4.2-rc3, though it states the fix is for
  Braswell, but the uuid use in the commit can also be found on
  Skylake-U platforms.

  Commit log is as follows:

  commit c3c5819a350952439c3198aa46581f9e4c46557f
  Author: Mathias Nyman mathias.ny...@linux.intel.com
  Date:   Tue Jul 21 17:20:25 2015 +0300

  xhci: call BIOS workaround to enable runtime suspend on Intel
  Braswell

  Intel xhci hw that require XHCI_PME_STUCK quirk have as default disabled
  xhci from going to D3 state in runtime suspend. Driver needs to verify
  it can deal with the hw by calling an ACPI _DSM method to get D3 enabled.

  Signed-off-by: Mathias Nyman mathias.ny...@linux.intel.com
  Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

  [Test]

  1. Install the patched kernel
  2. Boot with battery
  3. Insert a USB device (disk, keyboard, mouse), should work normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1489292/+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 1476900] Re: Backport Intel 8260 Wifi/BT firmwares

[Phidias]

Verify step:

1. Remove Intel 8260 module
2. Clean install Vivid/Trusty, and install Intel 8260 module back
3. Install 4.1 kernel which contains 8260 Wifi/BT driver
4. Check if the device works - no, can't find firmware as expected
5. Add -proposed repo and update, then install new linux-firmware
6. Reboot and verify if the device works - yes, both wifi and BT can find the 
firmware and work

For Trusty:
Install linux-firmware-1.127.15

For Vivid:
Install linux-firmware-1.143.3

Both work.

** Tags added: verification-done

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

Title:
  Backport Intel 8260 Wifi/BT firmwares

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Vivid:
  Fix Committed

Bug description:
  Both Intel 8260 Wifi and Bluetooth firmwares are now available in
  mainline linux-firmware and has been tested. Vivid currently doesn't
  support Intel 8260 Wifi and BT, and need to backport the firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1476900/+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 1473880] Re: Backport Intel 8260 Wifi/BT driver

[Phidias]

** Summary changed:

- Backport Intel 8260 Wifi driver
+ Backport Intel 8260 Wifi/BT driver

** Description changed:

- The driver is now available in mainline 4.1 kernel and has been tested.
- Vivid currently doesn't support Intel 8260 Wifi, and need to backport
- the driver.
+ The drivers are now available in mainline 4.1 kernel and has been
+ tested. Vivid currently doesn't support Intel 8260 Wifi/BT, and need to
+ backport the drivers.

** Summary changed:

- Backport Intel 8260 Wifi/BT driver
+ Backport Intel 8260 Wifi/BT drivers

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

Title:
  Backport Intel 8260 Wifi/BT drivers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The drivers are now available in mainline 4.1 kernel and has been
  tested. Vivid currently doesn't support Intel 8260 Wifi/BT, and need
  to backport the drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473880/+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 1476900] Re: Backport Intel 8260 Wifi/BT firmwares

[Phidias]

We're also planning to backport 8260 Wifi/BT drivers for better support,
which use the new firmware. In our test the old driver is not work well.

For drivers bug please refer to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473880

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

Title:
  Backport Intel 8260 Wifi/BT firmwares

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Both Intel 8260 Wifi and Bluetooth firmwares are now available in
  mainline linux-firmware and has been tested. Vivid currently doesn't
  support Intel 8260 Wifi and BT, and need to backport the firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1476900/+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 1476900] [NEW] Backport Intel 8260 Wifi/BT firmwares

[Phidias]

Public bug reported:

Both Intel 8260 Wifi and Bluetooth firmwares are now available in
mainline linux-firmware and has been tested. Vivid currently doesn't
support Intel 8260 Wifi and BT, and need to backport the firmwares.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: New

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

Title:
  Backport Intel 8260 Wifi/BT firmwares

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Both Intel 8260 Wifi and Bluetooth firmwares are now available in
  mainline linux-firmware and has been tested. Vivid currently doesn't
  support Intel 8260 Wifi and BT, and need to backport the firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1476900/+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 1473880] [NEW] Backport Intel 8260 Wifi driver

[Phidias]

Public bug reported:

The driver is now available in mainline 4.1 kernel and has been tested.
Vivid currently doesn't support Intel 8260 Wifi, and need to backport
the driver.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Phidias (phidias-chiang)
 Status: Incomplete

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

Title:
  Backport Intel 8260 Wifi driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The driver is now available in mainline 4.1 kernel and has been
  tested. Vivid currently doesn't support Intel 8260 Wifi, and need to
  backport the driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473880/+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 1450322] Re: [i915_bdw] No screen output on specific LCD panel (DPN: 99DCK))

[Phidias]

Test against with 3.13.0-49 to reproduced the problem, and then
installed 3.13.0-53 in trusty-proposed to verify the fix, and it works.

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

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

Title:
  [i915_bdw] No screen output on specific LCD panel (DPN: 99DCK))

Status in HWE Next Project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Summary]
  There are no screen output on specific LCD panel (DPN: 99DCK).

  [Reproduce Steps]
  1. Normal install the system
  2. start the system

  [Results]:
  Only black screen showed up

  [Additional Information]
  Kernel: 3.13.0-36-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1450322/+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 1434442] Re: [Vostro 3549] Wireless key does not work on 14.04.2

[Phidias]

The patch in #7 fix the wireless hotkey.

** Changed in: hwe-next
 Assignee: Phidias (phidias-chiang) = Alex Hung (alexhung)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: Phidias (phidias-chiang) = Alex Hung (alexhung)

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

Title:
  [Vostro 3549] Wireless key does not work on 14.04.2

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

Bug description:
  CID: 201408-15444 Vostro 3549

  The wireless key does not work on this system.

  Debugging information:
  ubuntu@201408-15444:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  ^Ccaught signal 2, cleaning up...

  Nothing could be detected by sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-31-generic 3.16.0-31.43~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 20 04:24:01 2015
  InstallationDate: Installed on 2015-03-20 (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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1434442/+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 1442466] Re: [Dell Inspiron 3147] wireless hotkey does not work on 14.04.2

[Phidias]

** Changed in: hwe-next
 Assignee: Phidias (phidias-chiang) = Keng-Yu Lin (lexical)

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

Title:
  [Dell Inspiron 3147] wireless hotkey does not work on 14.04.2

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

Bug description:
  201403-14889

  Steps to reproduce this bug:
  fn+printscr button (this is the way to trigger wireless switch)

  Expected to reproduce this bug:
  wireless on/off

  Actual result:
  1. wireless applet has no response
  2. rfkill list has no reponse. always shows

  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  More info:
  1. APs could be scanned.
  2. could enable/disable wifi via desktop applet.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-34-generic 3.16.0-34.45~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 10 11:53:57 2015
  InstallationDate: Installed on 2015-04-09 (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.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1654 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=442dffc7-a562-4b0d-a6d6-cb69d6891c61
  InstallationDate: Installed on 2015-04-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 11 - 3147
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=da9b59f7-7780-41c5-9e5f-03acb414b69e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-34-generic N/A
   linux-backports-modules-3.16.0-34-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.16.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/22/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X30
  dmi.board.name: 00K010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X30
  dmi.modalias: 
dmi:bvnDellInc.:bvrX30:bd08/22/2014:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn00K010:rvrD02:cvnDellInc.:ct8:cvrX30:
  dmi.product.name: Inspiron 11 - 3147
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1442466/+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 1440949] Re: [Dell Inspiron 3543] Wireless key does not work on 14.04.2

[Phidias]

** Changed in: hwe-next
 Assignee: Phidias (phidias-chiang) = Keng-Yu Lin (lexical)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: Phidias (phidias-chiang) = Keng-Yu Lin (lexical)

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

Title:
  [Dell Inspiron 3543] Wireless key does not work on 14.04.2

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

Bug description:
  CID: 201408-15437 Dell Inspiron 3543

  The wireless key does not work on this system at all with14.04.2 (3.16 kernel)
  Maybe it's related to the udev - systemd migration (similar to bug 1434442)

  ubuntu@201408-15437:~$ sudo showkey -k
  [sudo] password for ubuntu: 
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...
  ubuntu@201408-15437:~$

  nothing could be detected by sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  6 22:17:20 2015
  InstallationDate: Installed on 2015-04-03 (3 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/1440949/+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 1439592] Re: [Dell Inspiron 7347] Wireless key does not work on 3.16 kernel

[Phidias]

https://bugs.launchpad.net/ubuntu/+source/linux-lts-
utopic/+bug/1434442/comments/8

** Changed in: hwe-next
 Assignee: Phidias (phidias-chiang) = Alex Hung (alexhung)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: Phidias (phidias-chiang) = Alex Hung (alexhung)

** Changed in: hwe-next
 Assignee: Alex Hung (alexhung) = Keng-Yu Lin (lexical)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: Alex Hung (alexhung) = Keng-Yu Lin (lexical)

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

Title:
  [Dell Inspiron 7347] Wireless key does not work on 3.16 kernel

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

Bug description:
  CID: 201406-15234 Dell Inspiron 7347

  The wireless key does not work on this system at all with 14.04.2 (3.16 
kernel)
  Maybe it's related to the udev - systemd migration (similar to bug 1434442)

  ubuntu@201406-15234:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  ^Ccaught signal 2, cleaning up...
  ubuntu@201406-15234:~$ 

  Nothing can be detected by the sudo showkey -s command

  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
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  2 05:12:56 2015
  InstallationDate: Installed on 2015-04-02 (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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1439592/+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 1439935] Re: [Dell Inspiron 7746] Wireless key does not work on 14.04.2

[Phidias]

https://bugs.launchpad.net/ubuntu/+source/linux-lts-
utopic/+bug/1434442/comments/8

** Changed in: hwe-next
 Assignee: Phidias (phidias-chiang) = Alex Hung (alexhung)

** Changed in: hwe-next
 Assignee: Alex Hung (alexhung) = Keng-Yu Lin (lexical)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: Phidias (phidias-chiang) = Keng-Yu Lin (lexical)

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

Title:
  [Dell Inspiron 7746] Wireless key does not work on 14.04.2

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

Bug description:
  CID: 201408-15456 Dell Inspiron 7746

  The wireless key does not work on this system at all with14.04.2 (3.16 kernel)
  Maybe it's related to the udev - systemd migration (similar to bug 1434442)

  ubuntu@201408-15456:~$ sudo showkey -k
  [sudo] password for ubuntu: 
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode 240 press
  keycode 240 release
  ^Ccaught signal 2, cleaning up...
  ubuntu@201408-15456:~$ 

  nothing could be detected by sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  2 23:22:28 2015
  InstallationDate: Installed on 2015-04-03 (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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1439935/+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 1435278] Re: [Dell Vostro 3449] Wireless key does not work on 14.04.2 (3.16 kernel)

[Phidias]

** Changed in: hwe-next
 Assignee: Phidias (phidias-chiang) = Keng-Yu Lin (lexical)

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

Title:
  [Dell Vostro 3449] Wireless key does not work on 14.04.2 (3.16 kernel)

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

Bug description:
  CID: 201408-15447 Dell Vostro 3449

  The wireless key does not work on this system at all.
  acpi_osi=\!Windows 2012\ parameter can't make it work.
  And unlike bug 1434442, adding options dell_laptop force_rfkill=1 into 
/etc/modprobe.d/dell.conf can't make it work as well.

  ubuntu@201408-15447:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...
  ubuntu@201408-15447:~$ 

  
  nothing could be detected by using sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-31-generic 3.16.0-31.43~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 07:04:20 2015
  InstallationDate: Installed on 2015-03-23 (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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1435278/+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 1435731] Re: [Dell Inspiron 7437] Wireless key does not work on 14.04.1

[Phidias]

** Changed in: hwe-next
 Assignee: Alex Hung (alexhung) = Keng-Yu Lin (lexical)

** Changed in: linux (Ubuntu)
 Assignee: Alex Hung (alexhung) = Keng-Yu Lin (lexical)

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

Title:
  [Dell Inspiron 7437] Wireless key does not work on 14.04.1

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

Bug description:
  CID: 201307-13932 Dell Inspiron 7437

  The wireless key does not work on this system.
  Nothing could be detected with sudo showkey -s

  ubuntu@201307-13932:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  ^Ccaught signal 2, cleaning up...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-48-generic 3.13.0-48.80
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1574 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1574 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 Mar 24 04:45:23 2015
  HibernationDevice: RESUME=UUID=bd120b66-ea6e-4f9b-b52a-021340e042d3
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 7437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic 
root=UUID=b603f1fd-caaa-4688-aff0-288141b61d50 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-48-generic N/A
   linux-backports-modules-3.13.0-48-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/31/2013:svnDellInc.:pnInspiron7437:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 7437
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1435731/+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 1442466] Re: [Dell Inspiron 3147] wireless hotkey does not work on 14.04.2

[Phidias]

https://bugs.launchpad.net/ubuntu/+source/linux-lts-
utopic/+bug/1434442/comments/8

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

Title:
  [Dell Inspiron 3147] wireless hotkey does not work on 14.04.2

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

Bug description:
  201403-14889

  Steps to reproduce this bug:
  fn+printscr button (this is the way to trigger wireless switch)

  Expected to reproduce this bug:
  wireless on/off

  Actual result:
  1. wireless applet has no response
  2. rfkill list has no reponse. always shows

  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  More info:
  1. APs could be scanned.
  2. could enable/disable wifi via desktop applet.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-34-generic 3.16.0-34.45~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 10 11:53:57 2015
  InstallationDate: Installed on 2015-04-09 (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.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1654 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=442dffc7-a562-4b0d-a6d6-cb69d6891c61
  InstallationDate: Installed on 2015-04-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 11 - 3147
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=da9b59f7-7780-41c5-9e5f-03acb414b69e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-34-generic N/A
   linux-backports-modules-3.16.0-34-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.16.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/22/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X30
  dmi.board.name: 00K010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X30
  dmi.modalias: 
dmi:bvnDellInc.:bvrX30:bd08/22/2014:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn00K010:rvrD02:cvnDellInc.:ct8:cvrX30:
  dmi.product.name: Inspiron 11 - 3147
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1442466/+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 1440949] Re: [Dell Inspiron 3543] Wireless key does not work on 14.04.2

[Phidias]

https://bugs.launchpad.net/ubuntu/+source/linux-lts-
utopic/+bug/1434442/comments/8

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

Title:
  [Dell Inspiron 3543] Wireless key does not work on 14.04.2

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

Bug description:
  CID: 201408-15437 Dell Inspiron 3543

  The wireless key does not work on this system at all with14.04.2 (3.16 kernel)
  Maybe it's related to the udev - systemd migration (similar to bug 1434442)

  ubuntu@201408-15437:~$ sudo showkey -k
  [sudo] password for ubuntu: 
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...
  ubuntu@201408-15437:~$

  nothing could be detected by sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  6 22:17:20 2015
  InstallationDate: Installed on 2015-04-03 (3 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/1440949/+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 1435278] Re: [Dell Vostro 3449] Wireless key does not work on 14.04.2 (3.16 kernel)

[Phidias]

https://bugs.launchpad.net/ubuntu/+source/linux-lts-
utopic/+bug/1434442/comments/8

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

Title:
  [Dell Vostro 3449] Wireless key does not work on 14.04.2 (3.16 kernel)

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

Bug description:
  CID: 201408-15447 Dell Vostro 3449

  The wireless key does not work on this system at all.
  acpi_osi=\!Windows 2012\ parameter can't make it work.
  And unlike bug 1434442, adding options dell_laptop force_rfkill=1 into 
/etc/modprobe.d/dell.conf can't make it work as well.

  ubuntu@201408-15447:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...
  ubuntu@201408-15447:~$ 

  
  nothing could be detected by using sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-31-generic 3.16.0-31.43~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 07:04:20 2015
  InstallationDate: Installed on 2015-03-23 (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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1435278/+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 1418312] Re: [HP Pavilion 14 Notebook PC] Audio mute LED does not work on 14.04.1

[Phidias]

The alsa daily build (oem-audio-hda-daily-
dkms-0.201502051931~ubuntu14.04.1) fix the problem, the audio mute LED
works now.

Release: 14.04.1 LTS
Kernel: 3.13.0-45-generic #74-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/1418312

Title:
  [HP Pavilion 14 Notebook PC] Audio mute LED does not work on 14.04.1

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

Bug description:
  CID: 201303-13115 HP Pavilion 14 Notebook PC

  The audio mute LED does not work on this system.

  Steps:
  1. Install 14.04.1 + update (3.13.0-45)
  2. Verify the audio mute LED

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

  ubuntu@201303-13115:~$ lspci -nn | grep -i audio
  00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller [8086:0c0c] (rev 02)
  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 02)

  Codec: Realtek ALC282

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2035 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Feb  4 22:27:46 2015
  HibernationDevice: RESUME=UUID=d7ac18b8-cbc0-4c4b-91d9-73a5563c3f29
  InstallationDate: Installed on 2015-02-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=25461a3a-bfb5-4777-985d-7aab84c57b24 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1974
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd05/28/2013:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr089D100630100:rvnHewlett-Packard:rn1974:rvr96.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 089D100630100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1418312/+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 1407571] Re: [Dell Latitude 3340] Microphone mute LED does not work on 14.04.1

[Phidias]

dkms from alsa-daily ppa has been tested. Mic mute LED works, but
wireless LED stays lit on (hotkey can disable/enable wireless, but the
LED doesn't behave right).

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

Title:
  [Dell Latitude 3340] Microphone mute LED does not work on 14.04.1

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

Bug description:
  CID: 201312-14381 Dell Latitude 3340

  As mentioned in bug 1326684, the mic mute LED does not work on this
  system.

  Steps:
  1. Install 14.04.1 + update to make the mic mute key work
  2. Test the mic mute key

  Expected result:
  Mic mute LED should lit when the mic is disabled.

  Actual result:
  The mic mute LED is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1540 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1540 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Mon Jan  5 02:00:57 2015
  HibernationDevice: RESUME=UUID=8881bf5a-55d6-4314-80db-170ff3d262b6
  InstallationDate: Installed on 2015-01-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude 3340
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed 
root=UUID=9f9c408e-d1c2-496c-9fd2-8f9ecb77810b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-43-generic N/A
   linux-backports-modules-3.13.0-43-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 4OA010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd05/02/2014:svnDellInc.:pnLatitude3340:pvr01:rvnDellInc.:rn4OA010:rvrD01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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