[Kernel-packages] [Bug 1827752] Re: Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when using Ubuntu 19.04

2019-05-19 Thread Kai-Heng Feng
What was the kernel version that can do S3 successfully?

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

Title:
  Suspend to RAM regressions in Asus X541N laptop (VivoBook Max) when
  using Ubuntu 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04 this laptop no longer suspends to RAM
  correctly (and it would resume by itself in previous versions of
  Ubuntu). It does not matter if the lid is closed or trying to suspend
  from GUI/CLI, the laptop tries to suspend but immediately resumes back
  to the lock screen.

  Below I attached the information necessary to debug such problem
  followed from the wiki, this logs were made using the Linux mainline
  non-daily kernel 5.0.12 from the Ubuntu kernel repository.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1767808] Re: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15

2019-05-19 Thread Kai-Heng Feng
Please test Linux kernel v5.1, the fix lands there.

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

Title:
  "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated
  Graphics with Kernel 4.15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the 
boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 
Integrated Graphics (driver i915).
  In total it is 198 seconds that are lost in these timeouts during boot, more 
than 3 minutes!

  Regression is present since linux kernel 4.8 (with Ubuntu 16.04).

  To fix, explicitly disable the port with an i915 module setting with 
video=SVIDEO-1:d in the kernel command line parameter in the bootloader.
  1/ sudo gedit /etc/default/grub
  2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line
  3/ sudo update-grub

  After applying this, the system boots up much faster, there are no
  "drm ... timed out" messages.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1828084] Re: Kernel modules generated incorrectly when system is localized to a non-English language

2019-05-19 Thread Kai-Heng Feng
Is it upstream commit e46b94d228458aefc2553ee7c34ab18c2e3288e3?

What kernel versions need this commit?

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

Title:
  Kernel modules generated incorrectly when system is localized to a
  non-English language

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When LANG is set to a non-English language with the relevant language
  pack installed, Kbuild's recordmcount.pl script fails to function
  correctly when building out-of-tree kernel modules on architectures
  that do not use the C version of recordmcount (e.g. ppc64le). This can
  result in invalid kernel modules being built.

  This was due to the non-C version of recordmcount relying on parsing
  the output of objdump(1), which can be localized. This is now fixed in
  the linux-kbuild tree with the following commit:

  https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-
  kbuild.git/commit/?h=kbuild=7b6954a982e7f60af38b835db52a06afc6e4b84c

  This commit is not in the torvalds/linux.git tree yet, but it would be
  good to backport the change to the Ubuntu kernel, particularly the
  linux-headers packages that are used for building out-of-tree kernel
  modules.

  Steps to Reproduce:
  1. Set LANG to a language other than English (e.g. ja_JP.UTF-8)
  2. Make sure that the correct language pack is installed and that 
localization is working; for example, run a command expected to print an error 
message, like `cp` with no additional arguments.
  3. Install the NVIDIA GPU driver

  Actual results:
  The kernel panics when loading the nvidia-modeset kernel module.

  Expected results:
  The driver should install and load normally.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume (fails in kernel 5.0.0 but works in 4.20.17)

2019-05-19 Thread Kai-Heng Feng
It's no longer needed if the issue is fixed.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume (fails in
  kernel 5.0.0 but works in 4.20.17)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume (fails in kernel 5.0.0 but works in 4.20.17)

2019-05-19 Thread Kai-Heng Feng
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-rc1 kernel [0].

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”, and attach dmesg.

Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc1/

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume (fails in
  kernel 5.0.0 but works in 4.20.17)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu

2019-05-19 Thread Kai-Heng Feng
The usb ethernet chip in LP: #1579984 is r8153, while this Lenovo Dock
uses cdc_ether. In general this needs special driver support, where the
mechanism is opaque to us.

So please raise the issue to 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/1827961

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar to bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC
  address pass through does not work with a Lenovo Thunderbolt 3
  Workstation Dock.

  The dock's network port is recognized and working but it has its own
  MAC address even though MAC Address pass through is enabled in the
  BIOS.

  This is the dock in question:

  https://www.lenovo.com/us/en/accessories-and-monitors/top-tech
  /Thunderbolt-WS-230W-dock-US/p/40AN0230US

  and the laptop is a Lenovo P1. Debug files attached.

  
  Please let me know if further info is required.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rauer  2107 F pulseaudio
   /dev/snd/controlC1:  rauer  2107 F pulseaudio
   /dev/snd/controlC0:  rauer  2107 F pulseaudio
  CurrentDesktop: i3
  Date: Mon May  6 19:34:26 2019
  InstallationDate: Installed on 2019-04-09 (27 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20MES1WH00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET39W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES1WH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES1WH00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829514] Re: Can't boot

2019-05-18 Thread Kai-Heng Feng
Does the system boot with kernel parameter "mds=off"?

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

Title:
  Can't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey,
  after updating to linux-image-5.0.0-15-generic, I get a blackscreen of death 
forever ; while picking manually the previous linux-image-5.0.0-13-generic, I 
can loggin in my system effectively.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linux  1591 F pulseaudio
   /dev/snd/controlC1:  linux  1591 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 14:24:05 2019
  InstallationDate: Installed on 2019-05-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Sony Corporation VPCEC3C5E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d497f787-98dc-4602-8c93-04fa80fcab3c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1140Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEC3C5E:pvrC607H2FR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEC3C5E
  dmi.product.sku: N/A
  dmi.product.version: C607H2FR
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829095] Re: Keyborad backligt does not work

2019-05-17 Thread Kai-Heng Feng
Please attach output of  `ls /sys/class/leds/dell::kbd_backlight`.

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

Title:
  Keyborad backligt does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a dell XPS14 (L421X).  In releases 18.04 and lower the keyboard
  back light used to work.  However in 18.10 and 19.04 it does not

  The dell_laptop model is loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-desktop 1.431
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 15 11:44:51 2019
  InstallationDate: Installed on 2019-04-23 (21 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cmartin2046 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-23 (23 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS L421X
  NonfreeKernelModules: nvidia wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=994f28ca-26f0-46f9-9e20-27bb85872aa0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  Tags:  disco
  Uname: Linux 5.0.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: 02/08/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0T8078
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A17
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd02/08/2018:svnDellInc.:pnXPSL421X:pvrA17:rvnDellInc.:rn0T8078:rvrA00:cvnDellInc.:ct8:cvrA17:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS L421X
  dmi.product.sku: XPS L421X
  dmi.product.version: A17
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2019-05-17 Thread Kai-Heng Feng
Does acpi_listen show anything?

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck

2019-05-16 Thread Kai-Heng Feng
Sorry for the late reply. Does this happen on generic kernel?

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

Title:
  iwlwifi-29 kernel timeout queue active on fifo 2 and stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is
  down!

  Happens sometimes after a few minutes, never more than 30 minutes.
  Easy to capture journalctl when the network connection hangs. Intel
  fails on 2.4 GHz or 5 GHz, using several different AP's.

  The same system runs stable and perfect with a USB dongle Realtek
  RTL8188CUS, but I have to blacklist iwlwifi in
  /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network
  activity while simply scanning and not connected to an AP.

  I've had similar problems with this system under 17.10, but it has
  become more reproducible under 18.04. I've back-levelled the driver as
  far as possible, but they all hang the network. Because version 29
  firmware is the latest in the bionic repository, and also on the intel
  support web site, I won't confuse matters by reporting earlier ubuntu
  kernels or iwlwifi versions

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend

2019-05-16 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Killer Wireless 1525 firmware crashes on suspend

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Problem: 
  Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's 
stay on and FAN keeps running. Strangely this does not happen in Fedora 29 
(Kernel 4.18 & same board firmware)

  System:
  Ubuntu 19.04 
  Kernel 5.0.0-13-generic
  Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1)
  Wireless info:
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 20
 serial: 40:b8:9a:ca:2b:99
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 
ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:32 memory:f680-f69f

  
  My attempts:
  1. Tried other kernels:
  5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114

  2. Tried several distro's based on ubuntu -> all have the same issue

  3. Checked firmware from Fedora 29 (md5sum was equal) and updated
  firmware (not available, using latest)

  4. Created systemd scripts for disabling & enabling the driver, this causes 
the same crashes in /var/log/syslog
  See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11

  5. Physically replaced Killer 1525 with Intel 8260 --> problem is
  gone, standby works perfectly

  Of course i want to be able to use the 1525, so please help me solve the 
issue.
  Happy to perform additional debugging if required.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829310] Re: kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720

2019-05-15 Thread Kai-Heng Feng
Please test upstream stable kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.16/

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

Title:
  kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux kernel 5.0.0-13
  Kubuntu 19.04
  hardware: old Dell laptop Inspiron 1720

  After upgrading an old Dell laptop Inspiron 1720 (from 2007 I think) from 
Kubuntu 18.10 to 19.04, the result is a broken system:
  booting takes + 5 minutes
  looking at the boot messages I see "Failed to start Dispatcher daemon for 
systemd-networkd" and consequently Network Manager fails to run.
  Eventually it reaches the desktop where it takes another 5 minutes to display 
the panel.
  In a terminal it fails to execute any network command (ifconfig, ip) as well 
as "sudo" and "lshw".

  If I boot with the previous kernel, the 4.18.0-18 of Kubuntu 18.10, it works 
without problem.
  For now I have set its grub to start by default the 4.18 kernel instead of 
the 5.0 one.

  I tried running "apport-cli -f -p linux --save
  kernel5.0onOldDellInspiron1720.apport" but that has been spitting out
  periods ("") for 10 minutes now and still hasn't finished.

  dmesg output attached.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829310] Re: kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720

2019-05-15 Thread Kai-Heng Feng
This is fixed in mainline, but not sure if upstream stable have this fix or not.
[   48.065638] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310
[   48.065641] Code: 4c 8b 45 a8 4c 8b 1d af c7 a9 01 89 d3 45 31 d2 44 8b 4d 
a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c 
a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f
[   48.065643] RSP: 0018:bed680f6b3c0 EFLAGS: 00010016
[   48.065646] RAX: 0001 RBX:  RCX: 
[   48.065648] RDX:  RSI: 001f RDI: 0001
[   48.065650] RBP: bed680f6b420 R08: 0001 R09: 0001
[   48.065652] R10:  R11:  R12: 
[   48.065653] R13:  R14: 0001 R15: 0020
[   48.065656] FS:  7f9e750f16c0() GS:96d53da0() 
knlGS:
[   48.065659] CS:  0010 DS:  ES:  CR0: 80050033
[   48.065661] CR2:  CR3: 73114000 CR4: 06f0
[   48.065662] Call Trace:
[   48.065669]  swiotlb_map+0x6c/0x1c0
[   48.065673]  dma_direct_map_page+0xc5/0x160
[   48.065679]  b44_alloc_rx_skb+0x18e/0x3f0 [b44]
[   48.065683]  b44_init_rings+0xbe/0x1b0 [b44]
[   48.065686]  b44_open+0xfc/0x3f0 [b44]
[   48.065691]  __dev_open+0xd4/0x170
[   48.065694]  __dev_change_flags+0x18f/0x200
[   48.065698]  dev_change_flags+0x27/0x60
[   48.065701]  do_setlink+0x31c/0xe30
[   48.065707]  ? __nla_parse+0x38/0x120
[   48.065710]  __rtnl_newlink+0x531/0x910
[   48.065715]  ? update_load_avg+0x4b6/0x590
[   48.065719]  ? __alloc_pages_nodemask+0x13f/0x2e0
[   48.065726]  ? _cond_resched+0x19/0x30
[   48.065730]  ? kmem_cache_alloc_trace+0x153/0x1d0
[   48.065732]  rtnl_newlink+0x48/0x70
[   48.065735]  rtnetlink_rcv_msg+0x213/0x300
[   48.065737]  ? rtnl_calcit.isra.31+0x100/0x100
[   48.065741]  netlink_rcv_skb+0x4f/0x120
[   48.065744]  rtnetlink_rcv+0x15/0x20
[   48.065746]  netlink_unicast+0x1a1/0x260
[   48.065749]  netlink_sendmsg+0x20d/0x3c0
[   48.065753]  sock_sendmsg+0x3e/0x50
[   48.065756]  ___sys_sendmsg+0x295/0x2f0
[   48.065758]  ? sock_destroy_inode+0x2f/0x40
[   48.065762]  ? destroy_inode+0x3e/0x60
[   48.065764]  ? evict+0x139/0x1a0
[   48.065767]  ? iput+0x148/0x210
[   48.065769]  ? _cond_resched+0x19/0x30
[   48.065772]  ? __dentry_kill+0x124/0x170
[   48.065775]  ? dentry_kill+0x52/0x1a0
[   48.065778]  __sys_sendmsg+0x5c/0xa0
[   48.065781]  __x64_sys_sendmsg+0x1f/0x30
[   48.065785]  do_syscall_64+0x5a/0x110
[   48.065788]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

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

Title:
  kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux kernel 5.0.0-13
  Kubuntu 19.04
  hardware: old Dell laptop Inspiron 1720

  After upgrading an old Dell laptop Inspiron 1720 (from 2007 I think) from 
Kubuntu 18.10 to 19.04, the result is a broken system:
  booting takes + 5 minutes
  looking at the boot messages I see "Failed to start Dispatcher daemon for 
systemd-networkd" and consequently Network Manager fails to run.
  Eventually it reaches the desktop where it takes another 5 minutes to display 
the panel.
  In a terminal it fails to execute any network command (ifconfig, ip) as well 
as "sudo" and "lshw".

  If I boot with the previous kernel, the 4.18.0-18 of Kubuntu 18.10, it works 
without problem.
  For now I have set its grub to start by default the 4.18 kernel instead of 
the 5.0 one.

  I tried running "apport-cli -f -p linux --save
  kernel5.0onOldDellInspiron1720.apport" but that has been spitting out
  periods ("") for 10 minutes now and still hasn't finished.

  dmesg output attached.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829228] Re: boot time is too long

2019-05-15 Thread Kai-Heng Feng
Does this issue happen on 16.04?

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

Title:
  boot time is too long

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  boot time is too long and running HD videos starts flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 15 17:25:35 2019
  DistUpgraded: 2018-09-28 10:50:13,399 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-48-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:39c7]
 Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:39c7]
  InstallationDate: Installed on 2018-03-31 (409 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=998b8ab4-3e79-4347-99f7-06c2fadbd335 ro quiet splash noresume 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (229 days ago)
  dmi.bios.date: 10/23/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN36WW:bd10/23/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue May 14 07:06:58 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

2019-05-15 Thread Kai-Heng Feng
nils,

Does mainline kernel still have this issue?

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

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

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  Ethernet interface are 100% good hardware wise and can work properly.
  CentOS 7.4 uses NetworkManager as the default for managing the
  Ethernet interface.

  The only reason I'm using Ubuntu Server 18.04 on this motherboard is
  because of a specific package that Ubuntu has a newer packaged version
  than CentOS. CentOS is extremely stable when it comes to basic server
  functionality.

  Hopefully, this bug with the I219-V Ethernet interface using the
  e1000e drive for Linux can be verified and a fix rolled out.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1785715] Re: ubuntu hynix ssd I/O Errors after some minutes

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

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

Title:
  ubuntu hynix ssd I/O Errors after some minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Maybe similar to Bug 1678184
  Im working on ubuntu 18.04 (with Kernel 4.15.0-29-generic) on a dell XPS 
15-9560
  After 20 - 180 Minutes the graphical interface hangs up (i can switch 
workspaces, but not much else) and entering commands like "ls" yields bash: 
input/output error
  Reboot is impossible via the command or the button. Short click on power 
button gives me a TTY like view prompting errors for nvme0 ext4 file system 
errors (i will post more exact text on next hangup)

  The hangups appear randomly, but often during shutting the lid or plugging in 
power cable, which makes me thing it might be something with ssd power states.
  For that reason i added grub parameters like 
"nvme_core.default_ps_max_latency_us=3000" (see Bug 1678184) and ended up fully 
disabling APST by setting it to 0, but the bug still occured.

  sudo nvme id-ctrl /dev/nvme0 yields:
  NVME Identify Controller:
  vid : 0x1c5c
  ssvid   : 0x1c5c
  sn  : EJ75N621210105PBR   
  mn  : PC300 NVMe SK hynix 1TB 
  fr  : 20005A00
  rab : 1
  ieee: ace42e
  cmic: 0
  mdts: 5
  cntlid  : 0
  ver : 10200
  rtd3r   : 90f560
  rtd3e   : ea60
  oaes: 0
  ctratt  : 0
  oacs: 0x16
  acl : 3
  aerl: 3
  frmw: 0x16
  lpa : 0x2
  elpe: 254
  npss: 4
  avscc   : 0x1
  apsta   : 0x1
  wctemp  : 361
  cctemp  : 363
  mtfa: 0
  hmpre   : 0
  hmmin   : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs   : 0
  edstt   : 60
  dsto: 1
  fwug: 0
  kas : 0
  hctma   : 0
  mntmt   : 0
  mxtmt   : 0
  sanicap : 0
  hmminds : 0
  hmmaxd  : 0
  sqes: 0x66
  cqes: 0x44
  maxcmd  : 0
  nn  : 1
  oncs: 0x1e
  fuses   : 0
  fna : 0
  vwc : 0x1
  awun: 255
  awupf   : 0
  nvscc   : 1
  acwu: 0
  sgls: 0
  subnqn  : 
  ioccsz  : 0
  iorcsz  : 0
  icdoff  : 0
  ctrattr : 0
  msdbd   : 0
  ps0 : mp:5.87W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps1 : mp:2.40W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps2 : mp:1.90W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps3 : mp:0.1000W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps4 : mp:0.0060W non-operational enlat:1000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-

  
  sudo nvme get-feature -f 0x0c -H /dev/nvme0 yields:
  get-feature:0xc (Autonomous Power State Transition), Current value:
Autonomous Power State Transition Enable (APSTE): Disabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
... and so on ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  revisor1593 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1bc0493d-0592-40d4-b0f4-938fbe12a990
  InstallationDate: Installed on 2018-07-12 (25 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 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=70377f6e-8c1c-4316-bded-c738410879ab ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev

[Kernel-packages] [Bug 1829220] Re: Add in-kernel support for Realtek 8821CE WiFi device

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

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

Title:
  Add in-kernel support for Realtek 8821CE WiFi device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  There's no in-kernel support for rtl8821ce.

  [Fix]
  Include the driver to kernel.

  [Test Case]
  The basic function like scan, connect and transmit packet works.

  [Regression Potential]
  None. It's a new driver.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829220] Re: Add in-kernel support for Realtek 8821CE WiFi device

2019-05-15 Thread Kai-Heng Feng
** Attachment added: 
"rtl8821CE_WiFi_linux_v5.2.5.2.1_30816.20190425_COEX20170310-1212.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829220/+attachment/5263936/+files/rtl8821CE_WiFi_linux_v5.2.5.2.1_30816.20190425_COEX20170310-1212.tar.xz

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

Title:
  Add in-kernel support for Realtek 8821CE WiFi device

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  There's no in-kernel support for rtl8821ce.

  [Fix]
  Include the driver to kernel.

  [Test Case]
  The basic function like scan, connect and transmit packet works.

  [Regression Potential]
  None. It's a new driver.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1829220] [NEW] Add in-kernel support for Realtek 8821CE WiFi device

2019-05-15 Thread Kai-Heng Feng
Public bug reported:

[Impact]
There's no in-kernel support for rtl8821ce.

[Fix]
Include the driver to kernel.

[Test Case]
The basic function like scan, connect and transmit packet works.

[Regression Potential]
None. It's a new driver.

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

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

Title:
  Add in-kernel support for Realtek 8821CE WiFi device

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  There's no in-kernel support for rtl8821ce.

  [Fix]
  Include the driver to kernel.

  [Test Case]
  The basic function like scan, connect and transmit packet works.

  [Regression Potential]
  None. It's a new driver.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-15 Thread Kai-Heng Feng
I filed a new bug to track the SRU status: #1829220

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

-- 
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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-05-15 Thread Kai-Heng Feng
That's just a warning which got fixed in later release. Does it affect
network connection?

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1827725] Re: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386)

2019-05-14 Thread Kai-Heng Feng
Does it also happen to -generic kernel?

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

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

Title:
  linux-image-4.15.0-48-lowlatency doesn't boot after update
  (16.04)(i386)

Status in linux package in Ubuntu:
  New

Bug description:
  Currently I am on 4.15.0-47-lowlatency.
  I will attach kern.log if ubuntu-bug didn't it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18
  Uname: Linux 4.15.0-47-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat May  4 16:49:24 2019
  InstallationDate: Installed on 2018-10-01 (214 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1827677] Re: Resume from suspend: nothing on display, unable to login

2019-05-14 Thread Kai-Heng Feng
Does it work on previous kernels?

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

Title:
  Resume from suspend: nothing on display, unable to login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is 4.15.0-47-generic on a Dell Latitude 5580.  Closing the laptop
  lid will suspend the system, and opening it will resume, and I
  normally get my xfce session or the xscreensaver unlock dialog.  I
  recently suspended in this manner, but upon opening the laptop lid,
  nothing came up on the display.  The power button was on, and the
  keyboard backlight responded to keypresses.  Ctrl-Alt-PrtScr-[REISUB]
  had no discernible effect (PrtScr because I don't have SysRq on this
  keyboard).  Neither did Ctrl-Alt-Del or Ctrl-Alt-F1 for a console.  I
  needed to poweroff and poweron the laptop which of course caused the
  suspended session state to be lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May  3 16:25:37 2019
  HibernationDevice: RESUME=UUID=e77712df-7257-41aa-8062-076791733f67
  InstallationDate: Installed on 2017-12-12 (507 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Dell Inc. Latitude 5580
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash nouveau.modeset=0 pci=nomsi 
iommu=soft resume=/dev/disk/by-uuid/e77712df-7257-41aa-8062-076791733f67 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-30 (185 days ago)
  dmi.bios.date: 09/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.4
  dmi.board.name: 0FH6CJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: L05248
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.4:bd09/12/2017:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5580
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-05-13 Thread Kai-Heng Feng
Comment #35.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1828604] Re: Lenovo T490S and X390 GM do not have Firefox.App store install errors out

2019-05-10 Thread Kai-Heng Feng
** Package changed: linux (Ubuntu) => snapd (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/1828604

Title:
  Lenovo T490S and X390 GM do not have Firefox.App store install errors
  out

Status in snapd package in Ubuntu:
  New

Bug description:
  The new GM Images for T490S and X390 do not have Firefox preinstalled.
  When I try to install from the Appstore, it errors out "Firefox : too
  early for operation, device not yet seeded or device model not
  acknowledged."

  If I install using apt-get install firefox it seemed to install fine.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1828568] Re: Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless acpi=off and noapic

2019-05-10 Thread Kai-Heng Feng
Please try Safe Graphics mode in Disco live USB.

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

Title:
  Ubuntu 18.04.2 LTS amd64 installer hangs shortly after boot unless
  acpi=off and noapic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting an Ubuntu 18.04.2 LTS amd64 installer USB on a Clevo P650RE3
  results in a hang shortly after the desktop is presented, unless
  acpi=off and noapic (or nolapic) are given as kernel boot parameters.
  The same installer runs without issue on other machines and the 16.04
  installer runs without issue on the P650RE3.

  Without passing acpi=off and noapic, a desktop comes up and a terminal
  can be obtained, but keystrokes and mouse clicks are not responded to
  after a small number of seconds. The mouse pointer continues to move
  with trackpad input.

  With careful timing I was able to obtain, uname, dmidecode and (an
  empty) lspci output. I was not able to obtain any /proc/acpi
  information, but do have dmesg. These are all attached. With acpi=off
  and noapic, I can get lspci and dmidecode output, but obviously no
  /proc/acpi. In this case the lspci output is not impty and dmidecode
  is identical to the failing case.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1785715] Re: ubuntu hynix ssd I/O Errors after some minutes

2019-05-10 Thread Kai-Heng Feng
Do you still see this 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/1785715

Title:
  ubuntu hynix ssd I/O Errors after some minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Maybe similar to Bug 1678184
  Im working on ubuntu 18.04 (with Kernel 4.15.0-29-generic) on a dell XPS 
15-9560
  After 20 - 180 Minutes the graphical interface hangs up (i can switch 
workspaces, but not much else) and entering commands like "ls" yields bash: 
input/output error
  Reboot is impossible via the command or the button. Short click on power 
button gives me a TTY like view prompting errors for nvme0 ext4 file system 
errors (i will post more exact text on next hangup)

  The hangups appear randomly, but often during shutting the lid or plugging in 
power cable, which makes me thing it might be something with ssd power states.
  For that reason i added grub parameters like 
"nvme_core.default_ps_max_latency_us=3000" (see Bug 1678184) and ended up fully 
disabling APST by setting it to 0, but the bug still occured.

  sudo nvme id-ctrl /dev/nvme0 yields:
  NVME Identify Controller:
  vid : 0x1c5c
  ssvid   : 0x1c5c
  sn  : EJ75N621210105PBR   
  mn  : PC300 NVMe SK hynix 1TB 
  fr  : 20005A00
  rab : 1
  ieee: ace42e
  cmic: 0
  mdts: 5
  cntlid  : 0
  ver : 10200
  rtd3r   : 90f560
  rtd3e   : ea60
  oaes: 0
  ctratt  : 0
  oacs: 0x16
  acl : 3
  aerl: 3
  frmw: 0x16
  lpa : 0x2
  elpe: 254
  npss: 4
  avscc   : 0x1
  apsta   : 0x1
  wctemp  : 361
  cctemp  : 363
  mtfa: 0
  hmpre   : 0
  hmmin   : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs   : 0
  edstt   : 60
  dsto: 1
  fwug: 0
  kas : 0
  hctma   : 0
  mntmt   : 0
  mxtmt   : 0
  sanicap : 0
  hmminds : 0
  hmmaxd  : 0
  sqes: 0x66
  cqes: 0x44
  maxcmd  : 0
  nn  : 1
  oncs: 0x1e
  fuses   : 0
  fna : 0
  vwc : 0x1
  awun: 255
  awupf   : 0
  nvscc   : 1
  acwu: 0
  sgls: 0
  subnqn  : 
  ioccsz  : 0
  iorcsz  : 0
  icdoff  : 0
  ctrattr : 0
  msdbd   : 0
  ps0 : mp:5.87W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps1 : mp:2.40W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps2 : mp:1.90W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps3 : mp:0.1000W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps4 : mp:0.0060W non-operational enlat:1000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-

  
  sudo nvme get-feature -f 0x0c -H /dev/nvme0 yields:
  get-feature:0xc (Autonomous Power State Transition), Current value:
Autonomous Power State Transition Enable (APSTE): Disabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
... and so on ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  revisor1593 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1bc0493d-0592-40d4-b0f4-938fbe12a990
  InstallationDate: Installed on 2018-07-12 (25 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 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=70377f6e-8c1c-4316-bded-c738410879ab ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-29-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/05/2018
  dmi.bios.vendor: Dell Inc.
  

[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB 
devices
  author: Qualcomm Atheros
  srcversion: D49EBAB0107B6CE28383BB8
  alias:  pci:v168Cd0050sv*sd*bc*sc*i*
  alias:  pci:v168Cd0042sv*sd*bc*sc*i*
  alias:  pci:v168Cd0046sv*sd*bc*sc*i*
  alias:  pci:v168Cd0056sv*sd*b

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

2019-05-10 Thread Kai-Heng Feng
Comment #25?

And V2 here: https://lkml.org/lkml/2019/4/30/213

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep)
  Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done.
  Apr 02 13:39:59 taplop 

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2019-05-09 Thread Kai-Heng Feng
Lucas,
Do you still have this issue on mainline kernel?

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 

[Kernel-packages] [Bug 1738263] Re: Touchpad not working and locking CPU

2019-05-09 Thread Kai-Heng Feng
Luke, please test this kernel:
https://people.canonical.com/~khfeng/lp1738263/

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

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Notebook: ASUS GL703VD
  Touchpad: probably ELAN clickpad

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

  the multitouch hid module take almost 100% of cpu and the mouse cursor
  moves badly (loosing it for a second or 2 then resuming) also feature
  clicks and doubleclicks and sensitivity problems.

  doing rmmod hid-multitouch.ko (or rmmod multitouch_hid) and
  blacklisting the module solves the cpu problem but obviously the
  touchoad is dead.

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

  (the touchpad works perfectly in windows 10 by the way)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1579410] Re: Cannot suspend HP ProLiant SE316M1R2

2019-05-08 Thread Kai-Heng Feng
So it's not something fixable...

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

Title:
  Cannot suspend HP ProLiant SE316M1R2

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  pm-suspend does not work on HP ProLiant SE316M1R2 system.

  I am not sure if hardware actually supports that though, but there is
  kernel crash (see syslog.txt attached with Call Trace) which maybe is
  the cause.

  Monitor goes off for few seconds but after that system resumes and
  works as before.

  Also, some interesting lines:

  May  7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): 
hpsa_suspend+0x0/0x10 [hpsa] returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): 
pci_pm_freeze+0x0/0xe0 returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0 
failed to freeze async: error -38s2disks

  These lines also appears when using s2disk.

  s2ram gives:

  KMS graphics driver is in use, skipping quirks.
  s2ram_do: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sat May  7 20:55:52 2016
  HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3
  InstallationDate: Installed on 2015-10-12 (208 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: HP ProLiant SE316M1R2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago)
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: HP
  dmi.bios.version: R02
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant SE316M1R2
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826858] Re: XPS 9343 System freezes requiring hard reset

2019-05-08 Thread Kai-Heng Feng
Maybe this can help
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/comments/42?

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

Title:
  XPS 9343 System freezes requiring hard reset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to disco I have started having regular freezes of my
  laptop. There is no response to key presses, mouse movement etc. Only
  recourse is to reset the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 29 11:13:13 2019
  HibernationDevice: RESUME=UUID=e76f9b75-a3b2-48c0-931f-7af49bda53bb
  InstallationDate: Installed on 2019-01-06 (112 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-13 (15 days ago)
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.sku: 0665
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-05-08 Thread Kai-Heng Feng
FWIW this is the (not upstreamed yet) patch to solve the issue:
https://lkml.org/lkml/2019/4/30/213

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-05-08 Thread Kai-Heng Feng
"nomodeset" is just a way to check if the panel is intact. It disables
Intel graphics driver, so you'll lose all graphics acceleration by doing
that.

It'll also drastically increase the power consumption of your laptop.

Let's wait for Intel graphics maintainer's reply.

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat

2019-05-08 Thread Kai-Heng Feng
Sorry for not following up here, I've been quite busy recently.

So there are two bugs here - the first one, strcat overflow, is solved
by my test kernel or by your patch.

Though I am not sure it's totally correct, I'll raise my concern on
mailing list.

The second bug, null pointer dereference, requires more investigation.

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

Title:
  cifs set_oplock buffer overflow in strcat

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 18.04.2 LTS
  Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM

  top - 12:39:53 up  3:41,  4 users,  load average: 66.19, 64.06, 76.90
  Tasks: 1076 total,   1 running, 675 sleeping,  12 stopped,   1 zombie
  %Cpu(s): 28.2 us,  0.3 sy,  0.0 ni, 71.5 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 
st
  KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache
  KiB Swap:   999420 total,   999420 free,0 used. 33477683+avail Mem


  We've seen the following bug many times since we introduced new
  machines running Ubuntu 18. Wasn't an issue older machines running
  Ubuntu 16. Three different machines are affected, so it's rather not a
  hardware issue.

  
  | detected buffer overflow in strcat
  | [ cut here ]
  | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052!
  | invalid opcode:  [#1] SMP PTI
  | Modules linked in: [...]
  | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018
  | RIP: 0010:fortify_panic+0x13/0x22
  |  [...]
  | Call Trace:
  |  smb21_set_oplock_level+0x147/0x1a0 [cifs]
  |  smb3_set_oplock_level+0x22/0x90 [cifs]
  |  smb2_set_fid+0x76/0xb0 [cifs]
  |  cifs_new_fileinfo+0x259/0x390 [cifs]
  |  ? smb2_get_lease_key+0x40/0x40 [cifs]
  |  ? cifs_new_fileinfo+0x259/0x390 [cifs]
  |  cifs_open+0x3db/0x8d0 [cifs]
  |  [...]

  (Full dmesg output attached)

  After hitting this bug there are many cifs related dmesg entries,
  processes lock up and eventually the systems freezes.

  
  The share is mounted using:
  //server/share  /mnt/server/ cifs 
defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks

  Currently we're testing the cifs mount options "cache=none" as the bug
  seems to be oplock related.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

2019-05-08 Thread Kai-Heng Feng
Can you try "nomodeset" kernel parameter?

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824520] Re: Unable to turn off the airplane mode with wireless key on Dell M3800

2019-05-06 Thread Kai-Heng Feng
This is fixed in Disco. Cosmic needs to be fixed though.

** Package changed: linux (Ubuntu) => systemd (Ubuntu)

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

** Also affects: systemd (Ubuntu Cosmic)
   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/1824520

Title:
  Unable to turn off the airplane mode with wireless key on Dell M3800

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Cosmic:
  New

Bug description:
  The airplane mode can be activated with the wireless key combination on this 
laptop (fn + PrtScn)
  You will see the "Airplane mode enabled" notification, and the BT / Wireless 
turned off accordingly.

  However the same key combination cannot turn the wireless back on.
  You will see the "Airplane mode disabled" notification followed by the 
"Airplane mode enabled" message. 

  It feels a bit like a repeat-key issue.
  But the evtest shows the identical result:

  * Turn on the airplane mode:
  Event: time 1555070280.383302, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1
  Event: time 1555070280.383302, -- SYN_REPORT 
  Event: time 1555070280.383327, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0
  Event: time 1555070280.383327, -- SYN_REPORT 

  * Turn off the airplane mode:
  Event: time 1555070325.562502, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1
  Event: time 1555070325.562502, -- SYN_REPORT 
  Event: time 1555070325.562514, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0
  Event: time 1555070325.562514, -- SYN_REPORT 

  dmesg for turning on the airplane mode:
  Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Starting Load/Save RF Kill 
Switch Status...
  Apr 12 08:03:53 u-Dell-Precision-M3800 kernel: [ 1229.634982] wlp6s0: 
deauthenticating from 18:9c:5d:31:3f:e0 by local choice (Reason: 
3=DEAUTH_LEAVING)
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4574] manager: rfkill: WiFi now disabled by radio killswitch
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4581] device (wlp6s0): state change: activated -> unavailable 
(reason 'none', sys-iface-state: 'managed')
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4590] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 
6521
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4590] dhcp4 (wlp6s0): state changed bound -> done
  Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Started Load/Save RF Kill 
Switch Status.
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: wlp6s0: 
CTRL-EVENT-DISCONNECTED bssid=18:9c:5d:31:3f:e0 reason=3 locally_generated=1
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface 
wlp6s0.IPv6 no longer relevant for mDNS.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS 
multicast group on interface wlp6s0.IPv6 with address fe80::bb23:69c3:d7b9:f6df.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface 
wlp6s0.IPv4 no longer relevant for mDNS.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS 
multicast group on interface wlp6s0.IPv4 with address 10.101.46.102.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address 
record for fe80::bb23:69c3:d7b9:f6df on wlp6s0.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address 
record for 10.101.46.102 on wlp6s0.
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft 
blocked
  Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot 
reach: https://daisy.ubuntu.com
  Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] offline
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft 
blocked
  Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot 
reach: https://daisy.ubuntu.com
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u

[Kernel-packages] [Bug 1826549] Re: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0 (but kernel 4.18 works)

2019-05-06 Thread Kai-Heng Feng
It's in mainline and stable so it'll be in Ubuntu's 5.0 kernel soon.

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

Title:
  Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with
  Linux kernel 5.0 (but kernel 4.18 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse
  wheel does not work any more. My mouse is Microsoft Wireless Optical
  Mouse 2000. The mouse is connected to USB port via wireless receiver
  (Microsoft Wireless Mouse Receiver v1.0).

  
  I've found that problem is related to new Linux kernel 5.0. When I boot with 
previous kernel 4.18 all works good.

  The problem is reproducible with xorg and with wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 15:23:34 2019
  DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2017-09-12 (591 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
   Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: Z270 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826581] Re: Slow wired Ethernet Realtek 8118

2019-05-06 Thread Kai-Heng Feng
What's the network speed if r8169 is used instead of r8168 under
Manjaro?

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

Title:
  Slow wired Ethernet Realtek 8118

Status in linux package in Ubuntu:
  Confirmed
Status in r8168 package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  Using the latest kernel 5.0.0-13 my network is slower. My MB is a Gigabyte 
B360M-DS3H (Realtek 8118 chipset)

  I got ~22Mbps down on speedtest @1000 (i can reach up to 400Mbps)
  But if i sudo ethtool -s enp3s0 speed 100 duplex full i get up to 92Mbps

  jeanmarc@astrolabe:~$ sudo lshw -class network 
  [sudo] Mot de passe de jeanmarc : 
*-network 
 description: Ethernet interface
 produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 fabriquant: Realtek Semiconductor Co., Ltd.
 identifiant matériel: 0
 information bus: pci@:03:00.0
 nom logique: enp3s0
 version: 16
 numéro de série: e0:d5:5e:a7:59:ec
 taille: 1Gbit/s
 capacité: 1Gbit/s
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8168 
driverversion=8.047.01-NAPI duplex=full ip=192.168.0.26 latency=0 link=yes 
multicast=yes port=twisted pair speed=1Gbit/s
 ressources: irq:124 portE/S:3000(taille=256) mémoire:a3204000-a3204fff 
mémoire:a320-a3203fff

  Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeanmarc   1665 F pulseaudio
   /dev/snd/controlC0:  jeanmarc   1665 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-05 (235 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03f0:304a HP, Inc 
   Bus 001 Device 003: ID 0951:1665 Kingston Technology Digital DataTraveler 
SE9 64GB
   Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B360M-DS3H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: r8168
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a3da3bcd-b1ad-43de-8e7d-b5afb36efda7 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B360M-DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825987] Re: kernel 5.0 won't auto register bcache caching device

2019-05-06 Thread Kai-Heng Feng
Maybe this one https://github.com/systemd/systemd/issues/11368?

** Bug watch added: github.com/systemd/systemd/issues #11368
   https://github.com/systemd/systemd/issues/11368

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

Title:
  kernel 5.0 won't auto register bcache caching device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since I upgrade my desktop to Ubuntu 19.04, the boot process is enable
  to find the root file system, and drop me to a single user command
  line.

  It seems that kernel 5.0 does not automatically register the bcache caching 
device (/dev/sdb, SSD). However, it does register the backing device 
(/dev/sda6, rotating HDD). To recover, I have to type the following commands :
# echo /dev/sdb > /sys/fs/bcache/register
# lvm vgscan
# lvm vgchange -ay
# exit
  and then, the boot proceed to its normal end (graphical display manager).

  
  The problem does not occur if the system is booted with kernel 4.18.0.

  =
  # lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04

  # apt-cache policy linux-image-5.0.0-13-generic
  linux-image-5.0.0-13-generic:
Installed: 5.0.0-13.14
Candidate: 5.0.0-13.14
Version table:
   *** 5.0.0-13.14 500
  500 http://fr.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  #  apt-cache policy linux-image-4.18.0-17
  linux-image-4.18.0-17-generic:
Installed: 4.18.0-17.18
Candidate: 4.18.0-17.18
Version table:
   *** 4.18.0-17.18 100
  100 /var/lib/dpkg/status
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sylvie 4552 F pulseaudio
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=/dev/vg_acer/lv_swap
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/vg_acer-lv_root ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-23 (1 days ago)
  UserGroups: adm admin audio cdrom dialout docker famille fax fuse lpadmin 
netdev nopasswdlogin plugdev sambashare video wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/19/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G31TM-P35 (MS-7529)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.6:bd04/19/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31TM-P35(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7529
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-05-05 Thread Kai-Heng Feng
** Also affects: xserver-xorg-video-intel (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/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  New
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  New
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  New

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  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
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)

2019-05-02 Thread Kai-Heng Feng
clickwir, please file a new 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/1758507

Title:
  sky2 gigabit ethernet driver sometimes stops working after lid-open
  resume from sleep (88E8055)

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

Bug description:
  ===SRU Justification===
  [Impact]
  sky2 ethernet stops working after system resume from suspend.

  [Fix]
  Increase the PCI D3 delay can workaround the issue.

  [Test]
  User responded that the D3 delay increase can solve the issue.

  [Regression Potential]
  Low. It only affects one device. The fix only increase the delay timer,
  without any functional change.

  ===Original Bug Report===
  After resuming from sleep using the lid-open event, OFTEN (60% replicable, 
usually after 2nd or later resume) the NIC is not functional, and reloading the 
sky2 module does not help. Relevant parts from dmesg:

  [  582.852065] sky2 :04:00.0: Refused to change power state, currently in 
D3
  ...
  [  827.613729] sky2 :04:00.0: ignoring stuck error report bit
  [  827.613748] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613750] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613752] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613754] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613756] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613759] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613761] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613763] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613765] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613767] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613769] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613772] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613774] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613776] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613778] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613780] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613782] sky2 :04:00.0: enp4s0: phy I/O error

  And after reloading the module:
  [ 1421.781480] sky2: driver version 1.30
  [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003)
  [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff
  [ 1421.782292] sky2: probe of :04:00.0 failed with error -95

  Possibly relevant:
  [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID.

  Replicability: When it happens once, further suspend-resume cycles (tried ~5) 
don't fix it. Reboot fixes the NIC, and it often survives first resume after 
that, but 1-2 suspend-resume cycles later the issue WILL occur again.
  Per-boot chance of encountering the issue - so far 2/5.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-12-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/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: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Sat Mar 24 09:54:10 2018
  HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
  InstallationDate: Installed on 2018-03-21 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d 
consoleblank=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 1.11 - 067 - 1566
  dmi.board.name: S11D
  dmi.board.vendor: 

[Kernel-packages] [Bug 1813620] Re: Xorg indefinitely hangs in kernelspace at least 2-3 times a day

2019-05-02 Thread Kai-Heng Feng
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc7 kernel [0].

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”, and attach dmesg.

Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc7/

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

Title:
  Xorg indefinitely hangs in kernelspace at least 2-3 times a day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The graphical environment seems to hang when scrolling web pages in
  Firefox. Can't reliably reproduce during every scrolling, but it has
  happened at least 5 times in the past 7 days. Happens in Kubuntu VM-s
  running under KVM and QEMU (3.1.0) on multiple host machines.

  This issue only started to happen sometime this month. First these
  VM-s were running 18.04 so I was hoping that updating them to 18.10
  would help, but it didn't. I'm guessing that some kernel update for
  both bionic and cosmic causes this.

  Since this bug causes the graphical environment to become totally
  unresponsive, this has already already cost me some lost data, but
  very fortunately not much.

  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
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jotik  1962 F pulseaudio
  Date: Mon Jan 28 18:09:57 2019
  HibernationDevice: RESUME=UUID=9dfc65ab-a122-4254-8806-a580fea3c953
  InstallationDate: Installed on 2015-10-18 (1197 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=78ee528a-a065-4522-b2ca-a1959850a740 ro console=ttyS0 verbose
  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.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2019-01-20 (7 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.0-20180624_124920-prayer
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.3
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.0-20180624_124920-prayer:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.3:cvnQEMU:ct1:cvrpc-i440fx-2.3:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.3
  dmi.sys.vendor: QEMU

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2

2019-05-02 Thread Kai-Heng Feng
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

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 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:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826581] Re: Slow wired Ethernet Realtek 8118

2019-05-01 Thread Kai-Heng Feng
Similar to https://www.spinics.net/lists/netdev/msg560600.html?

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

Title:
  Slow wired Ethernet Realtek 8118

Status in linux package in Ubuntu:
  Confirmed
Status in r8168 package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  Using the latest kernel 5.0.0-13 my network is slower. My MB is a Gigabyte 
B360M-DS3H (Realtek 8118 chipset)

  I got ~22Mbps down on speedtest @1000 (i can reach up to 400Mbps)
  But if i sudo ethtool -s enp3s0 speed 100 duplex full i get up to 92Mbps

  jeanmarc@astrolabe:~$ sudo lshw -class network 
  [sudo] Mot de passe de jeanmarc : 
*-network 
 description: Ethernet interface
 produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 fabriquant: Realtek Semiconductor Co., Ltd.
 identifiant matériel: 0
 information bus: pci@:03:00.0
 nom logique: enp3s0
 version: 16
 numéro de série: e0:d5:5e:a7:59:ec
 taille: 1Gbit/s
 capacité: 1Gbit/s
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8168 
driverversion=8.047.01-NAPI duplex=full ip=192.168.0.26 latency=0 link=yes 
multicast=yes port=twisted pair speed=1Gbit/s
 ressources: irq:124 portE/S:3000(taille=256) mémoire:a3204000-a3204fff 
mémoire:a320-a3203fff

  Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeanmarc   1665 F pulseaudio
   /dev/snd/controlC0:  jeanmarc   1665 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-05 (235 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 03f0:304a HP, Inc 
   Bus 001 Device 003: ID 0951:1665 Kingston Technology Digital DataTraveler 
SE9 64GB
   Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B360M-DS3H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: r8168
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a3da3bcd-b1ad-43de-8e7d-b5afb36efda7 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B360M-DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826858] Re: XPS 9343 System freezes requiring hard reset

2019-05-01 Thread Kai-Heng Feng
Does update the BIOS to latest version (A19) help?

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

Title:
  XPS 9343 System freezes requiring hard reset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to disco I have started having regular freezes of my
  laptop. There is no response to key presses, mouse movement etc. Only
  recourse is to reset the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 29 11:13:13 2019
  HibernationDevice: RESUME=UUID=e76f9b75-a3b2-48c0-931f-7af49bda53bb
  InstallationDate: Installed on 2019-01-06 (112 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-13 (15 days ago)
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.sku: 0665
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

2019-04-29 Thread Kai-Heng Feng
gsettings set org.gnome.settings-daemon.plugins.power lid-close-ac-action 
'nothing'
gsettings set org.gnome.settings-daemon.plugins.power lid-close-battery-action 
'nothing'

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

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On ubuntu 16.04 settings "do anything when closing lid" is applied.
  Hard reset needs.

  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
   /dev/snd/controlC0:  neslihan   1863 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947
  InstallationDate: Installed on 2018-09-12 (220 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer TravelMate 5335
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BA51_MV
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TravelMate 5335
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

2019-04-29 Thread Kai-Heng Feng
** 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 nvidia-graphics-drivers-384 in Ubuntu.
https://bugs.launchpad.net/bugs/1743094

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2

2019-04-29 Thread Kai-Heng Feng
** Tags removed: verification-needed-cosmic verification-needed-disco
** Tags added: verification-done-cosmic verification-done-disco

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

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

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 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:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826581] Re: Slow wired Ethernet Realtek 8118

2019-04-29 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Slow wired Ethernet Realtek 8118

Status in linux package in Ubuntu:
  New
Status in r8168 package in Ubuntu:
  New

Bug description:
  Hello,
  Using the latest kernel 5.0.0-13 my network is slower. My MB is a Gigabyte 
B360M-DS3H (Realtek 8118 chipset)

  I got ~22Mbps down on speedtest @1000 (i can reach up to 400Mbps)
  But if i sudo ethtool -s enp3s0 speed 100 duplex full i get up to 92Mbps

  jeanmarc@astrolabe:~$ sudo lshw -class network 
  [sudo] Mot de passe de jeanmarc : 
*-network 
 description: Ethernet interface
 produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 fabriquant: Realtek Semiconductor Co., Ltd.
 identifiant matériel: 0
 information bus: pci@:03:00.0
 nom logique: enp3s0
 version: 16
 numéro de série: e0:d5:5e:a7:59:ec
 taille: 1Gbit/s
 capacité: 1Gbit/s
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8168 
driverversion=8.047.01-NAPI duplex=full ip=192.168.0.26 latency=0 link=yes 
multicast=yes port=twisted pair speed=1Gbit/s
 ressources: irq:124 portE/S:3000(taille=256) mémoire:a3204000-a3204fff 
mémoire:a320-a3203fff

  Thanks

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826716] Re: Include Sunix serial/parallel driver

2019-04-28 Thread Kai-Heng Feng
** Tags added: columbia originate-from-1769839

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

Title:
  Include Sunix serial/parallel driver

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

Bug description:
  [Impact]
  We shipped several platform with sunix device, which is enabled by sunix
  DKMS driver.
  We should use in-tree driver instead.

  [Fix]
  Include not-yet-merged sunix driver:
  https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/

  [Test]
  Use command `inputattach` to test serial mouse connected to the Sunix
  board. The mouse works correctly. 

  [Regression Potential]
  Low. It's a new driver so the regression potential is minimal.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826716] [NEW] Include Sunix serial/parallel driver

2019-04-28 Thread Kai-Heng Feng
Public bug reported:

[Impact]
We shipped several platform with sunix device, which is enabled by sunix
DKMS driver.
We should use in-tree driver instead.

[Fix]
Include not-yet-merged sunix driver:
https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/

[Test]
Use command `inputattach` to test serial mouse connected to the Sunix
board. The mouse works correctly. 

[Regression Potential]
Low. It's a new driver so the regression potential is minimal.

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

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

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

** No longer affects: linux (Ubuntu)

** Also affects: linux-oem (Ubuntu Bionic)
   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/1826716

Title:
  Include Sunix serial/parallel driver

Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  [Impact]
  We shipped several platform with sunix device, which is enabled by sunix
  DKMS driver.
  We should use in-tree driver instead.

  [Fix]
  Include not-yet-merged sunix driver:
  https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/

  [Test]
  Use command `inputattach` to test serial mouse connected to the Sunix
  board. The mouse works correctly. 

  [Regression Potential]
  Low. It's a new driver so the regression potential is minimal.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-04-26 Thread Kai-Heng Feng
X crashed after resume. Do you see the issue when i915 is used instead?

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  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:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1821738] Re: A userspace process hangs in d-state forever in a virtual machine environment with a virtio-scsi disk

2019-04-26 Thread Kai-Heng Feng
Is there an upstream commit to fix the issue?

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

Title:
  A userspace process hangs in d-state forever in a virtual machine
  environment with a virtio-scsi disk

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-46.49-generic 4.15.18

  
  It happens because the process is waiting for its request completion which 
never happens.

  The reason for the hung request is a race condition inside the block
  layer.

  Namely, there is a race condition with a long request.

  Each request has a timer. When timer fires it sets REQ_ATOM_COMPLETE
  and clears it after finishing.

  The request completion checks REQ_ATOM_COMPLETE and if it is set the 
completion returns doing nothing and never executes again, thinking that the 
request doesn't need any attention anymore since it's actually completed.
   
  Thus, if the request completion starts executing when the timer handler is in 
progress it just returns seeing that the complete flag is set, then the timer 
clears the complete flag and the request stays in the system forever executing 
the timer handler again and again which just rearms itself.

  This happens with the long-running requests only. By default, the request 
timeout is 30 seconds so there should be a request which execution time > 30 
seconds.
  This is a rare case for local hardware storages but may appear more often 
when the storage is accessed via a network.

  The behavior described affects mainstream 4.13, 4.14, 4.15 kernels and 
rh7-3.10.0-957.5.1.el7 kernel based systems.
   
  Before 4.13 - the timer didn't rearm itself and just aborted the request. The 
patch rearming the timer was introduced in 4.13: e72c9a2a67a6400c "scsi: 
virtio_scsi: let host do exception handling"

  After 4.15 the block layer switched to using MQ scheme in block layer
  which isn't prone to this kind of races. In recent kernel >=5.0 there
  is the only MQ scheme left and the legacy race-prone block layer code
  has been removed.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-26 Thread Kai-Heng Feng
Please attach the evtest log, 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/1822581

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825996] Re: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04

2019-04-26 Thread Kai-Heng Feng
*** This bug is a duplicate of bug 1825699 ***
https://bugs.launchpad.net/bugs/1825699

It's LEN2036 on this system.

Beaud'huy, can you attach full dmesg under the test kernel?

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

Title:
  Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I upgrade ubuntu on 19.10 but my touchpad is not found. Can you help
  me ?

  Thank you

  Josselin

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/controlC1:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/pcmC1D0p:   jbeaud-huy   2159 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 23 15:49:51 2019
  InstallationDate: Installed on 2018-11-19 (154 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LTS6YR00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c816b2e0-898d-4948-80e7-1466ae6b59e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)
  dmi.bios.date: 08/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET47W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS6YR00
  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:bvrR0QET47W(1.24):bd08/14/2018:svnLENOVO:pn20LTS6YR00:pvrThinkPadL480:rvnLENOVO:rn20LTS6YR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS6YR00
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock

2019-04-25 Thread Kai-Heng Feng
I think the keyboard might want to use hid-microsoft. But before doing
that, can you check if the TB16 has the latest firmware? You may need a
Windows system to update the 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/1822089

Title:
  Frequent (silent) USB disconnects with Dell TB16 dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I see something similar (but different) to bug 1766076 on a Dell 5530:

  - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from 
other bugs that make this dock unusable)
  - BIOS 1.6.0
  - TB16 dock with a single monitor on the display port, providing power, using 
native enumeration setting in the BIOS
  - Microsoft comfort curve keyboard, webcam, headset connected to dock USB 
ports
  - Wired ethernet via the dock.

  Keyboard stops responding frequently.  There is no output in dmesg
  when this happens.  If I later unplug the keyboard I see a
  disconnection message in dmesg and I can reconnect it to the same
  port.  Sometimes it works for a day after this, other times it works
  for <60s.

  Other devices disconnect too but the pattern is different.  Much more likely 
to see the disconnect under heavy load, such as webcam/headset getting 
disconnected during a conference call.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC4:  shaun  2837 F pulseaudio
   /dev/snd/controlC3:  shaun  2837 F pulseaudio
   /dev/snd/controlC1:  shaun  2837 F pulseaudio
   /dev/snd/controlC0:  shaun  2837 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-12-11 (133 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. Precision 5530
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0FP2W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825996] Re: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04

2019-04-25 Thread Kai-Heng Feng
*** This bug is a duplicate of bug 1825699 ***
https://bugs.launchpad.net/bugs/1825699

Beaud'huy,

Doesn't work in what regard? It can't boot?

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

Title:
  Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I upgrade ubuntu on 19.10 but my touchpad is not found. Can you help
  me ?

  Thank you

  Josselin

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/controlC1:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/pcmC1D0p:   jbeaud-huy   2159 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 23 15:49:51 2019
  InstallationDate: Installed on 2018-11-19 (154 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LTS6YR00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c816b2e0-898d-4948-80e7-1466ae6b59e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)
  dmi.bios.date: 08/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET47W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS6YR00
  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:bvrR0QET47W(1.24):bd08/14/2018:svnLENOVO:pn20LTS6YR00:pvrThinkPadL480:rvnLENOVO:rn20LTS6YR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS6YR00
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822089] Re: Frequent (silent) USB disconnects with Dell TB16 dock

2019-04-24 Thread Kai-Heng Feng
Please boot with kernel parameter "usbcore.dyndbg=+p", attach dmesg when
the issue happens.

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

Title:
  Frequent (silent) USB disconnects with Dell TB16 dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I see something similar (but different) to bug 1766076 on a Dell 5530:

  - Using kernel 5.0.4 from UKUU (because current Ubuntu kernel suffers from 
other bugs that make this dock unusable)
  - BIOS 1.6.0
  - TB16 dock with a single monitor on the display port, providing power, using 
native enumeration setting in the BIOS
  - Microsoft comfort curve keyboard, webcam, headset connected to dock USB 
ports
  - Wired ethernet via the dock.

  Keyboard stops responding frequently.  There is no output in dmesg
  when this happens.  If I later unplug the keyboard I see a
  disconnection message in dmesg and I can reconnect it to the same
  port.  Sometimes it works for a day after this, other times it works
  for <60s.

  Other devices disconnect too but the pattern is different.  Much more likely 
to see the disconnect under heavy load, such as webcam/headset getting 
disconnected during a conference call.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC4:  shaun  2837 F pulseaudio
   /dev/snd/controlC3:  shaun  2837 F pulseaudio
   /dev/snd/controlC1:  shaun  2837 F pulseaudio
   /dev/snd/controlC0:  shaun  2837 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-12-11 (133 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. Precision 5530
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0FP2W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Intel Kaby Lake)

2019-04-24 Thread Kai-Heng Feng
Does "i915.enable_psr=0" help?

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

Title:
  Dell XPS 13 9380 flickering  (Intel Kaby Lake)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826065] Re: Can't boot from usb live system to install disco dingo 19.04

2019-04-24 Thread Kai-Heng Feng
Possible to install 18.10 and find out if latest mainline kernel fixes
the issue?

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

Title:
  Can't boot from usb live system to install disco dingo 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot boot from a USB live system with Disco Dingo 19.04 to install
  Ubuntu. I tried several kernel command line options (nomodeset
  modprobe.blacklist=nouveau) but nothing seems to work.

  With acpi=off I can see some output. The boot sequence stops at
  "Freeing unused kernel image memory". Before, there are some UEFI
  error messages (Couldn't get UEFI db list, dbx list). I attached a
  photo of the output. I don't get these errors with 18.10.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825996] Re: Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04

2019-04-24 Thread Kai-Heng Feng
*** This bug is a duplicate of bug 1825699 ***
https://bugs.launchpad.net/bugs/1825699

Hui,

Does the one you have use id "LEN2036"?

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

Title:
  Touchpad not working on Lenovo ThinkPad L480 after upgrade to 19.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I upgrade ubuntu on 19.10 but my touchpad is not found. Can you help
  me ?

  Thank you

  Josselin

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/controlC1:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/pcmC1D0p:   jbeaud-huy   2159 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 23 15:49:51 2019
  InstallationDate: Installed on 2018-11-19 (154 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LTS6YR00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c816b2e0-898d-4948-80e7-1466ae6b59e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)
  dmi.bios.date: 08/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET47W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS6YR00
  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:bvrR0QET47W(1.24):bd08/14/2018:svnLENOVO:pn20LTS6YR00:pvrThinkPadL480:rvnLENOVO:rn20LTS6YR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS6YR00
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825996] Re: Touchpad is not found

2019-04-24 Thread Kai-Heng Feng
Can you remove i2c_i801 from backlist and test if this kernel helps?

https://people.canonical.com/~khfeng/lp1825996/

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

Title:
  Touchpad is not found

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I upgrade ubuntu on 19.10 but my touchpad is not found. Can you help
  me ?

  Thank you

  Josselin

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/controlC1:  jbeaud-huy   2159 F pulseaudio
   /dev/snd/pcmC1D0p:   jbeaud-huy   2159 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 23 15:49:51 2019
  InstallationDate: Installed on 2018-11-19 (154 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LTS6YR00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c816b2e0-898d-4948-80e7-1466ae6b59e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)
  dmi.bios.date: 08/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET47W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS6YR00
  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:bvrR0QET47W(1.24):bd08/14/2018:svnLENOVO:pn20LTS6YR00:pvrThinkPadL480:rvnLENOVO:rn20LTS6YR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS6YR00
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Intel Kaby Lake)

2019-04-24 Thread Kai-Heng Feng
Can you boot with kernel parameter "drm.debug=0xe" and attach full dmesg
after boot?

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

Title:
  Dell XPS 13 9380 flickering  (Intel Kaby Lake)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824050] Re: access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints

2019-04-24 Thread Kai-Heng Feng
The fix is not in linux-nfs tree yet.

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

Title:
  access.W_OK yields -1 EACCES (permission denied) on NFS mountpoints

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from xenial kernel (4.4.0-145) to linux-image-generic-
  hwe-16.04 (4.15.0-47) I am no longer able to run an application that
  checks it's data directory for write access/path traversal when that
  directory is an NFS share. This works on 4.4 and 3.13 kernels that I
  tested with but fails on 4.15. I'm using NFSv3 and have seen the
  behavior with both a synology NAS as the nfs-server as well as my
  xenial desktop as the nfs-server.

  To reproduce:
  0.) Boot test machine with kernel 4.15.0-47
  1.) set up a NFS export on another machine (nfs-server)
  /etc/exports:
  /srv/nfstest   192.168.100.100(rw,sync,no_subtree_check)

  2.) mount the NFS share on the test machine and give a non-root user
  ownership of the mount, in my case I have a user: aptly, with
  home=/var/lib/aptly, and I mounted the NFS at /var/lib/aptly/test.
  aptly:aptly owns /var/lib/aptly/test.

  /etc/fstab:
  192.168.100.101:/srv/nfstest/var/lib/aptly/test  nfs rw,mountvers=3

  
  3.) attempt to call access.W_OK on the mount as the non-root user `strace 
./testaccess.py`
  stderr:
  ...
  access("/var/lib/aptly/test", W_OK) = -1 EACCES (Permission denied)
  ...
  stdout:
  ('Writeable:', False)
  ('user r,e,s', (5062, 5062, 5062))
  ('group r,e,s', (5062, 5062, 5062))
  posix.stat_result(st_mode=16895, st_ino=101188113, st_dev=48, st_nlink=3, 
st_uid=5062, st_gid=5062, st_size=4096, st_atime=1554858490, 
st_mtime=1554858633, st_ctime=1554858633)

  testaccess.py:
  #!/usr/bin/python

  import os
  import sys
  from pprint import pprint
  directory = '/var/lib/aptly/test'

  if __name__ == "__main__":
writeable = os.access(directory, os.W_OK)
print("Writeable:", writeable)
print("user r,e,s", os.getresuid())
print("group r,e,s", os.getresgid())
pprint(os.stat(directory))
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  9 18:53 seq
   crw-rw 1 root audio 116, 33 Apr  9 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/pao03--aptly01--vg-swap_1
  InstallationDate: Installed on 2019-04-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=/dev/mapper/pao03--aptly01--vg-root ro
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.15.0-47-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Intel Kaby Lake)

2019-04-24 Thread Kai-Heng Feng
Download linux-image-
unsigned-5.1.0-994-generic_5.1.0-994.20190400_amd64.deb and linux-
modules-5.1.0-994-generic_5.1.0-994.20190400_amd64.deb then install
them.

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

Title:
  Dell XPS 13 9380 flickering  (Intel Kaby Lake)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Intel Kaby Lake)

2019-04-24 Thread Kai-Heng Feng
Does the drm-intel-nightly help?

https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
nightly/2019-04-23/

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

Title:
  Dell XPS 13 9380 flickering  (Intel Kaby Lake)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

2019-04-24 Thread Kai-Heng Feng
Long press the shutdown icon or press ALT, it'll change to 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/1825219

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On ubuntu 16.04 settings "do anything when closing lid" is applied.
  Hard reset needs.

  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
   /dev/snd/controlC0:  neslihan   1863 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947
  InstallationDate: Installed on 2018-09-12 (220 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer TravelMate 5335
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BA51_MV
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TravelMate 5335
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1766377] Re: Ethernet E1000 Controller Hangs

2019-04-24 Thread Kai-Heng Feng
Same as lp: #1785171?

Please test:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/comments/54

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

Title:
  Ethernet E1000 Controller Hangs

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

Bug description:
   With Bionic kernel 4.15.0-15 and 4.15.0-17 I am experiencing periodic 
hanging of the LAN connection.  This is happening on an Asus X99-DELUX 
motherboard, controller specifications:
  Intel® I218V, 1 x Gigabit LAN Controller(s)
  Intel® I211-AT, 1 x Gigabit LAN
  Dual Gigabit LAN controllers- 802.3az Energy Efficient Ethernet (EEE) 
appliance
  Support Teaming Technology
  ASUS Turbo LAN Utility
  The CPU is an i7-6850 and it is configured with 128GB of DDR4 RAM.
  This machine has a number of Qemu/KVM virtual guests and is using a software 
bridge to share the interface.
  This did not happen with 17.10 and 4.13.0 kernel.  It is happening on 
multiple machines here.
  Here are the messages from dmesg:
  1016198.957850] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <13c8d0008>
 next_to_watch
 jiffies  <13c8d0880>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <3c00>
   PHY Extended Status<3000>
   PCI Status <10>
  [1016200.942072] e1000e :00:19.0 eno1: Detected Hardware Unit Hang:
 TDH  
 TDT  <2d>
 next_to_use  <2d>
 next_to_clean
   buffer_info[next_to_clean]:
 time_stamp   <13c8d0008>
 next_to_watch
 jiffies  <13c8d1040>
 next_to_watch.status <0>
   MAC Status <80083>
   PHY Status <796d>
   PHY 1000BASE-T Status  <3c00>
   PHY Extended Status<3000>
   PCI Status <10>
  [1016202.413607] e1000e :00:19.0 eno1: Reset adapter unexpectedly
  [1016202.413701] bridge0: port 1(eno1) entered disabled state
  [1016202.413732] bridge0: topology change detected, propagating
  [1016206.76] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [1016206.666708] bridge0: port 1(eno1) entered blocking state
  [1016206.666712] bridge0: port 1(eno1) entered listening state
  [1016216.750911] bridge0: port 1(eno1) entered learning state
  [1016232.110291] bridge0: port 1(eno1) entered forwarding state
  [1016232.110294] bridge0: topology change detected, sending tcn bpdu
  [1017834.390579] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [1017834.390770] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [1017834.414792] platform regulatory.0: Direct firmware load for 
regulatory.db failed with error -2
  [1017834.414794] cfg80211: failed to load regulatory.db
  If there is any other information I can provide to aid in resolution, please 
contact me, nan...@eskimo.com.  Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: MATE
  Date: Mon Apr 23 16:45:30 2018
  HibernationDevice: RESUME=UUID=963cb206-8962-4fc0-82a1-fc4f02a9b5c5
  InstallationDate: Installed on 2017-05-05 (353 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-lowlatency 
root=UUID=28825f5b-a6fd-4e09-982c-0513ae4d2842 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

[Kernel-packages] [Bug 1826065] Re: Can't boot from usb live system to install disco dingo 19.04

2019-04-24 Thread Kai-Heng Feng
Does "Safe Graphics" mode help?

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

Title:
  Can't boot from usb live system to install disco dingo 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot boot from a USB live system with Disco Dingo 19.04 to install
  Ubuntu. I tried several kernel command line options (nomodeset
  modprobe.blacklist=nouveau) but nothing seems to work.

  With acpi=off I can see some output. The boot sequence stops at
  "Freeing unused kernel image memory". Before, there are some UEFI
  error messages (Couldn't get UEFI db list, dbx list). I attached a
  photo of the output. I don't get these errors with 18.10.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1826113] Re: socket creation failure - invalid argument error

2019-04-24 Thread Kai-Heng Feng
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  socket creation failure - invalid argument error

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, This code is working in 32 bit ubuntu versions 14.04 and 16.04. 
  Also, this code is working in ubuntu 14.04 64 bit versions. 

  but it is giving socket creation failure error in ubuntu 64 bit.
  (linux-image-3.19.0-25-generic 32/64 bit both working (ubuntu 14.04),
  linux-image-4.15.0-45-generic (32 bit working for ubuntu 16.04) and
  linux-image-4.15.0-47-generic ubunutu 64 bit gives error. Please
  suggest to this issue to run on 64 bit ubuntu 16.04 and other
  machines.

  This code socket fail and returns -1 :  s = socket(AF_PACKET,
  SOCK_RAW, htons(ETH_P_ALL));

  
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  static int s = -1;
  static int s1 = -1;

  void onexit(int signum)
  {
  (void)signum;
  printf("Exiting");
  close(s);
  close(s1);
  }

  int main()
  {
  char buf[1600];
  ssize_t recv_size = -1;
  ssize_t send_size = -1;

  int i = 0;

  struct sockaddr_ll socket_address, socket_address1;

  s = socket(AF_PACKET, SOCK_RAW, htons(ETH_P_ALL));
  s1 = socket(AF_PACKET, SOCK_RAW, htons(ETH_P_ALL));

  if ((s == -1) || (s1 == -1))
  {
  perror("Socket creation failed");
  exit (0);
  }

  signal(SIGINT, onexit);

  memset(_address, 0, sizeof (socket_address));
  socket_address.sll_family = PF_PACKET;
  socket_address.sll_ifindex = if_nametoindex("eth0");
  socket_address.sll_protocol = htons(ETH_P_ALL);

  i = bind(s, (struct sockaddr*)_address,
  sizeof(socket_address));
  if (i == -1)
  {
  perror("Bind");
  exit (0);
  }

  memset(_address1, 0, sizeof (socket_address1));
  socket_address1.sll_family = PF_PACKET;
  socket_address1.sll_ifindex = if_nametoindex("eth1");
  socket_address1.sll_protocol = htons(ETH_P_ALL);

  i = bind(s1, (struct sockaddr*)_address1,
  sizeof(socket_address1));
  if (i == -1)
  {
  perror("Bind");
  exit (0);
  }

  while (1)
  {
  memset(, 0, sizeof(buf));

  recv_size = recv(s, , sizeof(buf), 0);
  if (recv_size == -1)
  {
  perror("Socket receive");
  exit (0);
  }

  printf("\n");
  for(i=0; i  recv_size; i++)
  {
  printf("%02x ", buf[i]);
  }

  send_size = send(s1, , recv_size, 0);
  if (send_size == -1)
  {
  perror("Socket send");
  exit (0);
  }
  }

  return 0;
  }

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-23 Thread Kai-Heng Feng
"hp_wmi: query 0x4 returned error 0x5" may just be red herring.
What's the output of evtest when choosing "HP WMI hotkeys" instead?

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-23 Thread Kai-Heng Feng
Ok, please attach acpidump.

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat

2019-04-23 Thread Kai-Heng Feng
Does this also happen on 4.18.0-17?
Apr 22 23:40:47 BUG: unable to handle kernel NULL pointer dereference at 
0038
Apr 22 23:40:47 IP: smb2_push_mandatory_locks+0x104/0x3b0 [cifs]

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

Title:
  cifs set_oplock buffer overflow in strcat

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.2 LTS
  Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM

  top - 12:39:53 up  3:41,  4 users,  load average: 66.19, 64.06, 76.90
  Tasks: 1076 total,   1 running, 675 sleeping,  12 stopped,   1 zombie
  %Cpu(s): 28.2 us,  0.3 sy,  0.0 ni, 71.5 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 
st
  KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache
  KiB Swap:   999420 total,   999420 free,0 used. 33477683+avail Mem


  We've seen the following bug many times since we introduced new
  machines running Ubuntu 18. Wasn't an issue older machines running
  Ubuntu 16. Three different machines are affected, so it's rather not a
  hardware issue.

  
  | detected buffer overflow in strcat
  | [ cut here ]
  | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052!
  | invalid opcode:  [#1] SMP PTI
  | Modules linked in: [...]
  | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018
  | RIP: 0010:fortify_panic+0x13/0x22
  |  [...]
  | Call Trace:
  |  smb21_set_oplock_level+0x147/0x1a0 [cifs]
  |  smb3_set_oplock_level+0x22/0x90 [cifs]
  |  smb2_set_fid+0x76/0xb0 [cifs]
  |  cifs_new_fileinfo+0x259/0x390 [cifs]
  |  ? smb2_get_lease_key+0x40/0x40 [cifs]
  |  ? cifs_new_fileinfo+0x259/0x390 [cifs]
  |  cifs_open+0x3db/0x8d0 [cifs]
  |  [...]

  (Full dmesg output attached)

  After hitting this bug there are many cifs related dmesg entries,
  processes lock up and eventually the systems freezes.

  
  The share is mounted using:
  //server/share  /mnt/server/ cifs 
defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks

  Currently we're testing the cifs mount options "cache=none" as the bug
  seems to be oplock related.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective

2019-04-22 Thread Kai-Heng Feng
https://wiki.gentoo.org/wiki/Xrandr#Screen_manipulation

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

Title:
  Super + p does not work as expected, it's defective

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have 3 monitors (2 landscape and 1 portrait), I normally need to
  change between my monitors due to my setup. If I want to play a game,
  I typically switch to a single monitor (Built-in) then I can switch
  back to Join and everything goes back to normal. That is what I would
  expect but that is NOT what happens.

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

  The first two options work correctly, but the 3rd and 4th options do
  not.

  
  External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.

  
  I am using:
  - Ubuntu 4.15.0-47.50-generic 4.15.18
  - GeForce GTX 1080/PCIe/SSE2
  - I have attached: lspci-vnvn.log

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  With nvidia-driver-418 from: ppa:graphics-drivers/ppa

  $ apt-cache policy nvidia-driver-418
  nvidia-driver-418:
Installed: 418.56-0ubuntu0~gpu18.04.1
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   *** 418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status


  I am not sure if this is actually necessary because I don't think this
  has to do with the graphics card.

  I am not sure what other information you will need for this report. I can 
provide more data upon request.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (298 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

2019-04-22 Thread Kai-Heng Feng
Subscribing Mika.

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

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET45W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JGS01000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in

2019-04-22 Thread Kai-Heng Feng
Should be "options mt76x0u disable_usb_sg=1".

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

Title:
  Ubuntu freezes when AC 430 WiFi Dongle is plugged in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu crashes after a short time after plugging in the WiFi stick
  "AC430". The kernel fails to load the driver and the following message
  appears repeatedly:

  [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  ...

  Tested with Kernel 4.19 and 5.0 (5.0.2)
  Tested with the following distributions:
  Ubuntu Cosmic Cuttlefish 18.10
  Ubuntu Studio 18.10
  Ubuntu Disco Dingo 19.04

  40-usb_modeswitch.rules was already modified to load the driver, otherwise 
the system chooses Driver=option.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-03-31 (13 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.2-050002-lowlatency x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare 
scanner sudo tape vboxusers video
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825841] Re: Laptop battery drains while suspend since 18.04 , even in deep sleep (STR)

2019-04-22 Thread Kai-Heng Feng
What kernel version have this issue and what kernel version don't have?

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

Title:
  Laptop battery drains while suspend since 18.04 , even in deep sleep
  (STR)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  1) 
  My laptop battery drains very fast while suspend, which prevent using 
suspend-to-ram as I almost always find the laptop shut down due to battery 
being empty.

  I Observed this problem since my upgrade from 16.04 to 18.04 on my
  Laptop. It's Toshiba Portege. Suspend does work fine but battery
  drains while suspend; it was working pretty well in Ubuntu 16.04.

  I suspect a kind of regression in the i915 driver for now, but did not
  find any evident of this.

  After a suspend to ram, we can observe a kind of crash in the i915
  driver suspend_late code :

  [  475.970946] [ cut here ]
  [  475.970947] Display power well on
  [  475.971009] WARNING: CPU: 0 PID: 7579 at 
/build/linux-6ZmFRN/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:8696 
assert_can_disable_lcpll+0x3b3/0x480 [i915]
  [  475.971010] Modules linked in: rfcomm ccm cmac bnep cdc_mbim uvcvideo 
cdc_wdm qcserial cdc_ncm usb_wwan usbserial usbnet mii btusb btrtl btbcm 
videobuf2_vmalloc btintel videobuf2_memops videobuf2_v4l2 videobuf2_core 
bluetooth videodev media ecdh_generic msr arc4 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel kvm 
mac80211 irqbypass snd_seq intel_cstate intel_rapl_perf iwlwifi snd_seq_device 
snd_timer joydev cfg80211 input_leds serio_raw wmi_bmof snd rtsx_pci_ms 
memstick lpc_ich shpchp mei_me toshiba_acpi mei soundcore sparse_keymap 
toshiba_bluetooth industrialio tpm_infineon mac_hid sch_fq_codel parport_pc
  [  475.971045]  ppdev lp parport ip_tables x_tables autofs4 algif_skcipher 
af_alg dm_crypt i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
rtsx_pci_sdmmc i2c_algo_bit aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd psmouse drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt 
e1000e fb_sys_fops drm rtsx_pci ptp pps_core video wmi
  [  475.971062] CPU: 0 PID: 7579 Comm: kworker/u16:7 Not tainted 
4.15.0-47-generic #50-Ubuntu
  [  475.971063] Hardware name: TOSHIBA PORTEGE Z30-B/PORTEGE Z30-B, BIOS 
Version 3.20   04/09/2015
  [  475.971066] Workqueue: events_unbound async_run_entry_fn
  [  475.971087] RIP: 0010:assert_can_disable_lcpll+0x3b3/0x480 [i915]
  [  475.971088] RSP: 0018:a96642bbfd00 EFLAGS: 00010286
  [  475.971089] RAX:  RBX: 9bf98b0a8000 RCX: 
bca62768
  [  475.971090] RDX: bca62768 RSI: 0082 RDI: 
0202
  [  475.971091] RBP: a96642bbfd20 R08:  R09: 
0015
  [  475.971091] R10: 0600 R11: 0340 R12: 
9bf98b0a8358
  [  475.971092] R13: 9bf98b0a8368 R14: c0580baf R15: 

  [  475.971093] FS:  () GS:9bf9a140() 
knlGS:
  [  475.971094] CS:  0010 DS:  ES:  CR0: 80050033
  [  475.971095] CR2: 7fb1afffeeb6 CR3: 00011e20a005 CR4: 
003606f0
  [  475.971096] Call Trace:
  [  475.971117]  hsw_enable_pc8+0x87/0x310 [i915]
  [  475.971129]  i915_drm_suspend_late+0xdb/0x140 [i915]
  [  475.971141]  i915_pm_suspend_late+0x20/0x30 [i915]
  [  475.971143]  pm_generic_suspend_late+0x2e/0x40
  [  475.971145]  pci_pm_suspend_late+0x31/0x40
  [  475.971147]  dpm_run_callback+0x5a/0x150
  [  475.971149]  ? pci_pm_poweroff_late+0x40/0x40
  [  475.971151]  __device_suspend_late+0xc6/0x1d0
  [  475.971152]  async_suspend_late+0x1f/0xa0
  [  475.971154]  async_run_entry_fn+0x3c/0x150
  [  475.971156]  process_one_work+0x1de/0x410
  [  475.971158]  worker_thread+0x32/0x410
  [  475.971160]  kthread+0x121/0x140
  [  475.971161]  ? process_one_work+0x410/0x410
  [  475.971163]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  475.971166]  ret_from_fork+0x35/0x40
  [  475.971167] Code: d5 ff 48 8b 83 18 07 00 00 e9 b0 fd ff ff 89 ce 4c 89 f7 
e8 90 fc 1a fb 0f 0b e9 99 fc ff ff 48 c7 c7 c9 0b 58 c0 e8 7d fc 1a fb <0f> 0b 
e9 b5 fc ff ff 48 c7 c7 7a 0c 58 c0 e8 6a fc 1a fb 0f 0b 
  [  475.971192] ---[ end trace 91209fe53f0c0cc2 ]---

  By using a more recent kernel (4.18), I get a crash in the pc8 disable
  function. I am not sure whether this thread backtrace is responsible
  for the battery drain or not.

  
  I also read Intel open source site to help debug this, without success for 
now : 
  * 
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

  The analyze_suspend.py script produced some bunch of data, if anyone
  needs 

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

2019-04-22 Thread Kai-Heng Feng
Yes, please use my custom built kernel in the interim.

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep)
  Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done.
  Apr 02 13:39:59 taplop kernel: 

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

2019-04-22 Thread Kai-Heng Feng
https://lkml.org/lkml/2019/4/22/81

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system...
  Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep)
  Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done.
  Apr 02 13:39:59 taplop kernel: Freezing user space 

[Kernel-packages] [Bug 1825699] Re: Touchpad not working after upgrade to 19.04

2019-04-22 Thread Kai-Heng Feng
Please test this kernel:
https://people.canonical.com/~khfeng/lp1825699/

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

Title:
  Touchpad not working after upgrade to 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 the touch pad stopped working during the 
upgrade.
  cat /proc/bus/input/devices does not show any information about the Synaptics 
Touchpad.
  lsusb does show an entry:
  Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. 

  synclient shows:
  Couldn't find synaptics properties. No synaptics driver loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  max1990 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 08:32:38 2019
  InstallationDate: Installed on 2019-04-10 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20LW0010GE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago)
  dmi.bios.date: 09/25/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW0010GE
  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:bvrR0QET49W(1.26):bd09/25/2018:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW0010GE
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb

2019-04-22 Thread Kai-Heng Feng
The system use Nvidia graphics, please use "safe graphics mode" provided
by the live usb.

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

Title:
  Lenovo Legion Y530-15ICH  does not start with live usb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Legion Y530-15ICH  does not start with live usb

  
  Does not load beyond the boot screen with the Ubuntu logo
  the same situation is with Kubuntu, but it loads up to the desktop image, the 
interface is not loaded
  Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04

  Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz
  lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use 
Ubuntu / Kubuntu (preferably).

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825718] Re: Touchpad not detecting in Linux

2019-04-22 Thread Kai-Heng Feng
https://lkml.org/lkml/2019/4/22/38

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

Title:
  Touchpad not detecting in Linux

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue was observed in laptop -"iBall-Aer3" which has a touch-pad with 
integrated fingerprint scanner. Both works very well in Windows 10, but not in 
Linux. 
  Please Check.  
  Any help is highly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dipin  1204 F pulseaudio
   /dev/snd/controlC1:  dipin  1204 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 18:12:35 2019
  InstallationDate: Installed on 2019-04-21 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: iBall Aer3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=53642f8a-ea5c-46e8-bde2-b1744102311b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G
  dmi.board.asset.tag: Default string
  dmi.board.name: Aer3
  dmi.board.vendor: iBall
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Aer3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: iBall

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb

2019-04-22 Thread Kai-Heng Feng
Not seeing lspci-vnvn.log here.

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

Title:
  Lenovo Legion Y530-15ICH  does not start with live usb

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Legion Y530-15ICH  does not start with live usb

  
  Does not load beyond the boot screen with the Ubuntu logo
  the same situation is with Kubuntu, but it loads up to the desktop image, the 
interface is not loaded
  Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04

  Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz
  lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use 
Ubuntu / Kubuntu (preferably).

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825678] Re: Intel wifi fails to resume after suspend

2019-04-21 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Intel wifi fails to resume after suspend

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

Bug description:
  Yesterday my WiFi card(Intel Wireless 3165) didn't show up on resuming
  the laptop from a suspend state. I rebooted a few times and found that
  the situation hadn't changed. Rebooting and choosing older kernels
  didn't help. I ran lspci and discovered my WiFi card was missing in
  the output. I shut down the laptop assuming my WiFi card suffered a
  hardware failure. In the evening, after starting up from a full
  shutdown, the WiFi card worked again.

  Today, the situation happened again, but I approached the debugging
  more methodically. I looked at nmcli and found it still saw my wifi
  card but found it unavailable. lspci could still see the Wifi card in
  the last position. I analyzed dmesg output and discovered an iwlwifi
  crash(the relevant part of dmesg is provided in wifi_dmesg.txt
  attachment).

  Then, I rebooted the laptop. This didn't fix the issue and from a
  quick look at lspci, the wifi card was missing again. So I repeated
  the procedure that worked the previous day - full shutdown, wait 10
  seconds, then start up. This restored my WiFi card to a working state
  and allowed me to file this bug report.

  I will be happy to provide any further information that could read to
  fixing this issue.

  Additional information:

  1. lsb_release -rd
  Description:  Peppermint 8 Eight
  Release:  8
  Yes, that's technically not Ubuntu. However, Peppermint does not modify 
Ubuntu's kernel, and Peppermint 8 is based on Ubuntu 16.04 Xenial Xerus.

  2. apt-cache policy linux-firmware
  linux-firmware:
Installed: 1.157.21
Candidate: 1.157.21
Version table:
   *** 1.157.21 500
  500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  3. I expected suspend and resume to work like they did for the last
  two years

  4. iwlwifi crashed and dumped its registers.

  5. Inxi, in case it's useful(many other bug reporting websites ask for it):
  inxi -Fz
  System:Host: PiDell Kernel: 4.15.0-47-generic x86_64 (64 bit) Desktop: N/A
 Distro: Peppermint Eight
  Machine:   System: Dell (portable) product: Inspiron 15 7000 Gaming
 Mobo: Dell model: 065C71 v: A00 Bios: Dell v: 1.7.0 date: 
05/08/2018
  CPU:   Quad core Intel Core i7-7700HQ (-HT-MCP-) cache: 6144 KB 
 clock speeds: max: 3800 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz
 4: 800 MHz 5: 800 MHz 6: 800 MHz 7: 800 MHz 8: 800 MHz
  Graphics:  Card-1: Intel Device 591b
 Card-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]
 Display Server: X.Org 1.19.6 driver: nvidia
 Resolution: 1920x1080@60.00hz
 GLX Renderer: GeForce GTX 1050 Ti/PCIe/SSE2
 GLX Version: 4.6.0 NVIDIA 396.54
  Audio: Card Intel CM238 HD Audio Controller driver: snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k4.15.0-47-generic
  Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
 driver: r8169
 IF: enp2s0 state: down mac: 
 Card-2: Intel Wireless 3165 driver: iwlwifi
 IF: wlp3s0 state: up mac: 
  Drives:HDD Total Size: 1256.3GB (27.6% used)
 ID-1: /dev/sda model: Micron_1100_SATA size: 256.1GB
 ID-2: /dev/sdb model: TOSHIBA_MQ01ABD1 size: 1000.2GB
  Partition: ID-1: / size: 46G used: 38G (87%) fs: ext4 dev: /dev/sdb3
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 51.0C mobo: N/A gpu: 48C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 258 Uptime: 51 min Memory: 2152.2/15906.5MB
 Client: Shell (bash) inxi: 2.2.35

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR

2019-04-21 Thread Kai-Heng Feng
Ok, please test if microphone works under v4.15.

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

Title:
  Internal microphone not working on Lenovo Ideapad 330S-15ARR

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal microphone on this troublesome laptop stopped working
  after upgrading from Bionic to Cosmic.  There is no signal from the
  microphone with kernel 4.18.0-7 or 4.18.0-8.

  This DOES work correctly with kernel 4.15.0-34 that is still present
  on Cosmic after the upgrade.

  I recommend Canonical gets this laptop for testing since a ton of
  stuff is troublesome on this Raven Ridge laptop.  Would be a good
  specimen to get support for this platform improved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2295 F pulseaudio
   /dev/snd/controlC0:  xorbit 2295 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct  7 12:02:45 2018
  InstallationDate: Installed on 2018-09-20 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago)
  dmi.bios.date: 09/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825736] Re: Mouse scroll wheel barely works after suspend

2019-04-21 Thread Kai-Heng Feng
Is this a regression? Does this issue happen to previous kernel
releases?

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

Title:
  Mouse scroll wheel barely works after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a resuming from a suspend the mouse scroll wheel is almost, but
  not quite, non functional. If you scroll quickly for a while you do
  get a slight movement of the scroll bar to show that there is some
  level of communication, but nothing remotely usable.

  The fix is to use the following commands to remove the hid_generic
  module and reinstate it:

  sudo rmmod hid_generic
  sudo modprobe hid_generic

  Following this all works as expected until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-modules-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1905 F pulseaudio
   /dev/snd/controlC1:  paul   1905 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 19:02:00 2019
  Dependencies:
   
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8032c5f7-74fd-4a23-92cb-5ad7d0642a9f
  InstallationDate: Installed on 2017-12-15 (491 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20238
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=63abd1a6-61ac-485b-9448-47d635ee8808 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-20 (1 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN50WW(V3.09)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G510
  dmi.modalias: 
dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20238
  dmi.product.sku: LENOVO_MT_20238
  dmi.product.version: Lenovo G510
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

2019-04-21 Thread Kai-Heng Feng
Yes it supports 64bit.

https://ark.intel.com/content/www/us/en/ark/products/42104/intel-
celeron-processor-t3500-1m-cache-2-10-ghz-800-mhz-fsb.html

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

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On ubuntu 16.04 settings "do anything when closing lid" is applied.
  Hard reset needs.

  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
   /dev/snd/controlC0:  neslihan   1863 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947
  InstallationDate: Installed on 2018-09-12 (220 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer TravelMate 5335
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BA51_MV
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TravelMate 5335
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1795116] Re: large performance regression (~20-40%) in wifi with 4.15.0-33 and later

2019-04-21 Thread Kai-Heng Feng
This should be fixed in latest bionic kernel, LP: #1788997.

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

Title:
  large performance regression (~20-40%) in wifi with 4.15.0-33 and
  later

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  16.04 install using the HWE stack. after several weeks of uptime on
  -32, an update to -34 showed a major drop in wifi throughput,
  dependent solely on the kernel chosen:

  $  uname -a && ./wifibench.sh 
  Linux brix 4.15.0-32-generic #35~16.04.1-Ubuntu SMP Fri Aug 10 21:54:34 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Tue 25-Sep-18 06:07
  PlatformSDK-SVR2003R2.iso
  429,840,384 100%8.41MB/s0:00:48 (xfr#1, to-chk=0/1)
  sent 429,945,420 bytes  received 35 bytes  8,685,766.77 bytes/sec

  $  uname -a && ./wifibench.sh 
  Linux brix 4.15.0-34-generic #37~16.04.1-Ubuntu SMP Tue Aug 28 10:44:06 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Tue 25-Sep-18 06:14
  PlatformSDK-SVR2003R2.iso
  429,840,384 100%4.83MB/s0:01:24 (xfr#1, to-chk=0/1)
  sent 429,945,420 bytes  received 35 bytes  5,028,601.81 bytes/sec

  (the script is a simple rsync from a NAS. nothing in the NAS, or the
  router, or the physical positions of the devices or etc etc has
  changed, let alone in those 7 minutes).

  there is no interference, no other devices connected, etc.
  prior to the transfer, the link quality is 62-64 and the signal similarly 
weaker because of power saving, but once packets are in flight it looks perfect:

  $  iwconfig 
  wlan0 IEEE 802.11  ESSID:""
Mode:Managed  Frequency:2.452 GHz  Access Point:    
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=70/70  Signal level=10 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:15   Missed beacon:0

  the client is a J1900-based (baytrail) machine with a RTL8723BE wifi module. 
average performance while on -32 was consistently 70-80 Mb/s, over a period of 
several weeks. with -33 and later, it's generally 50-65.
  (that machine has no access to launchpad. i'll try apport-cli over the 
weekend).

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

2019-04-21 Thread Kai-Heng Feng
Please use evtest, press hotkeys, and attach its output.

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825718] Re: Touchpad not detecting in Linux

2019-04-21 Thread Kai-Heng Feng
Please test this kernel:
https://people.canonical.com/~khfeng/lp1825718/

Use the descriptor in i2c-hid-dmi-quirks.c.

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

Title:
  Touchpad not detecting in Linux

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This issue was observed in laptop -"iBall-Aer3" which has a touch-pad with 
integrated fingerprint scanner. Both works very well in Windows 10, but not in 
Linux. 
  Please Check.  
  Any help is highly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dipin  1204 F pulseaudio
   /dev/snd/controlC1:  dipin  1204 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 18:12:35 2019
  InstallationDate: Installed on 2019-04-21 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: iBall Aer3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=53642f8a-ea5c-46e8-bde2-b1744102311b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G
  dmi.board.asset.tag: Default string
  dmi.board.name: Aer3
  dmi.board.vendor: iBall
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Aer3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: iBall

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-04-21 Thread Kai-Heng Feng
For those who doesn't use Ubuntu kernel, this patch may help:
https://lkml.org/lkml/2019/4/22/5

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

2019-04-21 Thread Kai-Heng Feng
> 1. I understand that it is done by command "git bisect reset"
Before doing the reset, run
$ git bisect log > log
To record the current bisection steps.

2. If I understand You well I am already on first regression commit (blank 
screen issue) becouse I can't boot on 4.10-rc2+3 but on 4.9.0+-2 it was 
possible.
Yes.

After the regression commit was found, run
$ git bisect replay log
To resume the original bisection.

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

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-04-21 Thread Kai-Heng Feng
The log in #42 is flooded with:
[  127.470404] i2c_designware i2c_designware.0: timeout waiting for bus ready

So it's actually a different issue needs to be addressed.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective

2019-04-21 Thread Kai-Heng Feng
Does it work if you use `xrandr` command manually?

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

Title:
  Super + p does not work as expected, it's defective

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have 3 monitors (2 landscape and 1 portrait), I normally need to
  change between my monitors due to my setup. If I want to play a game,
  I typically switch to a single monitor (Built-in) then I can switch
  back to Join and everything goes back to normal. That is what I would
  expect but that is NOT what happens.

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

  The first two options work correctly, but the 3rd and 4th options do
  not.

  
  External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.

  
  I am using:
  - Ubuntu 4.15.0-47.50-generic 4.15.18
  - GeForce GTX 1080/PCIe/SSE2
  - I have attached: lspci-vnvn.log

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  With nvidia-driver-418 from: ppa:graphics-drivers/ppa

  $ apt-cache policy nvidia-driver-418
  nvidia-driver-418:
Installed: 418.56-0ubuntu0~gpu18.04.1
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   *** 418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status


  I am not sure if this is actually necessary because I don't think this
  has to do with the graphics card.

  I am not sure what other information you will need for this report. I can 
provide more data upon request.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (298 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825554] Re: Ryzen5 2500U Vega 8 raven ridge flickering screen

2019-04-21 Thread Kai-Heng Feng
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc5 kernel [0].

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”, and attach dmesg.

Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc5/

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

Title:
  Ryzen5 2500U Vega 8 raven ridge flickering screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
  My display is flickering, depending on the displayed content in different 
frequency.

  Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-09 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.0-05-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-09 (161 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.8-050008-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1825490] Re: Bug in the update of ubuntu 18.10 to 19.04

2019-04-21 Thread Kai-Heng Feng
** Package changed: linux (Ubuntu) => texinfo (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/1825490

Title:
  Bug in the update of ubuntu 18.10 to 19.04

Status in texinfo package in Ubuntu:
  Confirmed

Bug description:
  First in the upgrade I had a notification like the install-info were
  not installed correctly. After, at the end after the next part of the
  installation, they say that the upgrade has not been completed and
  that a restauration will be made. Then a new page was opened to say
  that the upgrade was made successfully. After this, everything was
  closed but the part of the cleaning and restarting was not made so I
  restarted my computer and I was on ubuntu 19.04 but a new notification
  said me that I had software bug so I send the report.

  (It was an upgrade from the last update of Ubuntu 18.10, I made an
  update before the upgrade, to the 19.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolasb   1854 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 10:50:23 2019
  InstallationDate: Installed on 2019-02-27 (50 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04ca:706d Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f6f4518b-e644-4545-86f7-061cb36bda20 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.06.00
  dmi.board.name: 837D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.32.00
  dmi.chassis.asset.tag: 5CD82354RB
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.06.00:bd01/03/2019:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.32.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 450 G5
  dmi.product.sku: 1LU55AV
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in

2019-04-21 Thread Kai-Heng Feng
Please use /etc/modprobe.d or kernel parameter instead of sysctl.conf.

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

Title:
  Ubuntu freezes when AC 430 WiFi Dongle is plugged in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu crashes after a short time after plugging in the WiFi stick
  "AC430". The kernel fails to load the driver and the following message
  appears repeatedly:

  [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  ...

  Tested with Kernel 4.19 and 5.0 (5.0.2)
  Tested with the following distributions:
  Ubuntu Cosmic Cuttlefish 18.10
  Ubuntu Studio 18.10
  Ubuntu Disco Dingo 19.04

  40-usb_modeswitch.rules was already modified to load the driver, otherwise 
the system chooses Driver=option.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-03-31 (13 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.2-050002-lowlatency x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare 
scanner sudo tape vboxusers video
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR

2019-04-20 Thread Kai-Heng Feng
Do you use the same laptop as the original bug reporter?

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

Title:
  Internal microphone not working on Lenovo Ideapad 330S-15ARR

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal microphone on this troublesome laptop stopped working
  after upgrading from Bionic to Cosmic.  There is no signal from the
  microphone with kernel 4.18.0-7 or 4.18.0-8.

  This DOES work correctly with kernel 4.15.0-34 that is still present
  on Cosmic after the upgrade.

  I recommend Canonical gets this laptop for testing since a ton of
  stuff is troublesome on this Raven Ridge laptop.  Would be a good
  specimen to get support for this platform improved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2295 F pulseaudio
   /dev/snd/controlC0:  xorbit 2295 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct  7 12:02:45 2018
  InstallationDate: Installed on 2018-09-20 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago)
  dmi.bios.date: 09/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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   >