[Group.of.nepali.translators] [Bug 1849871] Re: Skip frame when buffer overflow on UVC camera

2019-10-25 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1849871

Title:
  Skip frame when buffer overflow on UVC camera

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

Bug description:
  [Impact]
  Currently to use Intel RealSense, kernel needs to be patched [1].
  This SRU is to bring one of several fixes to Ubuntu kernel. 

  "Some cameras post inaccurate frame where next frame data overlap
  it. this results in screen flicker, and it need to be prevented."

  [Fix]
  "So this patch marks the buffer error to discard the frame where
  buffer overflow."

  [Test]
  I don't have such bad device so I can't test it. By reading through the
  code, this patch seems to be correct.

  [Regression Potential]
  Low. This patch has been in the kernel tree for more than two years and
  it doesn't bring any regression. So it should be fairly safe. 

  [1] https://github.com/IntelRealSense/librealsense/blob/master/scripts
  /patch-realsense-ubuntu-lts.sh

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower

2019-08-23 Thread Kai-Heng Feng
However, for both libraries the new commits introduce ABI change, so all
packages linked against libpciaccess and libpci need to be rebuilt. So I
am not sure how feasible it is.

I'll just let the package maintainer decide.

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

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

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

** Changed in: libpciaccess (Ubuntu)
   Status: New => Invalid

** Changed in: libpciaccess (Ubuntu)
   Status: Invalid => New

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu)
     Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

** Also affects: pciutils (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libpciaccess (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-graphics-drivers (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: nvidia-graphics-drivers (Ubuntu Xenial)
   Status: New => Invalid

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1818816

Title:
  Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell
  5820 Tower

Status in libpciaccess package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in pciutils package in Ubuntu:
  Fix Released
Status in libpciaccess source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in nvidia-graphics-drivers source package in Xenial:
  Invalid
Status in pciutils source package in Xenial:
  New

Bug description:
  Hello Team,

  I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower
  over UEFI installation. I'm using Display port monitor, inorder to get
  proper display I need to download nvidia driver from ppa:graphics-
  drivers/ppa

  After install nvidia-384 and did a reboot, still no display, but can
  able to see the PCI modules conflicted

  #lspci -v 
  lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file 
or directory

  There is no issue with Ubuntu 18.04 , which is works perfectly on the
  same machine. Ubuntu 16.04 having issue. Please let me know id there
  is some issue with the running kernel or any package?

  
  Below is the environment details. 
  =

  Ubuntu 16.04.4 LTS Xenial
  Kernel - 4.15.0-46-generic

  NVIDIA Quadro P4000

  $lshw -C Display
  WARNING: you should run this program as super-user.
*-display   
 description: VGA compatible controller
 product: NVIDIA Corporation
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:65:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: vga_controller bus_master cap_list rom
 configuration: driver=nvidia latency=0
 resources: irq:29 memory:d700-d7ff memory:c000-cfff 
memory:d000-d1ff ioport:b000(size=128) memory:d800-d807

  #dpkg -l  | grep  xserver-xorg-core-hwe-16.04
  ii  xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 


  $dpkg -l | grep nvid
  ii  nvidia-384  384.130-0ubuntu0.16.04.1  
amd64NVIDIA binary driver - version 384.130
  ii  nvidia-opencl-icd-384   384.130-0ubuntu0.16.04.1  
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime0.8.2 
amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings 415.27-0ubuntu0~gpu16.04.1
amd64Tool for configuring the NVIDIA graphics driver

  #startx 
  xauth:  file /root/.Xauthority does not exist

  
  X.Org X Server 1.19.5
  Release Date: 2017-10-12
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic 
#49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7
  Build Date: 24 November 2017  09:44:25AM
  xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical supp

[Group.of.nepali.translators] [Bug 1757422] Re: Fix Runtime PM for r8169

2019-05-24 Thread Kai-Heng Feng
** No longer affects: linux (Ubuntu)

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1757422

Title:
  Fix Runtime PM for r8169

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
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:
  Won't Fix
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 stays in D0 even when no ethernet cable is plugged in. This drains
  lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0,
  1.8W when r8169 is in D3. The power saved is substantial.

  [Fix]
  Improved rumtime PM logic to let the device gets suspended (D3) when the
  port is not in used and the link is down.

  [Test Case]
  The chip version is 8168h/8111h.
  Test when no ethernet gets plugged.

  Powertop shows power consumption is roughly 5.5W.
  lspci shows the device is in D0.

  With the patch,
  The power consumption is reduced to 1.8W.
  lspci shows the device is in D3, PME# is correctly enabled.
  Plug ethernet cable can corretly wake up the device.
  Unplug the cable, the device gets suspended to D3 correctly.

  [Regression Potential]
  Medium.
  - r8169 is so ubiquitous, with lots of different chip versions. It's
hard to test all of them.
  - PCI D3 needs system firmware (ACPI) support, this might hit some
plaform bugs.
  - the code is still in v4.16-rc*, so it's not well tested by end users.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged

2019-01-15 Thread Kai-Heng Feng
igb's PME starts working on Bionic & Cosmic.

** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1806818

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

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  New

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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1773905] Re: Support UVC1.5 Camera for Xenial

2018-06-26 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1773905

Title:
  Support UVC1.5 Camera for Xenial

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

Bug description:
  ===SRU Justification===
  [Impact]
  UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get 
loaded.

  [Test]
  See if the uvcvideo module is loaded for UVC1.5 camera.
  I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese 
can use the webcam without issue.

  [Fix]
  Add UVC1.5 device id to uvcvideo. 

  [Regression Potential]
  Low. The short control message is already fixed by another commit.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

2018-06-22 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756700

Title:
  Ryzen/Raven Ridge USB ports do not work

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

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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320

2018-03-04 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: hwe-next
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1732056

Title:
  Touchpad stops working after a few seconds in Lenovo ideapad 320

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
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 Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  === SRU Justifications ===

  [Impact]
  Touchpad freezes after a brief usage.

  [Fix]
  Quote from the commit log:
  "The stale cached value written at the final stage undoes the masking.
  Fix this by re-reading the register before clearing the interrupt.

  I also spotted that the interrupt-clearing code can race against
  amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there.
  Presumably this race was leading to the loss of interrupts."

  [Test Case]
  Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and
  a new Dell Inspiron.

  [Regression Potential]
  Low. It limits to AMD laptops

  === Original Bug Report ===

  I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
  stops working a few seconds after I log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rebeca 1440 F pulseaudio
   /dev/snd/controlC0:  rebeca 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 20:03:41 2017
  InstallationDate: Installed on 2017-09-22 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago)
  dmi.bios.date: 05/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

2017-11-17 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1722719

Title:
  HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

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

Bug description:
  [Impact]
  Alps touchpad with ID 0x120A + trackpoint will not be used for mass 
production machines.
  Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will 
confuse userspace apps.

  [Fix]
  Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A device is 
no longer a MT_CLS_WIN_8_DUAL device.

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  Minimal.
  This patch is for a single device in a specific driver.

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

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1718578] Re: Support setting I2C_TIMEOUT via ioctl for i2c-designware

2017-10-31 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1718578

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

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:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

2017-08-08 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1667750

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kern

[Group.of.nepali.translators] [Bug 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

2017-04-26 Thread Kai-Heng Feng
@Carl, I burrowed a Precision 5520 and seems to be normal. Not sure what
happened on your system...

--- TLP 0.8 

+++ Processor
CPU Model  = Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz

/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu1/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu3/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu3/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu4/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu4/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu5/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu5/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu5/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu6/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu6/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu6/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu6/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/cpu7/cpufreq/scaling_driver= intel_pstate
/sys/devices/system/cpu/cpu7/cpufreq/scaling_governor  = powersave
/sys/devices/system/cpu/cpu7/cpufreq/scaling_min_freq  =   80 [kHz]
/sys/devices/system/cpu/cpu7/cpufreq/scaling_max_freq  =  390 [kHz]

/sys/devices/system/cpu/intel_pstate/min_perf_pct  = 20
/sys/devices/system/cpu/intel_pstate/max_perf_pct  = 100
/sys/devices/system/cpu/intel_pstate/no_turbo  = 0

x86_energy_perf_policy.cpu0= powersave
x86_energy_perf_policy.cpu1= powersave
x86_energy_perf_policy.cpu2= powersave
x86_energy_perf_policy.cpu3= powersave
x86_energy_perf_policy.cpu4= powersave
x86_energy_perf_policy.cpu5= powersave
x86_energy_perf_policy.cpu6= powersave
x86_energy_perf_policy.cpu7= powersave

/proc/sys/kernel/nmi_watchdog  = 0

+++ Undervolting
PHC kernel not available.


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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1672439

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

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

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c

[Group.of.nepali.translators] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

2017-03-14 Thread Kai-Heng Feng
Systemd PR: https://github.com/systemd/systemd/pull/5591

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1657553

Title:
  Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Incomplete
Status in systemd source package in Xenial:
  New

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp