[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260

2019-06-10 Thread Anthony Wong
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.2-rc4 kernel[1].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc4

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

Title:
  Bluetooth not work on INTEL WIRELESS-AC 9260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+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 1831065] Re: does not detect headphone when there is no other output devices

2019-06-06 Thread Anthony Wong
** Tags added: oem-priority

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

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: New => Incomplete

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: Incomplete => Invalid

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

Title:
  does not detect headphone when there is no other output devices

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  Invalid

Bug description:
  These two patches are already in the kernel-v5.0, so only B and C need
  these two patches.

  [Impact]
  On a Dell machine, there is no other output devices but a headphone
  on it, when plugging headset, the headset-mic can't work.

  [Fix]
  The headphone detection method is buggy, the driver can't detect
  the headphone, then the driver will not initialize for headset-mic,
  after applying these patches, the problem is fixed.

  [Test Case]
  Plug headset and record the sound from headset-mic, it works well.

  [Regression Risk]
  Low. the patch just change the headphone detection function, and the
  function is already in the kernel from 5.0-rc, no bug is reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831065/+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 1831833] Re: [SRU][B/C] Add the firmwares of RTL8822BE and RTL8822CE

2019-06-06 Thread Anthony Wong
** Also affects: linux-firmware (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  [SRU][B/C] Add the firmwares of RTL8822BE and RTL8822CE

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware source package in Cosmic:
  New

Bug description:
  SRU justification:

  [Impact]
  Add new firmwares of RTL8822BE/RTL8822CE.

  [Fix]
  rtw88 and these new firmwares will support RTL8822BE/RTL8822CE

  [Test]
  Verified on hardware. Tests result are good.

  [Regression Potential]
  Low, it introducs the new firmwares to enable new wifi chips supports.
  These firmwares are already in disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831833/+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 1831828] Re: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88

2019-06-06 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

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

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

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

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: New => Invalid

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

** Changed in: linux-oem-osp1 (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: New => Invalid

** Changed in: linux-oem-osp1 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux-oem-osp1 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  SRU justification:

  [Impact]
  RTL8822BE/RTL8822CE need new driver rtw88 supports.

  [Fix]
  This is a new mac80211 driver for Realtek 802.11ac wireless network chips.
  And it needs new firmware too.

  [Test]
  Verified on hardware. Tests result are good.

  [Regression Potential]
  Low, it introducs the new driver to enable new wifi chips supports.
  2 more upstream commits are introduced:
  e7d4a95da bitfield: fix *_encode_bits()
  00b0c9b82 Add primitives for manipulating bitfields both in host- and 
fixed-endian.
  These 2 commits add "le32p_replace_bits" functions that rtw88 uses.
  They introduced new operator of bitfields since 4.16 kernel, don't change 
exsit funtions.
  C/D/OEM-OSP-1 don't need these 2 patches.

  These firmwares are already in disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831828/+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 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines

2019-06-02 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  iwlwifi fails to work on 16 or more logical CPUs machines

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or 
more logical CPUs
 kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  And it leads to wifi can't scan any APs, and leads to system hangs while 
suspending.

  [Fix]
  Below commit contained in v4.17 fix the issue.
 ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not 
number of CPUs

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805088/+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 1825272] Re: headset-mic doesn't work on two Dell laptops.

2019-06-01 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  headset-mic doesn't work on two Dell laptops.

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  the headset-mic can't be detected after we plug the headset into the audio 
jack

  [Fix]
  Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE.

  [Test Case]
  Boot up the system
  plug the headset into the audio jack
  The audio device selecting dialogue will show up
  selecting headset-mic icon, then rerord sound from headset-mic, it works well.

  [Regression Risk]
  Low. this patch only applies to specific dell machines which have the same 
pin config
  as defined in the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1825272/+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 1756700] Re: Ryzen/Raven Ridge USB ports do not work

2019-06-01 Thread Anthony Wong
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1756700

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1756700/+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 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor

2019-05-30 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1827967

Title:
  There are 4 HDMI/Displayport audio output listed in sound setting
  without attach any HDMI/DP monitor

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  In our OEM projects, we often meet this issues, there is no any monitor 
plugged,
  but in the gnome-sound-setting, there are 4 hdmi/dp audio devices.

  
  [Fix]
  We check the eld_valid when reporting the hdmi/dp jack event

  [Test Case]
  On the problematic machines, we do s3 test without plugging monitor, there
  is no hdmi audio device in the sound-setting.
  On the machines without this problem, we do s3 test, pluggin/unplugging
  monitor test, the hdmi audio work well as before.

  [Regression Risk]
  Low. We have done many tests on machines with or without this problem,
  there is no regression so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827967/+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 1828948] Re: OBSOLETE_BY in DKMS.CONF not work

2019-05-14 Thread Anthony Wong
** Also affects: dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dkms (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  OBSOLETE_BY in DKMS.CONF not work

Status in DKMS:
  Confirmed
Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  New
Status in dkms source package in Bionic:
  New

Bug description:
  the issue has been fixed by upstream [1]:
  https://github.com/dell/dkms/issues/81

  we need to land that fix to DKMS on Ubuntu as well.

  [1] https://github.com/dell/dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1828948/+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 1819413] Re: [ICL] S0ix Enabling

2019-05-09 Thread Anthony Wong
** Also affects: linux-oem-osp1 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-osp1 (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
  [ICL] S0ix Enabling

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  New

Bug description:
  Description:

  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.

  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;

  (2) by runtime PM, i.e no system activities with display off.

  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.

   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine

  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM

  Both paths will require intel_idle driver support for S0ix support.

  238f9c11351f8af8534ae0318b4d9acc77b09ee8

  8aba056a4ea6da18186025a335a96b2f071e69d3

  6769fdbe27d782dfee5e459e25b44baacc7c8459

  cfb55af9add9c19806300fdb31f4cd25e67c6d1a

  4a5861f714293767980e4948c9a7c9e5e09c9b94

  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b

  cd89e92b7399a69512b8d855a2dd145c47399bf8

  d6827015e671cd17871c9b7a0fabe06c044f7470

  0e68eeea9894feeba2edf7ec63e4551b87f39621

  e50af8332785355de3cb40d9f5e8c45dbfc86f53

  Target Kernel: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819413/+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 1819413] Re: [ICL] S0ix Enabling

2019-05-09 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Tags added: icelake

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

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

Title:
  [ICL] S0ix Enabling

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:

  S0ix-states represent the residency in the Intel® SoC idle standby power 
states.
  The S0ix states shut off part of the SoC when they are not in use. The S0ix
  states are triggered when specific conditions within the SoC have been 
achieved,
  for example: certain components are in low power states. The SoC consumes the
  least amount of power in the deepest (for example, S0i3) state.

  S0ix is triggered by two paths:
  (1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
  on Android device or command manually triggered on any Linux based distros;

  (2) by runtime PM, i.e no system activities with display off.

  S0ix should simply work in theory with trigger path (1) if we have the device
  drivers ready. On GLK, we require the below PCI device drivers with system PM
  support. ACPI device requirements are WIP.

   I2C designware PCI driver
   USB XHCI PCI ID
   Intel trace Hub[NPK) PCI ID
   SPI BXT PCI ID
   SCSI UFS BXT PCI host ID
   Graphics
   Audio
   PWM
   HSUART
   Security engine

  S0ix with trigger path (2) require work as defined below.
   All the above device drivers need to support runtime PM (already defined in 
the same LCK above)
   PCI root port to support runtime PM

  Both paths will require intel_idle driver support for S0ix support.

  238f9c11351f8af8534ae0318b4d9acc77b09ee8

  8aba056a4ea6da18186025a335a96b2f071e69d3

  6769fdbe27d782dfee5e459e25b44baacc7c8459

  cfb55af9add9c19806300fdb31f4cd25e67c6d1a

  4a5861f714293767980e4948c9a7c9e5e09c9b94

  2a13096ac7da07a1bfc9d91fc4a982020e7ded2b

  cd89e92b7399a69512b8d855a2dd145c47399bf8

  d6827015e671cd17871c9b7a0fabe06c044f7470

  0e68eeea9894feeba2edf7ec63e4551b87f39621

  e50af8332785355de3cb40d9f5e8c45dbfc86f53

  Target Kernel: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819413/+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 1771252] Re: [ICL] Enable intel_rapl driver for Icelake

2019-05-09 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Tags added: icelake

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

Title:
  [ICL] Enable intel_rapl driver for Icelake

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Desription:
  This feature is intended to track intel_rapl driver enabling for IceLake.

  Commit:Powercap/intel_rapl driver enabling for Icelake

  Target Release: 19.10
  Target Kernel: 5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1771252/+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 1483095] Re: Bluetooth device 0cf3:e007 may sometimes fail to initialize

2019-05-08 Thread Anthony Wong
** Changed in: hwe-next
   Status: In Progress => Won't Fix

** Changed in: linux (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  Bluetooth device 0cf3:e007 may sometimes fail to initialize

Status in HWE Next:
  Won't Fix
Status in HWE Next vivid series:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  On cold or warm boot, sometimes this device would fail to initialize.
  An error message can be found in dmesg:

  [ 19.268671] Bluetooth: hci0: Failed to access otp area (-113)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1483095/+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 1820153] Re: [SRU][B/C/OEM]IOMMU: add kernel dma protection

2019-05-08 Thread Anthony Wong
** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  [SRU][B/C/OEM]IOMMU: add kernel dma protection

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  SRU justification:

  [Impact]
  Recent systems shipping with "kernel DMA protection" = "enabled" by default 
in BIOS. This setting option changed "Thunderbolt Security Level" = "No 
Security (SL0)".
  With this setting systems will be vulnerable to a DMA attack by a thunderbolt 
device.

  OS can use IOMMU to defend against DMA attacks from a PCI device like 
thunderbolt one.
  Intel adds DMA_CTRL_PLATFORM_OPT_IN_FLAG flag in DMAR ACPI table.
  Use this flag to enable IOMMU and use _DSD to identify untrusted PCI devices.

  [Fix]
  Enable IOMMU when BIOS supports DMA opt in flag and ExternalFacingPort in 
_DSD.
  Disable ATS on the untrusted PCI device.

  [Test]
  Tested on 2 Intel platforms that supports DMA opt in flag with a thunderbolt 
dock station.
  iommu enabled as expected with this fix.

  Verified by QA's full test with a temporary build of bionic-oem kernel.
  All test passed on one supported "DMA protection" system and one
  non-supported "DMA protection" system.

  [Regression Potential]
  Upstream fix, Verified on supported platforms, no affection on not supported 
platforms.
  Backported changes are fairly minimal.

  These patches are included in 5.0 kernel, disco is good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1820153/+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 1740231] Re: Add support for Realtek WiFi device [10ec:c821]

2019-05-07 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: Jesse Sung (wenchien) => Kai-Heng Feng (kaihengfeng)

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

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

Title:
  Add support for Realtek WiFi device [10ec:c821]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740231/+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 1809219] Re: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported

2019-05-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1809219

Title:
  Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not
  supported

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

Bug description:
  [Impact]
  Killer Wireless-1550 is not supported by Bionic kernel.

  [Fix]
  This card can be supported by adding its structs and IDs into table by below 
commit.
  0a5257bc6d89 iwlwifi: add more card IDs for 9000 series

  [Test]
  Verified wifi works after applied the commit.

  [Regression Potential]
  Low. It adds its own structs and IDs to support killer cards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809219/+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 1817848] Re: i915: Backport watermark fixes for gen9+

2019-04-22 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  i915: Backport watermark fixes for gen9+

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  5.0 fixes screen flicker issues with new panel models and on hybrid machines, 
and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ 
cherry-picked commits plus a handful of build fixes:

  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15

  [Test case]
  Various display configurations with an external monitor connected need to be 
tested, preferably on a wider set of hardware

  [Regression potential]
  The backport was done by Intel, and tested with intel-gpu-tools to do the 
right thing, but there's always a chance of regressing something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1817848/+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 1819907] Re: 19.04 installer hangs on installation complete dialog

2019-04-12 Thread Anthony Wong
A “safe graphics” mode has just been added to 19.04. It is present in
the latest daily test image, which can be found at
http://cdimage.ubuntu.com/daily-live/current/. 19.04 will be release on
Apr 18.

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

Title:
  19.04 installer hangs on installation complete dialog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed version 19.04 on a Lenovo P1 laptop and when the installation 
Complete dialog came up I hit the restart button and the system froze.  I then 
have to hard power down.  At this point it boots to a login prompt.  I login 
but there is no desktop after ten minutes or more finally reinstalled.  On 
reinstall again same freeze at install complete but this time after several 
minutes the desktop did finally show up.  Only difference on the installs was 
first time I selected the update wifi and other drivers click box and second 
time I did not.
  BIOS N2EET38W
  CPU i7-8850H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819907/+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 1819907] Re: 19.04 installer hangs on installation complete dialog

2019-04-03 Thread Anthony Wong
@Vamshee
Can you provide more details what you did and what did not work?

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

** Tags added: disco

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

Title:
  19.04 installer hangs on installation complete dialog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed version 19.04 on a Lenovo P1 laptop and when the installation 
Complete dialog came up I hit the restart button and the system froze.  I then 
have to hard power down.  At this point it boots to a login prompt.  I login 
but there is no desktop after ten minutes or more finally reinstalled.  On 
reinstall again same freeze at install complete but this time after several 
minutes the desktop did finally show up.  Only difference on the installs was 
first time I selected the update wifi and other drivers click box and second 
time I did not.
  BIOS N2EET38W
  CPU i7-8850H

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

2019-04-03 Thread Anthony Wong
@Stephan

Following comment #28, I have re-packaged linux-firmware package to
include the firmwares from the two upstreams:

[1] 
https://people.canonical.com/~ypwong/lp1818881/linux-firmware_1.173.3test1_all.deb
[2] 
https://people.canonical.com/~ypwong/lp1818881/linux-firmware_1.173.3test2_all.deb

You can grab them and use dpkg -i to install them.

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  firmware:   ath10k/QCA9887/hw1.0/board.bin
  firmware:   ath10k/QCA9887/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/board-2.bin
  firmware:   ath10k/QCA988X/hw2.0/board.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-4.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-3.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-2.bin
  license:Dual BSD/GPL
  description:

[Kernel-packages] [Bug 1822682] Re: nvidia driver issues

2019-04-01 Thread Anthony Wong
I see you mentioned GeForce 1050Ti in your bug. The commit I posted above is 
for GV100 "Volta". So the warning messages shouldn't affect you.
That said, it might be a good idea to add the relevant firmwares to Bionic.

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

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

** Also affects: linux-signed-hwe (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Also affects: linux-signed-hwe (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  nvidia driver issues

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-signed-hwe package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-signed-hwe source package in Bionic:
  New
Status in linux-firmware source package in Cosmic:
  New
Status in linux-signed-hwe source package in Cosmic:
  New

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Kernel: Linux 4.18.0-15-generic
  Intel Core i7-7700HQ + GeForce 1050Ti
  after: sudo update-initramfs -u (i'm using this command after installing 
fresh Ubuntu because it can't reboot correctly)
  I get :
  update-initramfs: Generating /boot/initrd.img-4.18.0-16-generic
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module 
nouveau

  Had no such trouble on Ubuntu 18.04.01 with older kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 00:18:33 2019
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1822682/+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 1797304] Re: Keyboard backlight sysfs sometimes is missing on Dell laptops

2019-03-28 Thread Anthony Wong
Already fixed in mainline, set to Fix Released.

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

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

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

Title:
  Keyboard backlight sysfs sometimes is missing on Dell laptops

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  When the keyboard backlight sysfs is missing, userspace does not know
  the current keyboard backlight brightness.

  [Fix]
  There's a loading order race condition, between the dell-smbios and its
  backends, dell-smbios-{smm,wmi}. 
  Build them as one module can solve the issue.

  The last patch is what we want, but pulls the entire series as a
  whole.

  [Test]
  The backlight sysfs always exists with the patch. Userspace now knows
  the current keyboard backlight brightness.

  [Regression Potential]
  Low. No functional change, as it simply links the modules together.
  Limits to Dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1797304/+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 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid

2019-03-22 Thread Anthony Wong
Worked with doko on IRC and the nvidia 418 driver (currently in
-proposed) fixes this.

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

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

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1814325] Re: Keyboard light fn does not works for Asus VivoBook S14 X430UA on Ubuntu 18.04

2019-03-21 Thread Anthony Wong
The 4.19 linux kernel can resolve this bug. You can wait for the Disco
(19.04) release and upgrade to that to get this feature.

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

Title:
  Keyboard light fn does not works for Asus VivoBook S14 X430UA on
  Ubuntu 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I started using Ubuntu in my new Asus VivoBook S14 X430UA laptop. But
  it is very disappointing that the keyboard light cannot be controlled
  using the dedicated switch (fn + f7). Similarly fn + f8 also not
  working, which is for screen toggling.

  echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness

  command to switch on the keyboard light is working fine. Is there any
  solution for this issue?

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajithabhks   1491 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  2 01:25:22 2019
  HibernationDevice: RESUME=UUID=29048cc5-d306-4844-8f70-c87fc7a20081
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:56c1 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook S14 X430UA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=911bc958-ea13-4f07-9757-ce3a56799271 ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X430UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X430UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX430UA.204:bd06/06/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookS14X430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook S
  dmi.product.name: VivoBook S14 X430UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814325/+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 1820153] Re: [SRU][B/C/OEM]IOMMU: add kernel dma protection

2019-03-20 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  [SRU][B/C/OEM]IOMMU: add kernel dma protection

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  New

Bug description:
  SRU justification:

  [Impact]
  OS can use IOMMU to defend against DMA attacks from a PCI device like 
thunderbolt one.
  Intel adds DMA_CTRL_PLATFORM_OPT_IN_FLAG flag in DMAR ACPI table.
  Use this flag to enable IOMMU and use _DSD to identify untrusted PCI devices.

  [Fix]
  Enable IOMMU when BIOS supports DMA opt in flag and ExternalFacingPort in 
_DSD.
  Disable ATS on the untrusted PCI device.

  [Test]
  Tested on 2 Intel platforms that supports DMA opt in flag with a thunderbolt 
dock station.
  iommu enabled as expected with this fix.

  [Regression Potential]
  Upstream fix, Verified on supported platforms, no affection on not supported 
platforms.
  Backported changes are fairly minimal.

  These patches are included in 5.0 kernel, disco is good.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1820153/+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 1800995] Re: [ICL] GPIO support

2019-03-19 Thread Anthony Wong
The commit is already in Disco kernel.

** Changed in: intel
   Status: New => Fix Released

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

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: linux
   Status: New => 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/1800995

Title:
  [ICL] GPIO support

Status in intel:
  Fix Released
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  GPIO support for ICL should be basically the same as in CNL.

  Reduction in minimum selectable GPIO block configuration. Allows for
  more flexibility in selecting 1.8 or 3.3V GPIOs

  Commit ID: e6800d2601fafb51f5feb3c216c884c2efb4c77d

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1800995/+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 1819907] Re: 19.04 installer hangs on installation complete dialog

2019-03-14 Thread Anthony Wong
** Tags added: lenovo

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

Title:
  19.04 installer hangs on installation complete dialog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed version 19.04 on a Lenovo P1 laptop and when the installation 
Complete dialog came up I hit the restart button and the system froze.  I then 
have to hard power down.  At this point it boots to a login prompt.  I login 
but there is no desktop after ten minutes or more finally reinstalled.  On 
reinstall again same freeze at install complete but this time after several 
minutes the desktop did finally show up.  Only difference on the installs was 
first time I selected the update wifi and other drivers click box and second 
time I did not.
  BIOS N2EET38W
  CPU i7-8850H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819907/+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 1819882] Re: [CONFIG] please enable highdpi font FONT_TER16x32

2019-03-13 Thread Anthony Wong
*** This bug is a duplicate of bug 1819881 ***
https://bugs.launchpad.net/bugs/1819881

** This bug has been marked a duplicate of bug 1819881
   [CONFIG] please enable highdpi font FONT_TER16x32

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

Title:
  [CONFIG] please enable highdpi font FONT_TER16x32

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [CONFIG] please enable highdpi font FONT_TER16x32

  This is now available in v5.0

  config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819882/+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 1715271] Re: Middle button of trackpoint doesn't work

2019-03-11 Thread Anthony Wong
** Changed in: hwe-next
   Status: Opinion => 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/1715271

Title:
  Middle button of trackpoint doesn't work

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Won't Fix

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1715271/+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 1819282] Re: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0

2019-03-10 Thread Anthony Wong
The BIOS of your machine does not support S3 and so linux just does what it's 
been told:
[0.345650] ACPI: (supports S0 S4 S5)

Your machine should enter suspend-to-idle (s2idle) instead of S3 when
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/1819282

Title:
  Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: HP Spectre x360 13" i7 2018 Gem Cut

  No s3 support and ACPI errors in dmesg:

  [0.165087] ACPI FADT declares the system doesn't support PCIe ASPM, so 
disable it
  [0.165087] ACPI: bus type PCI registered
  [0.165087] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
  [0.165087] PCI: MMCONFIG for domain  [bus 00-ff] at [mem 
0xe000-0xefff] (base 0xe000)
  [0.165087] PCI: MMCONFIG at [mem 0xe000-0xefff] reserved in E820
  [0.165087] PCI: Using configuration type 1 for base access
  [0.165256] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.165256] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [0.165256] ACPI: Added _OSI(Module Device)
  [0.165256] ACPI: Added _OSI(Processor Device)
  [0.165256] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.165256] ACPI: Added _OSI(Processor Aggregator Device)
  [0.165256] ACPI: Added _OSI(Linux-Dell-Video)
  [0.165256] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.165256] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.209836] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.XDCI], 
AE_NOT_FOUND (20181213/dswload2-160)
  [0.209841] ACPI Error: AE_NOT_FOUND, During name lookup/catalog 
(20181213/psobject-221)
  [0.209844] ACPI: Skipping parse of AML opcode: Scope (0x0010)
  [0.210311] ACPI BIOS Error (bug): Could not resolve 
[\_SB.PCI0.I2C1.TPL1], AE_NOT_FOUND (20181213/dswload2-160)
  [0.210315] ACPI Error: AE_NOT_FOUND, During name lookup/catalog 
(20181213/psobject-221)
  [0.210317] ACPI: Skipping parse of AML opcode: Scope (0x0010)
  [0.210811] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.210814] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.210816] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.210817] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.210820] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.210822] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.210823] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  ...

  Full output of many AE_ALREADY_EXISTS in attached dmesg. I am running
  v5.0.0+ (only change is the patch for the hid error reported here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+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 1804604] Re: SRU: Fix thinkpad 11e 3rd boot hang

2019-03-08 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  SRU: Fix thinkpad 11e 3rd boot hang

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  ThinkPad 11e 3rd boot hang in systemd loading.

  [Fix]
  When boot case acpi_lpss_resume() get called without a corresponding 
acpi_lpss_suspend() having been called.
  Thus force setting the flag during boot.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Booting successfully.

  [Regression Potential]
  Low,  upstream fix cherry-picked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1804604/+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 1644804] Re: [Vostro 15-3568] Right key does not work on this clickpad

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Invalid

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

Title:
  [Vostro 15-3568] Right key does not work on this clickpad

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

Bug description:
  CID: 201606-22528 Dell Vostro 15-3568

  The right key on the clickpad does not work on this laptop.

  Steps:
  1. Install 14.04.1 + dist-upgrade 
  2. Reboot and test the right key

  Result:
  * Not working at all

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1525 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 25 06:52:56 2016
  HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6
  InstallationDate: Installed on 2016-11-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 15-3568
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1644804/+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 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

2019-03-07 Thread Anthony Wong
** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1730544

Title:
  AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  From vendor's suggestion, there are some patches in v4.14-rc6 are
  required to enable the 2 NICs

  417a3ae net: aquantia: Bad udp rate on default interrupt coalescing
  b82ee71 net: aquantia: Enable coalescing management via ethtool interface
  6849540 net: aquantia: mmio unmap was not performed on driver removal
  4c8bb60 net: aquantia: Limit number of MSIX irqs to the number of cpus
  93d87b8 net: aquantia: Fixed transient link up/down/up notification
  5d8d84e net: aquantia: Add queue restarts stats counter
  65e665e net: aquantia: Reset nic statistics on interface up/down

  And to avoid conflict, cherry pick 2 more commits

  3aec641 aquantia: Fix Tx queue hangups
  65e665e net: aquantia: Reset nic statistics on interface up/down

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1730544/+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 1759188] Re: [8086:3e92] display becomes blank after S3

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  [   38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first 
message, retry
  [   38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent 
adapter i915 gmbus dpd
  [   38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
  [   38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
adaptor ID: 44 (err 0)
  [   38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 
HDMI) detected (max TMDS clock: 165000 kHz)
  [   38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] 
[CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected

  [Fix]
  This commit pointed out by Timo fixes the issue.

  [Regression Potential]
  Should be low, although the change applies broadly.
  From the patch description, it explains it should be safe.
  > This workaround was designed to minimize the impact only
  > to save the bad case with that link rates. But HW engineers
  > indicated that it should be safe to apply broadly, although
  > they were expecting the DPLL0 link rate to be unchanged on
  > runtime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759188/+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 1782540] Re: Allow Raven Ridge's audio controller to be runtime suspended

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1782540

Title:
  Allow Raven Ridge's audio controller to be runtime suspended

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  AMD Raven Ridge's audio controller doesn't get runtime suspended. It consumes 
unnecessary power.

  [Test]
  With the patch, it can get runtime suspended and save ~1W for the system.
  It can also get runtime resumed correctly when doing audio input/output.

  [Fix]
  Add AZX_DCAPS_PM_RUNTIME flag to let sound subsystem know it supports runtime 
PM.

  [Regression Potential]
  Low. This change limits to Raven Ridge's audio controller.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1782540/+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 1806335] Re: Enable new Realtek card reader

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Enable new Realtek card reader

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  USB Storage based Realtek card reader doesn't work, because the usb-storage 
module tries to use it in UAS mode instead of using "ums-realtek".

  [Fix]
  Add new IDs to ums-realtek driver.
  In addition to that, we add a new module knob, "enable_mmc=", to 
enable/disable MMC, as vendors may not pay MMC royalties. "enable_mmc" defaults 
to 1.

  [Test]
  After applying the patch, the card reader works, and verified "enable_mmc=" 
can enable/disable MMC support.

  [Regression Potential]
  Minimal. This SRU enables two specific card readers that don't work as UAS, 
the new module knob only introduces new behavior when enable_mmc=0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806335/+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 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless
  Network Adapter

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  It drains power more than 0.5 Watt after power off(S5) the machine with 
QCA9377 wifi card. The power consumption should be lower than 0.5 Watt, or it 
won't pass E-star 7.

  [Fix]
  Qualcomm provides this fix, and the power consumption becomes 0.23 Watt at 
S5. This fix doesn't submit to upstream yet, Qualcomm is still working on it.

  [Test]
  Verified on Dell machines, it works.

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805607/+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 1763594] Re: xhci hangs; reset results in NULL pointer dereference

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  xhci hangs; reset results in NULL pointer dereference

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux package in Arch Linux:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stops to work after some time. This happens when the xHC gets
  runtime resumed/suspended constantly.

  [Test]
  User reports this backport fixes the issue.

  [Fix]
  In addition to check EINT, also check ports' status.

  [Regression Potential]
  Low. It fixes a known bug and it's in -stable.

  ===Original Bug Report===

  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
    cd $xhci
    echo Resetting devices from $xhci...
    for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
    done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress algif_skcipher af_alg 

[Kernel-packages] [Bug 1779823] Re: xhci_hcd 0000:00:14.0: Root hub is not suspended

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  xhci_hcd :00:14.0: Root hub is not suspended

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Runtime suspended xHC keeps spewing out this message:
  xhci_hcd :00:14.0: Root hub is not suspended

  [Test]
  With the fix, the message stops.

  [Fix]
  Only decrement PM counter when DBC was started.

  [Regression Potential]
  Low. It fixes the overlooked logic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1779823/+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 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long
  idle

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Western Digital PC SN720 
NVMe SSD SDAPNTW-256G.

  Short idle: 5.3
  Long idle: 3.0
  S2I: 5.07

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the WD NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 1.66W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805775/+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 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  Fix Intel I210 doesn't work when ethernet cable gets plugged

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Plugging ethernet cable cannot wake up Intel I210 when it's runtime
  suspended. It's because the PME is not enabled.

  [Fix]
  PCI core doesn't enable PME because the driver explicitly saves its PCI
  state before runtime suspend routine. Don't save PCI state fixes the
  issue. 

  [Test]
  PME is correctly enabled, and cable plugging starts to work.

  [Regression Potential]
  Minimal. The fix limits to on device, and it's specific to runtime power
  management. Other functionalities are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806818/+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 1811337] Re: To reduce the Realtek USB cardreader power consumption

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  To reduce the Realtek USB cardreader power consumption

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Realtek USB cardreader consumes more than 1 Watt during long idle if it's not 
suspended. And it's runtime PM functions are available after v4.20.

  [Fix]
  To avoid conflicts, have to backport some patches for mmc core.

  [Test]
  Note: Inside () are the previous value (non-patch)
  Sort idle: 7.76W (7.88)
  Long idle: 4.658W (5.79)
  S3: 0.5W (0.5)
  S5: 0.20W (0.208)

  [Regression Potential]
  Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811337/+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 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1742094

Title:
  [16.04][classic] Redpine: wowlan feature doesn't work

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

Bug description:
  Steps to reproduce:

   1. Ensure WoWLAN is enabled in BIOS.
   2. Initiate connection to an AP (using nmcli)
   3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
   4. Enter S5/S4/S3 (using poweroff, etc.)
   5. From another computer on the same network run the following command:
  $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)

  Expected result: the device starts/resume

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742094/+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 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Enable AMD PCIe MP2 for AMDI0011

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Touchpad doesn't work on Latitude 5495.

  [Test]
  I can confirm the driver from AMD works.
  All issues found by us should be fixed.

  [Fix]
  The touchpad connects to AMDI0011, which doesn't have any driver until
  now.
  I'll backport the patch to A/B/C once it's in mainline and gets
  thoroughly tested.
   
  [Regression Potential]
  Low. It's a new driver, shouldn't affect any other device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773940/+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 1778658] Re: Nvidia fails after switching its mode

2019-03-07 Thread Anthony Wong
** 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/1778658

Title:
  Nvidia fails after switching its mode

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Switch Nvidia mode requires rebooting the system. It's because of losing some 
of its status while switching mode if runtime PM is enabled. It's a generic 
issue that would happen on some other devices, too. This patch restores 
devices' config space on runtime resume.

  [Test]
  Test and verify it on machines with Nvidia discrete graphics.

  [Fix]
  Fix by saving and restoring config space over a runtime suspend cycle even if 
the device is not bound.

  [Regression Potential]
  Low. It saves and restores states during suspending and resuming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778658/+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 1798328] Re: USB cardreader (0bda:0328) make the system can't enter s3 or hang

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1798328

Title:
  USB cardreader (0bda:0328) make the system can't enter s3 or hang

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

Bug description:
  [Impact]
  We have a couple o lenovo laptops, they have the realtek cardreader 
(0bda:0328),
  this cardreader is the latest product from realtek, and it uses the common
  usb-to-scsi driver UAS. When the system suspend and resume, the USB host will
  print some errors like can't disable the device under this USB bus and
  reset-and-verify fails, after that the system can't suspend anymore and hang
  randomly.

  [Fix]
  the mainline build v4.17-rc1 doesn't have this issue, so through bisecting,
  we found this patch can fix the problem.

  [Test Case]
  suspend and resume 30 times, and plug sd storage card into the cardreader,
  everything worked well.

  [Regression Potential]
  Low, we tested this patch on 7 different lenovo laptops. After suspending
  and resuming for 30 times, the system still worked well, and plug a usb
  storage, it still worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1798328/+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 1796789] Re: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev
  ca, 1002:15dd) often hangs randomly

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it
  switchs to amdgpufb, the system will hang randomlly, sometimes it hangs during
  boot, reboot or poweroff, sometimes it hangs with longtime standby.

  
  [Fix]
  Through bisecting, I found this patch can fix the problem, looks like without
  this patch the ATOM BIOS can't be parsed correctlly.

  
  [Test Case]
  Did the test of "boot, reboot and poweroff" 5 times, worked very well.
  Let the system standby over one night, worked very well.

  [Regression Potential]
  Very low, I tested this patch on at least 6 differnt lenovo machines
  and those machines have different AMD GPUs on them, all of them worked
  as well as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1796789/+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 1805085] Re: Fix and issue that LG I2C touchscreen stops working after reboot

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1805085

Title:
  Fix and issue that LG I2C touchscreen stops working after reboot

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  LG I2C touchscreen stops working after reboot.

  [Fix]
  Disable runtime PM for the touchscreen, which doesn't work well with 
consecutive ON/SLEEP commands.

  [Test]
  The touchscreen works well after reboot, when runtime PM is disabled.

  [Regression Potential]
  None. This is a new device and the fix is limited to this particular device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805085/+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 1806838] Re: Workaround CSS timeout on AMD SNPS 3.0 xHC

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Workaround CSS timeout on AMD SNPS 3.0 xHC

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Raven Ridge xHC may fail to suspend, causes the USB stops working, and blocks 
the system entering system-wide suspend.

  [Fix]
  It's a hardware/firmware bug, workarounded by bailing out suspend function if 
it ever fails, and reset the xHC in next resume function.

  [Test]
  After applying the patch, the USB works, and the system can enter S3 
consecutively.

  [Regression Potential]
  Minimal. This workaround only applies to AMD Raven Ridge xHC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806838/+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 1793463] Re: SRU: Enable middle button of touchpad on ThinkPad P72

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: Fix Committed => 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/1793463

Title:
  SRU: Enable middle button of touchpad on ThinkPad P72

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  ThinkPad P72 has 3 physical hardware button on touchpad.
  Middle button didn't work due to kernel mask it.

  [Fix]
  Add this button support by PNPID in kernel input driver.

  [Test Case]
  Touchpad left/right/middle buttons works fine. scroll mode
  works fine.

  [Regression Potential]
  Very low, Just enable specific hardware support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1793463/+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 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Fix I2C touchpanels' interrupt storms after system suspend

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some I2C touchpanels generate IRQ storm after system suspend/resume.

  [Test]
  After applying the fix, the IRQ storm stops generated by Raydium touchpanels.

  [Fix]
  Instead of requesting i2c reset, simply requesting the device to power on. 
The HID over I2C spec doesn't specify how the device should do upon resume from 
suspend, so some devices expect a power on instead of reset.

  [Regression Potential]
  Low. I tested other vendors' touchpanels, didn't observe any side effect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1792309/+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 1796786] Re: screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd)

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon
  Vega 8 Mobile, rev ca, 1002:15dd)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it
  switchs to amdgpufb, the screen displays abnormally, we tested with a couple 
monitors,
  all of them can reproduce this issue.

  [Fix]
  Backported 3 patches from mainline kernel, all of them focus on the change of
  disable_vga(). After applying these 3 patches, the issue disappears.

  
  [Test Case]
  boot the system, run glxgears, everything works well

  [Regression Potential]
  Very low, these patches come from upstream, and I have tested them on at 
least 6 different
  lenovo machines and those machines have different AMD GPUs on them, all of 
them worked
  as well as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1796786/+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 1781533] Re: SATA device is not going to DEVSLP

2019-03-07 Thread Anthony Wong
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1781533

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+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 1789145] Re: Microphone cannot be detected with front panel audio combo jack on HP Z8-G4 machine

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1789145

Title:
  Microphone cannot be detected with front panel audio combo jack on HP
  Z8-G4 machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  
  [Impact]
  This bug comes from OEM cert project of HP, the front mic jack can't detect
  any plug/unplug, and we can't record any sound from plugged mic. This is a
  block for OEM project.

  [Fix]
  The fix comes from Realtek, it is said that this is a power issue, after 
changing
  the capability of the pin of linein, the power will keep being on for both 
linein
  and front mic, then this issue is fixed.

  [Test Case]
  We tested plug/unplug detection and record through iphone/nokia type 
headset-mic,
  all worked well.

  [Regression Potential]
  none, this is new added quirk, and only apply to the specific machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789145/+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 1787058] Re: ThinkPad systems have no HDMI sound when using the nvidia GPU

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1787058

Title:
  ThinkPad systems have no HDMI sound when using the nvidia GPU

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Some ThinkPad systems have a power-saving feature that turns off
  Nvidia HDMI audio device in Windows, but NVidia Linux driver does not
  support this feature. As a result, HDMI audio will not work on Linux.

  A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-
  HDMI-Audio" which needs enabling in Linux kernel too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1787058/+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 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released

Bug description:
  == Impact ==
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.

  == Fix ==
  Integrate the new release from IHV.

  == Test Case ==
  Check if the device binds to a driver.

  == Risk of Regression ==
  The driver binds to certain USB IDs thus should be reasonably low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1807339/+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 1805081] Re: Add pointstick support for Cirque Touchpad

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1805081

Title:
  Add pointstick support for Cirque Touchpad

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Cirque Touchpad works but its pointstick doesn't work.

  [Test]
  With the fix the pointstick starts working.

  [Fix]
  Need to use MT_CLS_WIN_8_DUAL to let PTP driver use pointstick as a mouse.

  [Regression Potential]
  None. This is a new device and the fix is limited to this particular device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805081/+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 1808729] Re: MAC address pass through on RTL8153-BND for docking station

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1808729

Title:
  MAC address pass through on RTL8153-BND for docking station

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  A new chip RTL8153-BND on docks require to be added to the whitelist to 
support MAC address pass through.

  [Fix]
  This commit adds check for RTL8153-BND chip which is in v4.20.
  9c27369f4a13 r8152: Add support for MAC address pass through on RTL8153-BND

  [Regression Potential]
  Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't 
lead to regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1808729/+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 1810891] Re: audio output has constant noise on a Dell machine

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1810891

Title:
  audio output has constant noise on a Dell machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid

Bug description:

  [Impact]
  the audio output (headpohne, lineout and internal speaker) has constant
  noise when playing sound.

  [Fix]
  Set the pin configuration and some secret coeff registers, the noise
  disappears. This patch is written by Realtek engineer and is upstreamd
  already.

  
  [Test Case]
  play sound via internal speaker, lineout and headphone, no noise anymore.

  
  [Regression Potential]
  Very low, this patch is upstreamd for a while, no regression is reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1810891/+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 1797292] Re: The front MIC can't work on the Lenovo M715

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1797292

Title:
  The front MIC can't work on the Lenovo M715

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On the machine of Lenovo M715, there are 2 audio jacks on the front panel,
  one of them is microphone jack. When we plug a micrphone into it, the system
  can't detect this microphone and can't record sound via this microphone too.

  
  [Fix]
  Apply the quirk of ALC294_FIXUP_LENOVO_MIC_LOCATION, the alsa driver will
  assign a different name to this audio jack, then pulseaudio can handle this
  jack and everything works well.

  
  [Test Case]
  plug a microphone to this jack and record sound, system can detect the
  microphone and can record sound.

  [Regression Potential]
  Very low, this pin configuration is specific to the machine of
  M715 so far, will not affect other machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1797292/+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 1802248] Re: Disable LPM for Raydium Touchscreens

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1802248

Title:
  Disable LPM for Raydium Touchscreens

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Raydium touchscreens don't work on LPM capable platforms.

  [Test]
  Raydium touchscreens start to work with the patch.

  [Fix]
  Disable LPM for Raydium touchscreens.

  [Regression Potential]
  Low. Limits to specific Raydium touchscreens. Also, USB runtime PM
  (SeletiveSuspend) still works, so disabling LPM doesn't really increase
  power consumption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1802248/+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 1810892] Re: lineout jack can't work on a Dell machine

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1810892

Title:
  lineout jack can't work on a Dell machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  
  [Impact]
  The rear lineout jack can't work. If users plug a headphone or audio
  cable into the lineout jack, nothing happens, the audio still output
  from internal speaker. The expected behaviour is the lineout is
  active and the sound is routed to lineout jack from internal speaker.

  [Fix]
  apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the
  lineout pin to be a correct configuration value.

  
  [Test Case]
  plug headphone into the rear lineout jack, system can detect lineout
  jack is plugged and the audio output is routed to lineout jack from
  internal speaker.

  
  [Regression Potential]
  Very low, this patch is specific to one Dell machine model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1810892/+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 1789358] Re: Support Power Management for Thunderbolt Controller

2019-03-07 Thread Anthony Wong
** 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/1789358

Title:
  Support Power Management for Thunderbolt Controller

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  New TBT controllers may use Native PCIe Enumeration (i.e. just like
  other normal PCIe device listed under lspci) instead of ACPI hotplug.

  Since TBT controller stops getting unplugged from PCIe bus, it draws
  additional power.

  [Fix]
  Support runtime power management for TBT controllers, so it can be put
  to D3 to save powers.

  [Test]
  I tested and verified this patch series can make Lenovo T480's TBT
  controller enters PCI D3 at runtime.
  I also verified this series on XPS 9370 which uses ACPI hotplug, no 
regression observed.

  [Regression Potential]
  Low. Almost all TBT controllers in the wild still uses ACPI hotplug,
  this series won't affect those users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789358/+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 1811055] Re: Support new Realtek ethernet chips

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1811055

Title:
  Support new Realtek ethernet chips

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  New Realtek ethernet chips don't work.

  [Fix]
  Add new IDs to r8169.ko.

  [Test]
  The r8169 is loaded for the Realtek ethernet chip.
  It works, and I haven't seen any issues so far.
   
  [Regression Potential]
  Low. New IDs to existing driver, no functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811055/+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 1818341] Re: bluetooth discovery not working

2019-03-07 Thread Anthony Wong
If your original problem was only about bluetooth sound quality, check
the Profile shown in your Sound settings, confirm it is set to A2DP and
not HSP/HFP.

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

Title:
  bluetooth discovery not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  audio quality on my new bluetooth headphones was not ok, so I did the
  following

  sudo apt install git build-essential dkms
  git clone https://github.com/jeremyb31/newbtfix-4.15.git
  sudo dkms add ./newbtfix-4.15
  sudo dkms install btusb/4.0

  as suggested here
  
https://askubuntu.com/questions/1050304/bluetooth-is-not-working-ubuntu-18-04-lts

  then the devise discovery was not working anymore and this is what I
  have now

  $ dmesg | grep Blue
  [   14.403625] Bluetooth: Core ver 2.22
  [   14.403637] Bluetooth: HCI device and connection manager initialized
  [   14.403638] Bluetooth: HCI socket layer initialized
  [   14.403640] Bluetooth: L2CAP socket layer initialized
  [   14.403644] Bluetooth: SCO socket layer initialized
  [   17.432573] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   17.432573] Bluetooth: BNEP filters: protocol multicast
  [   17.432575] Bluetooth: BNEP socket layer initialized

  $ lspci | grep Net; lsusb
  02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  Bus 002 Device 002: ID 413c:81b6 Dell Computer Corp. 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
  Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  uname -r
  4.15.0-45-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matteo 2872 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  2 16:10:11 2019
  HibernationDevice: RESUME=UUID=ab496a2c-42ac-4236-a1ea-1569b35ffacb
  InstallationDate: Installed on 2018-08-21 (192 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude 7490
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd12/24/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818341/+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 1818381] Re: Two finger scroll does not work after hibernate

2019-03-04 Thread Anthony Wong
Jeff, please run 'apport-collect 1818381', we need more information to
diagnose the problem.

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

Title:
  Two finger scroll does not work after hibernate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Two finger scroll does not work in Chromium browser after HIBERNATION.
  I restarted Chromium browser and it did not resolve two finger scroll
  issue. I log out, then log back on. Again, it did not resolve two
  finger scroll issue. SO, I rebooted and it did resolved two finger
  scroll issue. It happened often ONLY after HIBERNATION.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818381/+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 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)

2019-03-01 Thread Anthony Wong
** No longer affects: linux (Ubuntu Xenial)

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

Title:
  Power consumption during s2idle is higher than long idle (Intel
  SSDPEKKF)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF.

  Short idle: 6
  Long idle: 2
  S2I: 4.8

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the new Intel NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 2.8W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1804588/+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 1788730] Re: TP-LINK TG-3468 network card not recognized correctly

2019-03-01 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1788730

Title:
  TP-LINK TG-3468 network card not recognized correctly

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  A few days ago purchased a couple of TP-LINK TG-3468 network cards
  (reviewed by Phoronix here:
  https://www.phoronix.com/scan.php?page=news_item=MTY2ODQ), both
  brand new, not reused. After installed them to a pc, to my surprise,
  one of them was correctly identified and the other was incorrectly
  identified as "NCube Device 8168 (rev 06)".

  After DuckDuckGoing for a while I found this kernel bud report for
  FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e
  -network-card.57734/

  IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I
  wanted to report this so it can be fixed, please let me know wich
  logs/data should I provide.

  When ran lspci -nv this is shown for the correct nic:
  03:00.0 0200: 10ec:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 27
I/O ports at e800 [size=256]
Memory at febff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdffc000 (64-bit, prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: r8169
Kernel modules: r8169

  And this for the incorrect one:
  01:00.0 0200: 10ff:8168 (rev 06)
Subsystem: 7470:3468
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c800 [size=256]
Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K]
Memory at fdefc000 (64-bit, prefetchable) [size=16K]
Capabilities: 

  1) lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  2) In regard to the package I think this is related to the kernel itself?
  3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the 
r8169 driver should be used.
  4) The network card was erroneously detected as a different one and the 
driver was not loaded by the kernel.

  Best regards.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-133-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791
  InstallationDate: Installed on 2017-12-06 (260 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-133-generic N/A
   linux-backports-modules-4.4.0-133-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-133-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-CM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788730/+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 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Anthony Wong
** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
+ 
+ ==
+ 
+ The fix for the root cause of the hang is tracked in bug 1804604.

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
  
  ==
  
- The fix for the root cause of the hang is tracked in bug 1804604.
+ The fix for the root cause of this hang issue is tracked in bug 1804604.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in kmod source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

  ==

  The fix for the root cause of this hang issue is tracked in bug
  1804604.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+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 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Anthony Wong
I have confirmed with Adam Jacobs on email that he runs latest 18.10
kernel, and his system no longer hangs after i2c_i801 is removed from
blacklist.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+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 1818152] Re: Nvidia 340

2019-02-28 Thread Anthony Wong
** Also affects: nvidia-graphics-drivers-340 (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/1818152

Title:
  Nvidia 340

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After installing NVIDIA driver, the screen brightness is freezed by
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   senne  2237 F...m pulseaudio
   /dev/snd/controlC0:  senne  2237 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Feb 28 23:00:25 2019
  InstallationDate: Installed on 2018-12-24 (66 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBook5,1
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818152/+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 1817971] Re: Ubuntu freezes and do not respond to mouseclicks or keyboard.

2019-02-28 Thread Anthony Wong
Do you hard reset when you have this problem? Can you attach
/var/log/kern.log to the bug?

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

Title:
  Ubuntu freezes and do not respond to mouseclicks or keyboard.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The mouse moves on the screen but it is not possible to click on
  anything and ctrl+alt+F1 doesn't do anything. I think it happens more
  often when VS code is open.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joakim 1857 F pulseaudio
   /dev/snd/controlC1:  joakim 1857 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:42:12 2019
  InstallationDate: Installed on 2019-02-07 (20 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7da0b25e-0d4f-48bf-8785-730733ff3aee ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4024
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X470-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817971/+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 1818025] Re: ethernet card not detected

2019-02-28 Thread Anthony Wong
Lucian, you need the 'apport' package, I believe it is in the default
installation but if you don't have it, just install it, and then run
'apport-collect 1818025'.

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

Title:
  ethernet card not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  06:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
  07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI 
Express Fast/Gigabit Ethernet controller (rev 07) Device: eth0 
-
Type:  Wired
Driver:r8169
State: unavailable
Default:   no
HW Address:28:F1:0E:27:81:D1

Capabilities:
  Carrier Detect:  yes
  Speed:   100 Mb/s

Wired Properties
  Carrier: off

  It does not see the ethernet controller card. I cannot use Wi-Fi anymore. 
Need it asap.
  Please help.
  Thank you in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818025/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-28 Thread Anthony Wong
I have confirmed with both Chad billman (cabillman) and Earle Lyons
(earlev4) through email that when running 4.15.0-45 and i2c_i801 removed
from blacklist, their touchpads still work.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1806532] Re: The line-out on the Dell Dock station can't work

2019-02-28 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in alsa-lib source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-27 Thread Anthony Wong
linux/Cosmic  should be Fix Released as the fix is already in 4.18 from
upstream.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => 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/1802135

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-27 Thread Anthony Wong
Change linux to Fix Released for the same reason.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1802168] Re: Unable to get right-click working on ThinkPad T480s

2019-02-26 Thread Anthony Wong
So there is a temporary fix in libinput (https://bit.ly/2ExTtIm) before
Benjamin's kernel fix is accepted as discussed in
https://gitlab.freedesktop.org/libinput/libinput/issues/177. That fix is
already in Disco so only need to fix Cosmic.


** Also affects: libinput (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/1802168

Title:
  Unable to get right-click working on ThinkPad T480s

Status in Linux:
  Unknown
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated to Ubuntu 18.10, I've been fighting some weird behavior of the
  touchpad. Now, right-click does not work, whatever solution I try
  within gnome-tweaks, whether relying on multi-finger tapping or not.

  Found a very very close report from RedHat, on the same model of laptop, 
around kernel 4.18, with a fix: 
https://bugzilla.redhat.com/show_bug.cgi?id=1628715
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2195 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1802168/+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 1815925] Re: wifi doesnt work.

2019-02-15 Thread Anthony Wong
The next thing to try is to find brcmfmac43430a0-sdio.txt from other
systems, and copy the file to
/lib/firmware/brcm/brcmfmac43430a0-sdio.txt and see which one works. The
following links contains brcmfmac43430a0-sdio.txt that may help you:

 * https://github.com/armbian/firmware/blob/master/brcm/brcmfmac43430a0-sdio.txt
 * http://anduin.linuxfromscratch.org/sources/linux-firmware/brcm/
 * http://jwrdegoede.danny.cz/brcm-firmware/

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

Title:
  wifi doesnt work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi card doesnt get detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 21:32:28 2019
  IwConfig: lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 009: ID 1018:1006
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1 
hid.ignore_special_drivers=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

2019-02-15 Thread Anthony Wong
So the wifi is SDIO. Do you have the file /sys/firmware/efi/efivars
/nvram-74b00bd9-805a-4d61-b51f-43268123d113? If there is,  run 'sudo cp
/sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113
/lib/firmware/brcm/brcmfmac43430a0-sdio.txt' and reboot.

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

Title:
  wifi doesnt work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi card doesnt get detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 21:32:28 2019
  IwConfig: lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 009: ID 1018:1006
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1 
hid.ignore_special_drivers=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

2019-02-14 Thread Anthony Wong
I can't find any wireless device in your PCI bus, perhaps it's on USB.
Can you attach the output of 'lsusb -v' here?

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

Title:
  wifi doesnt work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi card doesnt get detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 21:32:28 2019
  IwConfig: lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 009: ID 1018:1006
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1 
hid.ignore_special_drivers=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815925/+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 1815808] Re: Thunderbolt Ethernet high-traffic exception

2019-02-14 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1815808

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1994 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 13:54:28 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (86 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815808/+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 1814325] Re: Keyboard light fn does not works for Asus VivoBook S14 X430UA on Ubuntu 18.04

2019-02-14 Thread Anthony Wong
Looks like this feature has been added to linux kernel after v4.19.
Do you know how many levels of backlit the keyboard has?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Keyboard light fn does not works for Asus VivoBook S14 X430UA on
  Ubuntu 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I started using Ubuntu in my new Asus VivoBook S14 X430UA laptop. But
  it is very disappointing that the keyboard light cannot be controlled
  using the dedicated switch (fn + f7). Similarly fn + f8 also not
  working, which is for screen toggling.

  echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness

  command to switch on the keyboard light is working fine. Is there any
  solution for this issue?

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajithabhks   1491 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  2 01:25:22 2019
  HibernationDevice: RESUME=UUID=29048cc5-d306-4844-8f70-c87fc7a20081
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:56c1 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook S14 X430UA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=911bc958-ea13-4f07-9757-ce3a56799271 ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X430UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X430UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX430UA.204:bd06/06/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookS14X430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook S
  dmi.product.name: VivoBook S14 X430UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814325/+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 1815312] Re: Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

2019-02-14 Thread Anthony Wong
Can you undo what you have done and then try the kernel at
http://people.canonical.com/~ypwong/lp1815312 to see if it fixes the
problem?

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  Tags:  cosmic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  

[Kernel-packages] [Bug 1814806] Re: rtl8812AU_8821AU_linux

2019-02-13 Thread Anthony Wong
Closing bug per comment #3.

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

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

Title:
  rtl8812AU_8821AU_linux

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have a usb wifi Startech device that does run good in previous Kernels but 
not in kernel 4.15.0-45-generic . I used the 
https://github.com/scrivy/rtl8812AU_8821AU_linux.git  and tried to compile it 
with make and sudo make install and does not compile to work like in the 
previous kernel 4.15.0.44-generic  .
  Could it be because of security issues with this adaptor ?

  Regards

  Dave

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814806/+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 1815561] Re: touchpad not recognized

2019-02-13 Thread Anthony Wong
Can you attach dmesg output to this bug when you boot with that kernel
param added?

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

Title:
  touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 02:25:52 2019
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815561/+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 1815808] Re: Thunderbolt Ethernet high-traffic exception

2019-02-13 Thread Anthony Wong
This bug looks like similar to previous bugs such as bug 1729674, bug
1785780 and bug 1792574.

Gene, can you try running `sudo ethtool --offload  rx
off` and see if you can reproduce the issue? If so, could you attach the
output from 'lsusb -v'? Perhaps we can build a kernel for you to test.

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

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1994 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 13:54:28 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (86 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815808/+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 1815561] Re: touchpad not recognized

2019-02-13 Thread Anthony Wong
If you add hid.ignore_special_drivers=1 to the kernel command line, does
your touchpad work? You can follow
https://wiki.ubuntu.com/Kernel/KernelBootParameters on how to do that.

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

Title:
  touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 02:25:52 2019
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815561/+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 1815535] Re: 16.04 on Dell Precision shuts down during suspend if AC is unplugged

2019-02-12 Thread Anthony Wong
Are you able to find the last known good kernel in grub and boot into it
to see if the problem exist? Please also reproduce the problem and
attach your /var/log/kern.log to this bug in your next reboot. Thanks.

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

Title:
  16.04 on Dell Precision shuts down during suspend if AC is unplugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Dell Precision 5510 laptop has recent drivers for graphics. I
  installed a lot of updates this week, and I have been finding that the
  laptop shuts down in the "Suspend" state if at any point AC power is
  unplugged.

  Steps to reproduce:
  1. With laptop plugged in to AC power and Ubuntu running, use the GUI to 
enter the suspend state.
  2. With the laptop suspended, unplug AC power.
  3. Plug in AC power again.
  4. Press the ACPI power button to trigger a wake from suspend.

  Expected behavior:
  Login screen to resume the pre-suspend session.

  Actual behavior:
  Laptop goes through POST. During startup, fsck-like text flashes on the 
screen indicating that a "hard shutdown" occurred.

  What I've done:
  (I boot with GRUB from an encrypted LVM partition.) My grub config already 
has the "acpi_sleep=nonvs" option from the last time I had a suspend-related 
issue. Most online fora will recommend this as a fix, but I am still having 
these problems. I even re-ran grub-update just to be sure.

  uname -a output:
  Linux simon-Precision-5510 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 
21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  3648 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 11 15:40:27 2019
  HibernationDevice: RESUME=UUID=1c08d766-1118-4cc3-90dc-7671d83d7ae0
  InstallationDate: Installed on 2016-06-23 (963 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-142-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_sleep=nonvs quiet splash 
acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2019-01-05 (37 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

2019-02-12 Thread Anthony Wong
I don't have problem building that driver with kernel 4.15.0-45-generic.
Can you attach the error you got or post it to
https://paste.ubuntu.com/?

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

Title:
  rtl8812AU_8821AU_linux

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a usb wifi Startech device that does run good in previous Kernels but 
not in kernel 4.15.0-45-generic . I used the 
https://github.com/scrivy/rtl8812AU_8821AU_linux.git  and tried to compile it 
with make and sudo make install and does not compile to work like in the 
previous kernel 4.15.0.44-generic  .
  Could it be because of security issues with this adaptor ?

  Regards

  Dave

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814806/+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 1811755] Re: X1 Extreme: only one of the two SSDs is loaded

2019-02-05 Thread Anthony Wong
Yes, the fix will be included in the next kernel SRU, bionic-proposed
kernel will be available next week and target to be released to bionic-
updates on Feb 25.

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

Title:
  X1 Extreme: only one of the two SSDs is loaded

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

Bug description:
  [Impact]
  On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are 
  identical, then only one drive can be seen. NQN is supposed to be unique
  but some Intel drives do not follow that.

  [Fix]
  The device-supplied subnqn is ignored and one will be generated as if
  the field is empty.

  The upstream patch conflicts with a value in 'enum nvme_quirks' that we
  added in a SAUCE patch, changed that from (1<<8) to (1<<15).

  [Test]
  With this fix, both drives can be seen.

  [Regression Potential]
  The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been
  verified by the bug reporter.

  -

  I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
  256G and the other 512G with the intention of keeping the windows on
  the 256G disk and using the 512G for linux.

  When dealing with the installer, it only ever saw one of the SSDs. I
  did manged to get bionic installed on the 512, but on boot, sometimes
  it doesn't find the 512G disk and I just get a blank screen.  After a
  hard power-off, and reboot, it drops into the grub selector, and
  choosing linux, it failed again, but this time dropped into a VT.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2003 F pulseaudio
   /dev/snd/controlC0:  tim2003 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 18:53:34 2019
  InstallationDate: Installed on 2019-01-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109)
  MachineType: LENOVO 20MFCTO1WW
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2019-01-31 Thread Anthony Wong
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  

[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad

2019-01-30 Thread Anthony Wong
There is a newer linux kernel in -proposed pocket released today with
version 4.15.0-45.48, please give it a try.

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

Title:
  T480: closed lid and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After closing the lid and working with externals screens and mouse and
  keyboard, the mouse cursor jumps. The effect is caused by touchpad:
  the workaround is to completely disable it in settings.

  
  This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 
the problem was not observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:29:35 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813957/+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 1813902] Re: Lenovo Thinkpad T540p - Kernel Crash 4.15.0-44 (18.04 LTS)

2019-01-30 Thread Anthony Wong
There is a newer linux kernel in -proposed pocket released today with
version 4.15.0-45.48, should have fixed your problem, please give it a
try.

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

Title:
  Lenovo Thinkpad T540p - Kernel Crash 4.15.0-44 (18.04 LTS)

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  When notebook is in docking station the kernel crashes after bootup and logon 
in GDM.
  If notebook is in standalone mode without any external devices connected 
everything works.

  Tried to step back to Kernel 4.15.0-43-generic and everything works
  like a charm.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  # apt-cache policy linux-image-4.15.0-44-generic
  linux-image-4.15.0-44-generic:
Installed: 4.15.0-44.47
Candidate: 4.15.0-44.47
Version table:
   *** 4.15.0-44.47 500
  500 http://at.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  /var/log/syslog reports a Kernel BUG...
  Jan 30 10:18:41 bexlt036 kernel: [   34.993161] BUG: unable to handle kernel 
NULL pointer dereference at 0245
  Jan 30 10:18:41 bexlt036 kernel: [   34.993215] IP: 
intel_ddi_post_disable+0x54/0x170 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993217] PGD 0 P4D 0 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993222] Oops:  [#1] SMP PTI
  Jan 30 10:18:41 bexlt036 kernel: [   34.993225] Modules linked in: ccm 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep btusb 
btrtl btbcm cdc_mbim btintel cdc_wdm bluetooth cdc_ncm usbnet uvcvideo cdc_acm 
mii ecdh_generic joydev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek 
snd_hda_codec_generic irqbypass snd_hda_intel intel_cstate snd_hda_codec 
intel_rapl_perf snd_hda_core snd_hwdep thinkpad_acpi snd_pcm nvram rmi_smbus 
iwlmvm rmi_core input_leds videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
mac80211 snd_seq_midi
  Jan 30 10:18:41 bexlt036 kernel: [   34.993282]  videobuf2_core serio_raw 
videodev snd_seq_midi_event media iwlwifi snd_rawmidi wmi_bmof snd_seq 
rtsx_pci_ms memstick snd_seq_device cfg80211 snd_timer snd mei_me soundcore mei 
mac_hid lpc_ich shpchp ie31200_edac sch_fq_codel sunrpc parport_pc ppdev lp 
parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt 
hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i915 ahci aesni_intel 
i2c_algo_bit e1000e aes_x86_64 drm_kms_helper crypto_simd glue_helper cryptd 
psmouse syscopyarea libahci sysfillrect sysimgblt fb_sys_fops drm ptp i2c_i801 
rtsx_pci pps_core wmi video
  Jan 30 10:18:41 bexlt036 kernel: [   34.993339] CPU: 2 PID: 2890 Comm: Xorg 
Not tainted 4.15.0-44-generic #47-Ubuntu
  Jan 30 10:18:41 bexlt036 kernel: [   34.993341] Hardware name: LENOVO 
20BE00B5GE/20BE00B5GE, BIOS GMET66WW (2.14 ) 07/01/2014
  Jan 30 10:18:41 bexlt036 kernel: [   34.993375] RIP: 
0010:intel_ddi_post_disable+0x54/0x170 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993377] RSP: 0018:a739c28ef9f0 
EFLAGS: 00010297
  Jan 30 10:18:41 bexlt036 kernel: [   34.993380] RAX: 0007 RBX: 
95550026e000 RCX: c054f272
  Jan 30 10:18:41 bexlt036 kernel: [   34.993383] RDX:  RSI: 
 RDI: 95550026e000
  Jan 30 10:18:41 bexlt036 kernel: [   34.993385] RBP: a739c28efa20 R08: 
 R09: 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993387] R10: 0047 R11: 
028f R12: 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993390] R13: 95550026e000 R14: 
9554ffef8000 R15: 9554ffa62000
  Jan 30 10:18:41 bexlt036 kernel: [   34.993393] FS:  7fbfc6b5b600() 
GS:95551e28() knlGS:
  Jan 30 10:18:41 bexlt036 kernel: [   34.993395] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan 30 10:18:41 bexlt036 kernel: [   34.993398] CR2: 0245 CR3: 
0003bc132003 CR4: 001606e0
  Jan 30 10:18:41 bexlt036 kernel: [   34.993400] Call Trace:
  Jan 30 10:18:41 bexlt036 kernel: [   34.993432]  ? 
intel_dp_sink_dpms+0xbb/0xf0 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993462]  
intel_mst_post_disable_dp+0x99/0xd0 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993494]  
intel_encoders_post_disable.isra.102+0x66/0x80 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993523]  
haswell_crtc_disable+0xe8/0x150 [i915]
  Jan 30 10:18:41 

[Kernel-packages] [Bug 1813956] Re: Lenovo T480: problem with external screens

2019-01-30 Thread Anthony Wong
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  Lenovo T480: problem with external screens

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup: two external screens connected through separate DP ports and a
  docking station to a laptop Lenovo T480

  When the laptop is launched in the docking station (lid is closed) the 
screens remain off (there is information about missing signal).
  When the laptop is launched out of docking station (using only the internal 
screen), after logging to the Gnome session, connecting to the docking station: 
there is an image on two external screens. However, once the laptop is 
suspended or screensaver enabled (switch off all screens), after wakeup, all 
screens remain off.

  This bug is 4.15.0-44 kernel specific. With the previous version
  4.15.0-43 the external screens were served properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:27:50 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813956/+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 1806397] Re: acer_wmi: Unsupported machine has AMW0_GUID1, unable to load

2019-01-30 Thread Anthony Wong
Cristian, this message is harmless, kernel is just saying acer_wmi is
not to be loaded because your machine is not an Acer.

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

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

Title:
  acer_wmi: Unsupported machine has AMW0_GUID1, unable to load

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  dmesg:
  [   17.265418] acer_wmi: Unsupported machine has AMW0_GUID1, unable to load

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2647 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2647 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 10:24:35 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806397/+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 1809847] Re: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

2019-01-29 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => 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/1809847

Title:
  Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel 
4.15.0.43.64.
  There is no interrupt while plug/unplug Ethernet cable after S3, so it looks 
like a regression after 4.15.0-33.36.

  [Fix]
  Check changelog and found there are 2 commits introduced from 4.15.0-35.38 
might be suspicious
    * r8169 no internet after suspending (LP: #1779817)
  - r8169: don't use MSI-X on RTL8168g
  - r8169: don't use MSI-X on RTL8106e
  And check the upstream log and found the 2 MSI-X commits had been all 
reverted, since below commit claims it fixes the MSI-X interrupt issue which is 
already in Bionic kernel.
     083874549fdf PCI: Reprogram bridge prefetch registers on resume
  So, I reverted the 2 MSI-X commits and found the Ethernet works again after 
S3.

  [Regression Potential]
  Low, the 2 disable MSI-X commits are workarounds, and now we have proper way 
to fix the issue, so it should be fine to revert them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809847/+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 1796634] Re: [0cf3:e007] Can't turn on BT by Wireless hotkey

2019-01-29 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [0cf3:e007] Can't turn on BT by Wireless hotkey

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in Gaming Edition:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The issue has been found on new Dell laptop with DW1820 combo card(BT is 
[0cf3:e007])
  1) Use wireless hotkey to turn off WiFi/BT.
  2) Wait 5 minutes.
  3) Use wireless hotkey to turn on WiFi/BT.
  4) Wifi is back, but BT is still off
  5) Only reboot can recovery the BT state

  [Fix]
  Qualcomm releases a new firmware to fix it.

  [Regression Potential]
  Can't evaluate it, but from our verification and S3 stress test,
  there is no any issues result from the firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1796634/+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 1811807] Re: fingerprint scanner not working

2019-01-24 Thread Anthony Wong
We do not enable fingerprint reader for OEM projects. From what I see
this is more a lack of support in libfprint. There is someone who is
working on reverse engineering the protocol so that it works in
libfprint:

github project: https://github.com/nmikhailov/Validity90
github bug for 06cb:009a: https://github.com/nmikhailov/Validity90/issues/34

** Bug watch added: github.com/nmikhailov/Validity90/issues #34
   https://github.com/nmikhailov/Validity90/issues/34

** Package changed: linux (Ubuntu) => libfprint (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/1811807

Title:
  fingerprint scanner not working

Status in libfprint package in Ubuntu:
  Confirmed

Bug description:
  I have a new Thinkpad Carbon X1 Extreme and the fingerprint scanner
  does not appear to be supported.

  $ fprintd-enroll $USER
  list_devices failed: No devices available

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ian6133 F pulseaudio
   /dev/snd/controlC0:  ian6133 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Jan 15 21:29:38 2019
  MachineType: LENOVO 20MF000BUS
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=f198f923-1cae-439c-aab1-aa886fdddf29 ro quiet splash 
psmouse.synaptics_intertouch=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MF000BUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MF000BUS:pvrThinkPadX1Extreme:rvnLENOVO:rn20MF000BUS:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MF000BUS
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1811807/+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 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box

2019-01-24 Thread Anthony Wong
Pablo, do you mind opening a new bug for your problem? Need your
system's log files to see what's wrong and putting them in a new bug
will be easier to follow. Thanks.

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

Title:
  Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Won't Fix
Status in Linux:
  Unknown
Status in vivid:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux package in Fedora:
  New

Bug description:
  This device is appearing in some OEM machines, but driver is not yet
  available in mainline.

  The driver seems to be present in machines with pre-installed OS, but
  isn't available on the download-and-install versions!

  The driver that upstream is working on can be found at
  https://github.com/lwfinger/mt7630.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1220146/+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


  1   2   3   4   5   6   7   8   9   10   >