[Kernel-packages] [Bug 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode

2018-10-28 Thread Shih-Yuan Lee
** Description changed:

  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.
  
  
  $ nvidia-settings
  
  ERROR: NVIDIA driver is not loaded
  
  ERROR: Unable to load info from any available system
  
  
- However `prime-select nvidia` still works fine.
+ However `prime-select nvidia` still works fine and there is no such
+ issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates.
  
  Private Bug: https://bugs.launchpad.net/bugs/1800081

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  
  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system
  

  However `prime-select nvidia` still works fine and there is no such
  issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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


[Kernel-packages] [Bug 1798708] Re: It will load nvidia driver when swith to Intel mode

2018-10-28 Thread Bin Li
Here is another workaround. When  in Nvidia mode, do below commands.

First add/edit nvidia-kms.conf, comment out "options nvidia-drm
modeset=1", it will fix the external monitor issue.

$ prime-select intel # It will generate /lib/moprobe.d/blacklist-nvidia.conf
$ update-initramfs -u

These will fix the nvidia or noveau loaded in intel mode.

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

Title:
  It will load nvidia driver when swith to Intel mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We found the nvidia-prime will not run update-initramfs as before.
  After switch to intel, then reboot I found the nvidia modules was loaded. 

  If I did S3 or close the lid, and resume back, the nvidia modules was
  removed, so the gnome session will be reloaded, you need to login
  again, all the opend applications in this session was gone.

  nvidia-prime 0.8.8.1
  linux 4.15.0-1021-oem
  nvidia-driver-390 380.87-0ubuntu0~gpu18.04.1.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2218 F pulseaudio
   /dev/snd/controlC0:  u  2218 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-sutton-bionic-amd64-20181018-40+sutton-mccarthy-bionic-amd64+iso
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2b45d917-3587-410f-9b94-f52eb082b7dc
  InstallationDate: Installed on 2018-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20181018-09:17
  MachineType: LENOVO 20MEZ480US
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-oem 
root=UUID=e68fa8d5-22f5-464b-9775-753b4ae159eb ro noprompt quiet splash 
acpi_osi=! acpi_osi=Linux-Lenovo-NV-HDMI-Audio vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-oem N/A
   linux-backports-modules-4.15.0-1021-oem  N/A
   linux-firmware   1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-1021-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET30W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MEZ480US
  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:bvrN2EET30W(1.12):bd10/04/2018:svnLENOVO:pn20MEZ480US:pvrThinkPadP1:rvnLENOVO:rn20MEZ480US:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MEZ480US
  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/1798708/+subscriptions

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


[Kernel-packages] [Bug 1789465] Re: BUG: scheduling while atomic: irq/142-iwlwifi/383/0x7ffffc00

2018-10-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  BUG: scheduling while atomic: irq/142-iwlwifi/383/0x7c00

Status in linux package in Ubuntu:
  Expired

Bug description:
  Not doing anything in particular other than using wifi on my laptop.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-7-generic 4.17.0-7.8
  ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
  Uname: Linux 4.17.0-7-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Fri Aug 24 15:56:50 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=a9ecc827-5a24-4152-82b8-46517f36c610
  InstallationDate: Installed on 2016-09-01 (725 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  MachineType: LENOVO 20FRS2FK00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-7-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: scheduling while atomic: irq/142-iwlwifi/383/0x7c00
  UpgradeStatus: Upgraded to cosmic on 2018-08-18 (9 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  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: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1789581] Re: ubuntu_ecryptfs test hang on Cosmic

2018-10-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ubuntu_ecryptfs test hang on Cosmic

Status in linux package in Ubuntu:
  Expired

Bug description:
  The test will hang with:
  tests/run_one.sh -K -t lp-994247.sh -b 100 -D /mnt/image -l /mnt/lower -u 
/mnt/upper -f ext2

  With 100% reproducible rate.

  It looks like this is related to a package upgrade, not the kernel
  itself:

  The following NEW packages will be installed:
fontconfig-config fonts-dejavu-core libcairo2 libfontconfig1 libipt1 
libpixman-1-0 libxcb-render0 libxcb-shm0 libxrender1 python-cairo
python3-cairo
  The following packages will be upgraded:
bzip2 curl dpkg gdb gdbserver gir1.2-glib-2.0 grep init init-system-helpers 
iproute2 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dbg
libc6-dev libc6-dev-i386 libc6-dev-x32 libc6-i386 libc6-x32 libcurl3-gnutls 
libcurl4 libdb5.3 libgirepository-1.0-1 libglib2.0-data
liblxc-common liblxc1 libnss-systemd libpam-systemd libssl1.1 libsystemd0 
libudev1 libuv1 libx11-6 libx11-data libxml2 locales
multiarch-support openssl python-apt-common python-gi python3-apt 
python3-debian python3-distupgrade python3-gi python3-twisted
python3-twisted-bin systemd systemd-sysv ubuntu-release-upgrader-core udev 
unattended-upgrades

  The hang issue happens after a dist-upgrade with -proposed enabled,
  packages above is the upgrade candidate.

  Steps:
   1. Deploy a node with Cosmic
   2. Run the following commands:
  sudo apt-get install git python-minimal gdb -y
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  rm -fr autotest/client/tests
  ln -sf ~/autotest-client-tests autotest/client/tests
  AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_ecryptfs/control
   3. Enable -proposed, run dist-upgrade and reboot
   4. Repeat step 2.

  The first round will pass without any problem, but the test will hang
  with step 4.

  Which package is causing this issue is still unknown.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: User Name 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 29 08:11 seq
   crw-rw 1 root audio 116, 33 Aug 29 08:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed Aug 29 08:37:52 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=a343a3f9-f1b0-426d-bfb0-3ecdb1aa2635 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode

2018-10-28 Thread Shih-Yuan Lee
** Description changed:

  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.
  
+ 
  $ nvidia-settings
  
  ERROR: NVIDIA driver is not loaded
  
  ERROR: Unable to load info from any available system
+ 
  
  However `prime-select nvidia` still works fine.
  
  Private Bug: https://bugs.launchpad.net/bugs/1800081

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  
  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system
  

  However `prime-select nvidia` still works fine.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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


[Kernel-packages] [Bug 1800413] [NEW] It can not use nvidia-settings to switch from the power saving mode to the performance mode

2018-10-28 Thread Shih-Yuan Lee
Public bug reported:

I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
But it failed.

$ nvidia-settings

ERROR: NVIDIA driver is not loaded

ERROR: Unable to load info from any available system

However `prime-select nvidia` still works fine.

Private Bug: https://bugs.launchpad.net/bugs/1800081

** Affects: nvidia-drivers-ubuntu
 Importance: Undecided
 Status: Confirmed

** Affects: oem-priority
 Importance: Undecided
 Status: Confirmed

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic somerville

** Also affects: nvidia-drivers-ubuntu
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: bionic somerville

** Description changed:

  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.
  
  $ nvidia-settings
  
  ERROR: NVIDIA driver is not loaded
  
  ERROR: Unable to load info from any available system
  
  However `prime-select nvidia` still works fine.
+ 
+ Private Bug: https://bugs.launchpad.net/bugs/1800081

** Changed in: nvidia-drivers-ubuntu
   Status: New => Confirmed

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system

  However `prime-select nvidia` still works fine.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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


[Kernel-packages] [Bug 1799875] Re: Kernel Crash - consisten when shutting down the system

2018-10-28 Thread Stephen Smith
I didn't want the possibility of corrupting a HD from trying to shutdown
my system had have the kernel crash every time.   I therefore reverted
to 18.04LTS.

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

Title:
  Kernel Crash  - consisten when shutting down the system

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  When every I run "sudo sync && sudo shutdown -h now" I experience an
  immediate kernel crash.  This is 100% repeatible on my system.

  I have the 18.10 release installed with all patches applied.

  lsb_release -rd:
  Description:Ubuntu 18.10
  Release:18.10

  cat /proc/version_signature
  Ubuntu 4.18.0-10.11-generic 4.18.12

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steves 2854 F pulseaudio
   /dev/snd/controlC1:  steves 2854 F pulseaudio
  Date: Wed Oct 24 22:20:13 2018
  HibernationDevice: RESUME=UUID=84b37d15-2872-40b9-b406-0600c9d5f6f5
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   enp30s0   no wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=05bb8d54-5c84-4752-aeae-a50ab6542e93 ro quiet splash vt.handoff=1
  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.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-25 (0 days ago)
  dmi.bios.date: 02/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd02/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1800316] Re: Loss of network connectivity

2018-10-28 Thread Stephen Smith
I rolled back to 18.04LTS.  I can comment on what I saw while using
18.10, but I no longer have it on my HD

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

Title:
  Loss of network connectivity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.10 I consistently lose network connectivity after some
  time.   When trying to submit the but an hour ago I lost connectivity
  just prior to clicking submit.

  Runing "sudo /etc/init.d/network-manager restart" re-initalizaes the
  system, but I am still unable to ping or otherwise communicate with
  the wireless router at my home.  My linux box is hard wired to the
  wireless router.

  I have been using Ubuntu for for approx 12years and never experienced
  this problem.

  The only solution is a reboot, but there are problems with that too.
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799875

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

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


[Kernel-packages] [Bug 1800227] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]

2018-10-28 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1526155 ***
https://bugs.launchpad.net/bugs/1526155

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1526155, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build
+ nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build 
[cc: error: unrecognized command line option ‘-fstack-protector-strong’]

** This bug has been marked a duplicate of bug 1526155
   nvidia-* kernel module failed to build [cc: error: unrecognized command line 
option ‘-fstack-protector-strong’]

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

Title:
  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build [cc: error: unrecognized command line option ‘-fstack-
  protector-strong’]

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Having trouble installing the NVIDIA driver as found in the synaptic
  package manager list.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  It downloaded and tried to build, which failed.  That is all I know.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-36-generic
  Date: Fri Oct 26 15:20:00 2018
  DuplicateSignature: dkms:nvidia-dkms-390:390.77-0ubuntu0.18.04.1:cc: error: 
unrecognized command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2017-01-04 (660 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageVersion: 390.77-0ubuntu0.18.04.1
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed 
to build
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800227/+subscriptions

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


[Kernel-packages] [Bug 1800348] Re: nvidia-kernel-source-390 (not installed): nvidia kernel module failed to build [/usr/bin/ld.bfd: Relocatable linking with relocations from format elf32-i386 (...) t

2018-10-28 Thread Daniel van Vugt
** Summary changed:

- nvidia-kernel-source-390 (not installed): nvidia kernel module failed to build
+ nvidia-kernel-source-390 (not installed): nvidia kernel module failed to 
build [/usr/bin/ld.bfd: Relocatable linking with relocations from format 
elf32-i386 (...) to format elf64-x86-64 (...) is not supported]

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

Title:
  nvidia-kernel-source-390 (not installed): nvidia kernel module failed
  to build [/usr/bin/ld.bfd: Relocatable linking with relocations from
  format elf32-i386 (...) to format elf64-x86-64 (...) is not supported]

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  sudo apt upgrade

  /etc/kernel/header_postinst.d/dkms:
  Secure Boot not enabled on this system.
  Error! Bad return status for module build on kernel: 4.15.0-38-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia/390.77/build/make.log for more information. 
  --> make.log attached.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-source-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-38-generic
  Date: Sun Oct 28 14:04:31 2018
  InstallationDate: Installed on 2018-06-30 (120 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: (not installed)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 (not installed): nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800348/+subscriptions

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


[Kernel-packages] [Bug 1800292] Re: [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

2018-10-28 Thread Daniel van Vugt
** No longer affects: nvidia-graphics-drivers-390 (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After turn on my computer and my Ubuntu install updates today (Oct 27), I 
restarted to apply the updates and my mouse started do auto click 2-3 times in 
sequence every 1-2 minutes.
  I tried to restart, tried to unplug my mouse but it keep happening.
  Its infuriating, because im watching youtube fullscreen and every 1-2 minutes 
it clicks and stop the video and go out full screen, so I need to play again 
and go to fullscreen again, just to 1-2 minutes later repeat all over again.

  ---

  At the moment, I suspect two possibilities:

  1° There are problems with the driver
  2° The mouse is damaged
  --
  Cristian

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 27 12:54:34 2018
  DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:131d]
     Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d]
  InstallationDate: Installed on 2018-06-07 (141 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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: Sat Oct 27 12:24:30 2018
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to release device: Device not taken
  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/1800292/+subscriptions

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


[Kernel-packages] [Bug 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

2018-10-28 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => 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/178

Title:
  [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  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:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1800118] Re: NVHDA does not persist after Suspend or Hibernating

2018-10-28 Thread Daniel van Vugt
** Summary changed:

- [OMEN X by HP Laptop 17-ap0xx, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] 
Playback problem
+ NVHDA does not persist after Suspend or Hibernating

** No longer affects: pulseaudio (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/1800118

Title:
  NVHDA does not persist after Suspend or Hibernating

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Below is a Cut and paste of a recent Ubuntu Forum Page where I posted the 
issues
  https://ubuntuforums.org/showthread.php?t=2404566
  Note that though it says "Solved" it is just workarounds of Bigger ACPI 
Issues!

  ubuntu 18.10

  OK,

  This is a new thread, and I will make it HUGE!
  Edit Solution/ Work Around for the "2/" Problem
  see Post # 4, Thanks PeterSaints 

  Ubuntu, Please Listen!

  Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, or 
HDMI Audio, or Surround Sound 5.1-7.1 etc. ...
  NVHDA stands for Nvidia HDA. Just for anyone who does not know the Jargon! 

  What does Work ... (and I will post ALL my Notes and Links for others below!)
  1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and 
  2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend!

  First my System, and most importantly is it is a NEW Cutting Edge Hp Omen X 
Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel!
  -Computer-
  Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz
  Memory: 16245MB (3330MB used)
  Machine Type  : Notebook
  Operating System  : Ubuntu 18.10
  -Display-
  Resolution: 1920x1080 pixels
  OpenGL Renderer   : GeForce GTX 1080/PCIe/SSE2
  X11 Vendor: The X.Org Foundation

  -Audio Devices-
  Audio Adapter : HDA-Intel - HDA Intel PCH
  Audio Adapter : HDA-Intel - HDA NVidia
  -Input Devices-

  Video Bus
  ST LIS3LV02DL Accelerometer
  HDA Intel PCH Mic
  HDA Intel PCH Mic
  HDA Intel PCH Headphone
  HP WMI hotkeys
  HDA NVidia HDMI/DP,pcm:3
  HDA NVidia HDMI/DP,pcm:7
  HDA NVidia HDMI/DP,pcm:8
  So the LATEST 2 Problems I am looking for a SOLUTION that would indeed help 
THOUSANDS and/or MILLIONS of people Now and/or in the near future! 
  1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem!
  and MORE IMPORTANTLY!

  2/ Why is the fixed Patch System NOT working after a Suspend or Hibernation
  (Yes I am reiterating my issue once again!)
  After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, 
  1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or 
  2/ Visible but in a Dysfunctional State, ... Showing 3 version of the NVHDA 
0,1&2 ...
  and NONE of the 3 (three) WORK! to be clear NO SOUND AT ALL! when testing 
them. 

  So I will leave it here, and to show my continued Good Faith and
  Obvious Continued Support For Ubuntu, below are ALL my Solutions to
  Date!

  1st Solution - 
  Install the patch to get the INVISIBLE and/or Unloaded HDA Visible and/or 
Loaded
  ∘ I can confirm that kernel module, posted by 
  ‣ Maik Freudenberg (https://bugs.freedesktop.org/show_bug.cgi?id=75985#c27),
  • Kernel module to toggle audio function
  ∘ is working fine on my system. Thank you for the fix. The HDMI audio device 
now works as it should (now detected).
  ∘ The steps I did to enable HDMI audio device:
  • 1. Download and extract the file nvhda.tar.xz. (from above link)
  • 2. Run these commands in Terminal, in the location of the extracted folder 
  Code:
  • $ make
  • $ sudo make install
  • $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules
  • $ echo "options nvhda load_state=1" | sudo tee /etc/modprobe.d/nvhda.conf
  • $ sudo update-initramfs -u
  ‣ 3. Reboot.
  ## SOLVED ## ###

  2nd Solution
  Hibernation/Suspend Working (Not HDA Sound of Course)

  Troubleshooting
  ‣ Prerequisites - does your kernel support suspend-to-disk?
  • Kernel supports whatever is listed in /sys/power/state, so:
  Code:
  cat /sys/power/state
  ∘ Allowed (to my knowledge) entries there include: mem, standby, freeze, 
disk. Explanation:
  ‣ mem - has several meanings, which one exactly on your system you'll find 
out via cat /sys/power/mem_sleep. I have: s2idle [deep]
  ‣ standby - Power-On Suspend (if supported)
  ‣ freeze - Suspend To Idle (STI)
  ‣ disk - Hibernate - Suspend To Disk (STD), This - you want.
  ∘ mine says : freeze mem disk - PERFECT!

  • Then we need to check
  Code:
  $ cat /sys/power/disk
  ‣ If (good) shows ... 
  ‣ [platform] shutdown reboot suspend test_resume 

  • if : (Bad)
  • [disabled] 
  • (not very good)
  ‣ Enable Hibernate and put it in menu - Easy-Peasy

  • Software Prerequisites
  Code:
  sudo apt install pm-utils  cpufrequtils
  1. Edit a specific file with this command.
  Code:
   sudo gedit 
/var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla
  ∘ 2. Scroll down the Text Document and find the 

[Kernel-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back

2018-10-28 Thread Daniel van Vugt
It looks like you both indeed are hitting the same kernel crash in
'amdgpu'.

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

Title:
  Ubuntu  18.10 After Blank Screen System Won't Come Back

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.10 if the blank screen feature initiates (5 minutes
  default) the system will remain blank and there is no way to get the
  display back on without a hard reset. The video card I am using is a
  Vega 64. Other users who have Vega AMD GPU's are experiencing the same
  issue. This is only happening in Ubuntu 18.10. Does not occur in my
  Arch or Fedora installs.

  To reproduce:
  - Let 'Blank Screen' feature execute (5 min default)
  - Screen will not come back

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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
  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: Thu Oct 25 10:18:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
  InstallationDate: Installed on 2018-10-19 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Micro-Star International Co., Ltd. MS-7B78
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.20
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PRO CARBON (MS-7B78)
  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.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B78
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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


[Kernel-packages] [Bug 1795256] Re: frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-28 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
  00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

  
  aravind@comp:~$ sudo lshw
  [sudo] password for aravind: 
  comp
  description: Notebook
  product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
  vendor: Acer
  version: V1.25
  serial: NXGDWSI034717145457600
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
*-core
 description: Motherboard
 product: Ironman_SK
 vendor: Acer
 physical id: 0
 version: V1.25
 serial: NBGD411006717145457600
 slot: Type2 - Board Chassis Location
   *-firmware
description: BIOS
vendor: Insyde Corp.
physical id: 0
version: V1.25
date: 03/03/2017
size: 128KiB
capacity: 4544KiB
capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
   *-cpu
description: CPU
product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
flush_l1d cpufreq
configuration: cores=2 enabledcores=2 threads=4
  *-cache:0
   description: L1 cache
   

[Kernel-packages] [Bug 1798827] Re: Gnome Display Manager stop after installing Nvidia driver

2018-10-28 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1798790, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1798790
   Ubuntu 18.10 login screen never appears when using the Nvidia driver

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

Title:
  Gnome Display Manager stop after installing Nvidia driver

Status in gdm3 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  At first boot the system boots normally, but at restart after a
  shutdown or restart the boot is frozen in the Nvidia Persistence
  Daemon message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 10:39:14 2018
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-10-28 Thread AzureRaptor
I have installed the "edge" hwe packages as denoted in these two
comments:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/comments/148

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/comments/149

I can confirm that after this action hibernation is working properly for
me.  Previously I was stuck on a specific mainline 4.15 release and was
afraid to move off it; hibernation is vital for my workflow (and sanity
in general).

: uname -a
Linux hostname 4.15.0-38-generic #41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

-- 
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:
  Confirmed
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 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-10-28 Thread Lehel Gyuro
Missed one difference, so it should read:

snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lehel  1673 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0
  InstallationDate: Installed on 2017-04-30 (499 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! 
"acpi_osi=Windows 2009"
  ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-lowlatency N/A
   linux-backports-modules-4.15.0-34-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-34-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Kernel-packages] [Bug 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-10-28 Thread Lehel Gyuro
Hi Felipe

The symptoms you report are different from the one reported by me. Your are 
able to use the headphone output, while in my case the headphone output is not 
detected at all by the driver.
Could you please look up the alsa initialization section in your dmesg?
As stated before the issue reported in this bug is generating the following 
output:

snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0)

In your case my guess is, you will see:

snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 (0x1b/0x0/0x0/0x0/0x0)

BR
Lehel

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lehel  1673 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0
  InstallationDate: Installed on 2017-04-30 (499 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! 
"acpi_osi=Windows 2009"
  ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-lowlatency N/A
   linux-backports-modules-4.15.0-34-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-34-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-28 Thread Alex Garel
@grzesiekc thanks for the comment, on my side I have no such specific
content.

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver 
cannot change properties on a disabled device
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:65
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1  - 
Power Button: is tagged by udev as: 

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2018-10-28 Thread Dan Christian
I'm seeing this as well in 18.10 with an Apple MagicTouch 1 bluetooth connected 
to an Asus laptop.
It disconnects every few minutes of use and then reconnects after about 30sec.

Oct 28 09:37:39 marconi bluetoothd[979]: Can't get HIDP connection info
Oct 28 09:37:41 marconi kernel: [48771.558941] magicmouse 0005:05AC:030E.000C: 
unknown main item tag 0x0
Oct 28 09:37:41 marconi kernel: [48771.559239] input: Apple Wireless Trackpad 
as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.000C/input/input33
Oct 28 09:37:41 marconi kernel: [48771.559685] magicmouse 0005:05AC:030E.000C: 
input,hidraw6: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
44:03:2c:ea:91:00
Oct 28 09:37:41 marconi upowerd[1497]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.000C/power_supply/hid-cc:c7:60:f1:9c:a9-battery

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

2018-10-28 Thread Damian Campbell
Thanks @Ryan for the post. I'm not sure in this case that a bisection would be 
the most effective cure. There must be many many legacy Dell and other machines 
that are affected but we never know because people give up on the install. I 
think the suggestion (see somewhere above) of defaulting to having the 
workaround "Video=SVIDEO-1:d" enabled by default would be much more useful. The 
probable minority of users who do need to use SVIDEO could be dealt with 
through release note information and pointed to a legacy driver.

As an enthusiastic and fervent champion of Ubuntu I cannot emphasize
enough the negatives a fraught install/upgrade process for non-IT users
inflicts upon the reputation of the project. Far better to have a few
non-working features than to alienate a whole section of users with
legacy machines. After all, is Ubuntu not supposed to be "Great for use
with legacy machines."?? My experience rendered a working system on
16.04 LTS totally unusable by the automatic upgrade to 18.04 LTS. I am
surely not alone!!!??

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  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.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed 

[Kernel-packages] [Bug 1799998] Re: [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

2018-10-28 Thread Cristian Aravena Romero
** Summary changed:

- 20% of volume is like 0%
+ [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

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

Title:
  [Intel Corporation Sunrise Point-LP HD Audio] 20% of volume is like 0%

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is no sound on my laptop when volume is set to 20% or less.
  Also, when I set it to 100%, its output is lower than on Windows.
  The problem occurs when using a headphone as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   roinujnosde   1600 F...m pulseaudio
   /dev/snd/controlC0:  roinujnosde   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 13:33:21 2018
  InstallationDate: Installed on 2018-10-09 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Volume slider, or mixer problems
  Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  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:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1800292] Re: [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

2018-10-28 Thread Rodrigo Melotto
Update:

Hello Cristian,
So I havent changed anything, im watching Youtube all day long today and the 
autoclicks just stopped.
Since it was happening nonstop yesterday but today it didnt had one single 
"auto" click I think its over.
Lets wait for one more day and I think it can be closed.


*Just to stress that I didnt do anything to mouse/touchpad/video drivers. 
Yesterday before I open this topic I've shutdown my note and turn it on again 
but the autoclicks persisted.
I turned of my note the whole night.
I dont use any macro of any kind, be it mouse, keyboard or whatever.
Its weird.

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

Title:
  [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After turn on my computer and my Ubuntu install updates today (Oct 27), I 
restarted to apply the updates and my mouse started do auto click 2-3 times in 
sequence every 1-2 minutes.
  I tried to restart, tried to unplug my mouse but it keep happening.
  Its infuriating, because im watching youtube fullscreen and every 1-2 minutes 
it clicks and stop the video and go out full screen, so I need to play again 
and go to fullscreen again, just to 1-2 minutes later repeat all over again.

  ---

  At the moment, I suspect two possibilities:

  1° There are problems with the driver
  2° The mouse is damaged
  --
  Cristian

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 27 12:54:34 2018
  DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:131d]
     Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d]
  InstallationDate: Installed on 2018-06-07 (141 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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: Sat Oct 27 12:24:30 2018
  xserver.configfile: default
  xserver.errors: systemd-logind: failed 

[Kernel-packages] [Bug 1800292] Re: [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

2018-10-28 Thread Cristian Aravena Romero
** Summary changed:

- Mouse click every 1-2 minutes
+ [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

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

Title:
  [Logitech G403 Prodigy Gaming Mouse] Mouse click every 1-2 minutes

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After turn on my computer and my Ubuntu install updates today (Oct 27), I 
restarted to apply the updates and my mouse started do auto click 2-3 times in 
sequence every 1-2 minutes.
  I tried to restart, tried to unplug my mouse but it keep happening.
  Its infuriating, because im watching youtube fullscreen and every 1-2 minutes 
it clicks and stop the video and go out full screen, so I need to play again 
and go to fullscreen again, just to 1-2 minutes later repeat all over again.

  ---

  At the moment, I suspect two possibilities:

  1° There are problems with the driver
  2° The mouse is damaged
  --
  Cristian

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Oct 27 12:54:34 2018
  DistUpgraded: 2018-09-08 12:06:34,639 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-34-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:131d]
     Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 840M] [1043:131d]
  InstallationDate: Installed on 2018-06-07 (141 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X550LN
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic 
root=UUID=85a00f13-8692-4416-97cd-968f2bb3c697 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (49 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LN.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LN.305:bd05/14/2014:svnASUSTeKCOMPUTERINC.:pnX550LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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: Sat Oct 27 12:24:30 2018
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to release device: Device not taken
  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/1800292/+subscriptions

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


[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

2018-10-28 Thread Ryan C. Underwood
This should be bisectable, but I don't think anyone has done it 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/1685442

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  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.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  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.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2018-10-28 Thread Oded Arbel
Just got hit with the problem again, after the 1.11.0 firmware upgrade,
on Cosmic:

[428188.916420] xhci_hcd :0e:00.0: ERROR unknown event type 15
[428193.955247] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
[428193.955570] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
[428193.955670] usb 3-1.5: Failed to suspend device, error -22
[428193.955707] xhci_hcd :0e:00.0: HC died; cleaning up
[428193.955710] usb 4-1.1.1: Failed to suspend device, error -22
[428193.955768] usb 3-1: USB disconnect, device number 2
[428193.955770] usb 3-1.1: USB disconnect, device number 3
[428193.955773] usb 3-1.1.1: USB disconnect, device number 5
[428193.955776] usb 3-1.1.1.1: USB disconnect, device number 7
[428193.955779] usb 3-1.1.1.1.4: USB disconnect, device number 9
[428193.955923] usb 4-1: USB disconnect, device number 2
[428193.955926] usb 4-1.1: USB disconnect, device number 3
[428193.955927] usb 4-1.1.1: USB disconnect, device number 5
[428193.956974] usb 4-1.2: USB disconnect, device number 4
[428194.196633] usb 3-1.1.1.3: USB disconnect, device number 8
[428194.277991] usb 3-1.1.1.5: USB disconnect, device number 10
[428194.278531] usb 3-1.1.5: USB disconnect, device number 6
[428194.279067] usb 3-1.5: USB disconnect, device number 4

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

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

Title:
  USB over thunderbolt turns off every once in a while

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

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd :0e:00.0: remove, state 1

   
  [279389.814110] usb usb3: USB disconnect, device number 1 

   
  [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered 

   
  [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller   

[Kernel-packages] [Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

2018-10-28 Thread WinEunuchs2Unix
@@Kai-Heng Feng (kaihengfeng) Everything seems to be fixed for both this
old bug and for new problems I was having over last few days.

I found a bug report from 2010 (link in script below) and used this:

#!/bin/bash

# Original script was using /bin/sh but shellcheck reporting warnings.

# NAME: custom-xhci_hcd
# PATH: /lib/systemd/system-sleep
# CALL: Called from SystemD automatically
# DESC: Suspend broken for USB3.0 as of Oct 25/2018 various kernels all at once

# DATE: Oct 28 2018.

# NOTE: From comment #61 at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998

TMPLIST=/tmp/xhci-dev-list

# Original script was: case "${1}" in hibernate|suspend)

case $1/$2 in
  pre/*)
echo "$0: Going to $2..."
echo -n '' > $TMPLIST
  for i in `ls /sys/bus/pci/drivers/xhci_hcd/ | egrep 
'[0-9a-z]+\:[0-9a-z]+\:.*$'`; do
  # Unbind xhci_hcd for first device :XX:XX.X:
   echo -n "$i" | tee /sys/bus/pci/drivers/xhci_hcd/unbind
   echo "$i" >> $TMPLIST
  done
;;
  post/*)
echo "$0: Waking up from $2..."
for i in `cat $TMPLIST`; do
  # Bind xhci_hcd for first device :XX:XX.X:
  echo -n "$i" | tee /sys/bus/pci/drivers/xhci_hcd/bind
done
rm $TMPLIST
;;
esac

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

Title:
  Laptop wakes up immediately after suspend or hibernation

Status in linux package in Ubuntu:
  Expired

Bug description:
  After going into suspend (via command line or lid close), the MacBook
  Pro (early 2015) wakes up immediately again. Same for hibernation.
  Running Ubuntu 18.04.

  extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open
  cycle:

  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [ ... ]
  [  778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table 
err:-23
  [  783.011399] PM: suspend entry (deep)
  [  783.011400] PM: Syncing filesystems ... done.
  [  783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  783.030844] OOM killer disabled.
  [  783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  783.032193] Suspending console(s) (use no_console_suspend to debug)
  [  783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache
  [  783.054107] sd 1:0:0:0: [sda] Stopping disk
  [  783.146124] thunderbolt :07:00.0: suspending...
  [  783.146685] thunderbolt :07:00.0: suspend finished
  [  783.146689] thunderbolt :07:00.0: stopping RX ring 0
  [  783.146698] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [  783.146710] thunderbolt :07:00.0: stopping TX ring 0
  [  783.146718] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [  783.146725] thunderbolt :07:00.0: control channel stopped
  [  783.246464] ACPI: Preparing to enter system sleep state S3
  [  783.418015] ACPI: EC: event blocked
  [  783.418016] ACPI: EC: EC stopped
  [  783.418018] PM: Saving platform NVS memory
  [  783.418027] Disabling non-boot CPUs ...
  [  783.434574] IRQ 65: no longer affine to CPU1
  [  783.435629] smpboot: CPU 1 is now offline
  [  783.454574] IRQ 66: no longer affine to CPU2
  [  783.456378] smpboot: CPU 2 is now offline
  [  783.478405] IRQ 21: no longer affine to CPU3
  [  783.478414] IRQ 43: no longer affine to CPU3
  [  783.478435] IRQ 71: no longer affine to CPU3
  [  783.479449] smpboot: CPU 3 is now offline
  [  783.481656] ACPI: Low-level resume complete
  [  783.481733] ACPI: EC: EC started
  [  783.481734] PM: Restoring platform NVS memory
  [  783.482160] Enabling non-boot CPUs ...
  [  783.482240] x86: Booting SMP configuration:
  [  783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  783.558589]  cache: parent cpu1 should not be sleeping
  [  783.687159] CPU1 is up
  [  783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1
  [  783.687812]  cache: parent cpu2 should not be sleeping
  [  783.688001] CPU2 is up
  [  783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  783.783709]  cache: parent cpu3 should not be sleeping
  [  783.978233] CPU3 is up
  [  783.982020] ACPI: Waking up from system sleep state S3
  [  784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.112655] thunderbolt :07:00.0: control channel starting...
  [  784.112660] 

[Kernel-packages] [Bug 1795116] Re: large performance regression (~20-40%) in wifi with 4.15.0-33 and later

2018-10-28 Thread arQon
given the link quality observations in #11 and the behavior in #12, it's
pretty clear that the problem is with the radio power management.

since it isn't improved at all via any of the PM settings, that suggests
it's simply broken rather than overly-aggressive.

for reference, the head for the last good version of the driver is
6A56582B1FEECB841E329C4

-- 
You 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 1774994] Re: Laptop wakes up immediately after suspend or hibernation

2018-10-28 Thread WinEunuchs2Unix
@Kai-Heng Feng (kaihengfeng) just an update...

Suddenly my suspend totally broke down (wakes immediately from suspend)
using same kernel I had for a few months (outdated `4.13.0-36-generic`).

In order to update to newer kernels I had to install libssl1.1 to side-
step linux-header installation errors.

Either libsl1.1 or newer kernels broke dkms makefile's for nvidia,
bbswitch, virtual box, etc. So I had to use: `sudo apt install libelf-
dev`

I ended up successfully upgrading to mainline kernel `4.14.78` but now
suspend takes 30 seconds to break and goes to login screen instead.

So I'm out of the frying pan and into the fire...

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

Title:
  Laptop wakes up immediately after suspend or hibernation

Status in linux package in Ubuntu:
  Expired

Bug description:
  After going into suspend (via command line or lid close), the MacBook
  Pro (early 2015) wakes up immediately again. Same for hibernation.
  Running Ubuntu 18.04.

  extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open
  cycle:

  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [ ... ]
  [  778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table 
err:-23
  [  783.011399] PM: suspend entry (deep)
  [  783.011400] PM: Syncing filesystems ... done.
  [  783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  783.030844] OOM killer disabled.
  [  783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  783.032193] Suspending console(s) (use no_console_suspend to debug)
  [  783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache
  [  783.054107] sd 1:0:0:0: [sda] Stopping disk
  [  783.146124] thunderbolt :07:00.0: suspending...
  [  783.146685] thunderbolt :07:00.0: suspend finished
  [  783.146689] thunderbolt :07:00.0: stopping RX ring 0
  [  783.146698] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 12 (0x1001 -> 0x1)
  [  783.146710] thunderbolt :07:00.0: stopping TX ring 0
  [  783.146718] thunderbolt :07:00.0: disabling interrupt at register 
0x38200 bit 0 (0x1 -> 0x0)
  [  783.146725] thunderbolt :07:00.0: control channel stopped
  [  783.246464] ACPI: Preparing to enter system sleep state S3
  [  783.418015] ACPI: EC: event blocked
  [  783.418016] ACPI: EC: EC stopped
  [  783.418018] PM: Saving platform NVS memory
  [  783.418027] Disabling non-boot CPUs ...
  [  783.434574] IRQ 65: no longer affine to CPU1
  [  783.435629] smpboot: CPU 1 is now offline
  [  783.454574] IRQ 66: no longer affine to CPU2
  [  783.456378] smpboot: CPU 2 is now offline
  [  783.478405] IRQ 21: no longer affine to CPU3
  [  783.478414] IRQ 43: no longer affine to CPU3
  [  783.478435] IRQ 71: no longer affine to CPU3
  [  783.479449] smpboot: CPU 3 is now offline
  [  783.481656] ACPI: Low-level resume complete
  [  783.481733] ACPI: EC: EC started
  [  783.481734] PM: Restoring platform NVS memory
  [  783.482160] Enabling non-boot CPUs ...
  [  783.482240] x86: Booting SMP configuration:
  [  783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  783.558589]  cache: parent cpu1 should not be sleeping
  [  783.687159] CPU1 is up
  [  783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1
  [  783.687812]  cache: parent cpu2 should not be sleeping
  [  783.688001] CPU2 is up
  [  783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  783.783709]  cache: parent cpu3 should not be sleeping
  [  783.978233] CPU3 is up
  [  783.982020] ACPI: Waking up from system sleep state S3
  [  784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to 
reestablish PCI tunnels...
  [  784.112655] thunderbolt :07:00.0: control channel starting...
  [  784.112660] thunderbolt :07:00.0: starting TX ring 0
  [  784.112673] thunderbolt :07:00.0: enabling interrupt at register 
0x38200 bit 0 (0x0 -> 0x1)
  [  784.112677] thunderbolt :07:00.0: starting RX ring 0
  [  784.112689] thunderbolt :07:00.0: enabling interrupt at register 
0x38200 bit 12 (0x1 -> 0x1001)
  [  784.112696] thunderbolt :07:00.0: resuming...
  [  784.112699] thunderbolt :07:00.0: resetting switch at 0
  [  784.113249] thunderbolt :07:00.0: 0: resuming switch
  [  784.144609] thunderbolt :07:00.0: resume finished
  [  784.213878] thunderbolt :07:00.0: resetting error on 0:b.
  [  784.213897] thunderbolt 

[Kernel-packages] [Bug 1795256] Re: frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-28 Thread Aravind R
You can close this bug. It got fixed in last upgrade.

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

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
  00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

  
  aravind@comp:~$ sudo lshw
  [sudo] password for aravind: 
  comp
  description: Notebook
  product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
  vendor: Acer
  version: V1.25
  serial: NXGDWSI034717145457600
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
*-core
 description: Motherboard
 product: Ironman_SK
 vendor: Acer
 physical id: 0
 version: V1.25
 serial: NBGD411006717145457600
 slot: Type2 - Board Chassis Location
   *-firmware
description: BIOS
vendor: Insyde Corp.
physical id: 0
version: V1.25
date: 03/03/2017
size: 128KiB
capacity: 4544KiB
capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
   *-cpu
description: CPU
product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
flush_l1d cpufreq
configuration: cores=2 enabledcores=2 threads=4
  *-cache:0
   description: L1 cache
   physical id: 5
   

[Kernel-packages] [Bug 1795256] Re: frequent crash of Ubuntu 18.04 with purple dotted screen or black screen error death

2018-10-28 Thread Aravind R
Kernel 4.15.0.39.41 working fine. Last upgrade have broken xserver-
common. Reinstalling solves the issue.

As suggested in xdiagnose, I disabled vasedf for precaution.

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

Title:
  frequent crash of Ubuntu 18.04 with purple dotted screen or black
  screen error death

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had same problem in Ubuntu 16.04.3. But not frequent. It was
  happening when I play HD video. But now after installing Ubuntu 18.04
  the same problem even when browsing. Its too frequent.

  I have tried to reinstall Intel-microcode, bumblebee, xorg video
  drivers. No improvement.

  The system don't crash even show error message in dmesg and
  journalctl.

  aravind@comp:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
(rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.2 PCI bridge: Intel Corporation Device 9d1a (rev f1)
  00:1d.3 PCI bridge: Intel Corporation Device 9d1b (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation Device 179c (rev ff)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

  
  aravind@comp:~$ sudo lshw
  [sudo] password for aravind: 
  comp
  description: Notebook
  product: Aspire E5-575G (Aspire E5-575G_115F_1.25)
  vendor: Acer
  version: V1.25
  serial: NXGDWSI034717145457600
  width: 64 bits
  capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
  configuration: chassis=notebook family=KBL sku=Aspire E5-575G_115F_1.25 
uuid=BB9943DA-A143-49C0-8D00-A81E84883CFD
*-core
 description: Motherboard
 product: Ironman_SK
 vendor: Acer
 physical id: 0
 version: V1.25
 serial: NBGD411006717145457600
 slot: Type2 - Board Chassis Location
   *-firmware
description: BIOS
vendor: Insyde Corp.
physical id: 0
version: V1.25
date: 03/03/2017
size: 128KiB
capacity: 4544KiB
capabilities: pci upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 
int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
   *-cpu
description: CPU
product: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 799MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae 
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb 
stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec 
xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp 
flush_l1d cpufreq
configuration: cores=2 

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-10-28 Thread chetan Mehra
Hi I am on Carbon X1 2015 and  I was using ubuntu mate 16.04. The system
suggested that I update to 18.04. I did that and went for run. I came
back my screen was still there but the menu was gone. I forced a
restart. I now get a screen for bios load then sda3_crypt. I put in my
password and I get a blank screen with a blinking cursor that I cannot
move and nothing else. I cannot recall what my kernel was. I just wanted
tot ask if there has been any resolution on this issue...today is
2018-10-28.

I just read Stefan's comment and my heart sank...Any
suggestionsanybody?

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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


[Kernel-packages] [Bug 1800348] [NEW] nvidia-kernel-source-390 (not installed): nvidia kernel module failed to build

2018-10-28 Thread Simon Giger
Public bug reported:

sudo apt upgrade

/etc/kernel/header_postinst.d/dkms:
Secure Boot not enabled on this system.
Error! Bad return status for module build on kernel: 4.15.0-38-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.77/build/make.log for more information. 
--> make.log attached.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-kernel-source-390 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
DKMSKernelVersion: 4.15.0-38-generic
Date: Sun Oct 28 14:04:31 2018
InstallationDate: Installed on 2018-06-30 (120 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageVersion: (not installed)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-390
Title: nvidia-kernel-source-390 (not installed): nvidia kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/1800348/+attachment/5206482/+files/make.log

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

Title:
  nvidia-kernel-source-390 (not installed): nvidia kernel module failed
  to build

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  sudo apt upgrade

  /etc/kernel/header_postinst.d/dkms:
  Secure Boot not enabled on this system.
  Error! Bad return status for module build on kernel: 4.15.0-38-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia/390.77/build/make.log for more information. 
  --> make.log attached.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-source-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-38-generic
  Date: Sun Oct 28 14:04:31 2018
  InstallationDate: Installed on 2018-06-30 (120 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: (not installed)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 (not installed): nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800348/+subscriptions

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


[Kernel-packages] [Bug 1048544] Re: [Lenovo ThinkPad L512 2597] Fan speed freezes, and hotkeys stop working

2018-10-28 Thread robinson1010
Thank you for sharing this information. To know more about Lenovo Thinkpad visit
https://www.lenovo.dotcomstores.in/product-category/lenovo/laptops/thinkpad/

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

Title:
  [Lenovo ThinkPad L512 2597] Fan speed freezes, and hotkeys stop
  working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lenovo L512 (2597AB2) ubuntu 12.10

  I've purchased LENOVO ThinkPad L512 (2597AB2) laptop, and experiencing
  some problems with it in Linux. Particularly, after some time (it may
  be 10 minutes, or may be day) buttons Fn + F1, Fn + F2, ..., Fn + F12,
  Insert, Delete, Home, Volume+, Volume-, Volume Mute and POWER are no
  longer works. In addition, the CPU fan is behaving strangely does not
  respond to the temperature increase. And it does so until one
  completely cuts laptop from the power (no AC, no battery), reboot or
  on/off cycle are unhelpful.

  yet the topic was discussed here 
https://bugzilla.kernel.org/show_bug.cgi?id=27792
  ---
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC29', 
'/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC2', 
'/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/pcmC2D1p', 
'/dev/snd/hwC2D0', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [   20.405882] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio4/serio5/input/input15
   [  671.313808] atkbd serio0: Unknown key pressed (translated set 2, code 
0xf1 on isa0060/serio0).
   [  671.313814] atkbd serio0: Use 'setkeycodes e071 ' to make it 
known.
   [  671.324486] atkbd serio0: Unknown key released (translated set 2, code 
0xf1 on isa0060/serio0).
   [  671.324491] atkbd serio0: Use 'setkeycodes e071 ' to make it 
known.
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=51302391-e13c-484e-9425-220a784fe233
  MachineType: LENOVO 2597AB2
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=b4b2927b-e7d2-4074-881b-c0887cdc5caa ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.95
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  quantal
  Uname: Linux 3.5.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  dmi.bios.date: 11/07/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET62WW (1.38 )
  dmi.board.name: 2597AB2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr81ET62WW(1.38):bd11/07/2012:svnLENOVO:pn2597AB2:pvrThinkPadL512:rvnLENOVO:rn2597AB2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2597AB2
  dmi.product.version: ThinkPad L512
  dmi.sys.vendor: LENOVO

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

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


Re: [Kernel-packages] [Bug 1799470] Re: slow boot in kubuntu 18.04

2018-10-28 Thread dwizz
Hi Joseph,
I will try to pass to the latest upstream kernel the next week-end.
best regtards

Le mardi 23 octobre 2018 à 20:40:56 UTC+2, Joseph Salisbury 
 a écrit :  
 
 Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19


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

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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1799470

Title:
  slow boot in kubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the bug with the Kubuntu 18.04 
  sb_release -rd:
  Description:    Ubuntu 18.04.1 LTS
  Release:        18.04

  Before, i was using the 16 (LTS) version and the boot was quick.
  I have first try un update and i have the problem,
  with a fresh install, i have also the same problem.

  In the boot, i have a long time (33s) without message and action

  In this extract of the dmesg, you can see the 33 seconds without  messages
  [    5.434266]  sdc: sdc1 sdc2
  [    5.434268] sd 11:0:0:0: [sdd] 537234768 512-byte logical blocks: (275 
GB/256 GiB)
  [    5.434288] sd 11:0:0:0: [sdd] Write Protect is off
  [    5.434290] sd 11:0:0:0: [sdd] Mode Sense: 00 3a 00 00
  [    5.434312] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [    5.434404] ata12.00: Enabling discard_zeroes_data
  [    5.434436] sd 5:0:0:0: [sdc] Attached SCSI disk
  [    5.435541]  sdd: sdd1 sdd2
  [    5.435661] ata12.00: Enabling discard_zeroes_data
  [    5.435893] sd 11:0:0:0: [sdd] supports TCG Opal
  [    5.435895] sd 11:0:0:0: [sdd] Attached SCSI disk
  [  38.317233] EXT4-fs (dm-0): mounted filesystem with ordered data mode. 
Opts: (null)
  [  38.439463] ip_tables: (C) 2000-2006 Netfilter Core Team
  [  38.548456] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid)
  [  38.568547] systemd[1]: Detected architecture x86-64.
  [  38.572697] systemd[1]: Set hostname to .
  [  38.649301] systemd[1]: Created slice User and Session Slice.
  [  38.649610] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
  [  38.649680] systemd[1]: Created slice System Slice.
  [  38.649716] systemd[1]: Listening on fsck to fsckd communication Socket.
  [  38.649740] systemd[1]: Listening on Device-mapper event daemon FIFOs.
  [  38.649760] systemd[1]: Listening on udev Kernel Socket.
  [  38.649768] systemd[1]: Reached target Slices.
  [  38.667706] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro

  
  With the command 
  sudo systemd-analyze time
  [sudo] Mot de passe de jacky : 
  Startup finished in 12.351s (firmware) + 11.414s (loader) + 38.418s (kernel) 
+ 1.902s (userspace) = 1min 4.086s
  graphical.target reached after 1.898s in userspace

  You can see the 38 seconds in the kernel mode

  In the blame, there is any long action
  sudo systemd-analyze blame                    
            352ms disk-tera.mount
            321ms NetworkManager.service
            273ms dev-mapper-kubuntu\x2d\x2dvg\x2droot.device
            264ms udisks2.service
            236ms networkd-dispatcher.service
            234ms snapd.service
            201ms systemd-logind.service
            196ms mpd.service
            192ms ModemManager.service
            170ms disk-sdb.mount
            157ms systemd-timesyncd.service
            132ms systemd-resolved.service
            130ms accounts-daemon.service
              84ms thermald.service
              79ms alsa-restore.service
              76ms pppd-dns.service
              74ms keyboard-setup.service
              74ms plymouth-quit.service
              71ms systemd-journal-flush.service
              68ms wpa_supplicant.service
              61ms lvm2-pvscan@8:50.service
              58ms gpu-manager.service
              57ms colord.service
              56ms systemd-udev-trigger.service
              53ms systemd-udevd.service
              52ms upower.service
              51ms packagekit.service
              49ms lvm2-monitor.service
              49ms apparmor.service
              46ms rsyslog.service
              44ms user@119.service
              42ms systemd-journald.service
              41ms grub-common.service
              39ms polkit.service
              27ms 

[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

2018-10-28 Thread GrzesiekC
Hello again all,

In my #10 comment, I forgot to mention that my system it is upgraded
from ubuntu 16.04.4.

As it is, on Thursday (25-10-2018), two major things happened:
1. The kernel was updated to - Linux E7470 4.15.0-39-generic #42-Ubuntu SMP Tue 
Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

2. I "rewound" my bash history file. I was looking for any workarounds,
I performed during the lifespan of my 16.04.x. I found a line where I
was messing with my Intel driver. To be honest, ATM I'm not sure why,
but I added this file to resolve some other forgotten issue.

/usr/share/X11/xorg.conf.d/20-intel.conf

and here is the content:

Section "Device"
Driver "Intel"
Identifier "Intel"
EndSection

I deleted the file.

Why I bother you with this long post - since Thursday , I haven't had any 
single lock-up. 
So, it looks like, one of those two helped in my case. 
Finger cross it will stay this why for a bit longer.

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  

[Kernel-packages] [Bug 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-10-28 Thread Felipe Ortega
This week I got updates for several packages apparently related with
sound management, as well as a new kernel. After update and reboot, the
headphones jack started to work again. Connection/disconnection was
correctly managed in PulseAudio, and audio quality was very good.

However, like in the previous cases, as soon as I plugged in both the
headphones jack and the mic jack I got a peak of noise in my headset,
and everything stopped working again. Even connecting the headphones
only

Thus, maybe the key is some problem with *both the mic and headphones
jacks* connected at the same time.

Finally, my laptop support service provided this fix for turning off the
S/PDIF red light in the headphones connection:

mkdir -p ~/.config/autostart
tee -a ~/.config/autostart/disable_optical_led.desktop
Then, reboot.

Nevertheless, I have not tested this yet, just in case that for some
reason it may disconnect the complete headphones jack, preventing me to
test any solution for this problem.

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lehel  1673 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0
  InstallationDate: Installed on 2017-04-30 (499 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! 
"acpi_osi=Windows 2009"
  ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-lowlatency N/A
   linux-backports-modules-4.15.0-34-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-34-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

2018-10-28 Thread Damian Campbell
On Dell Inspiron 1525 auto upgraded from xubuntu 16.04 LTS 64bit to
18.04 LTS. This bug appeared.

Then tried clean install of Xubuntu 18.04.1 The bug appeared from moment
of boot of cd. Bug present also in Ubuntu 18.04.1

Grub edit of Video=SVIDEO-1:d works.

As a committed Ubuntu fan of years going on decades, I cannot adequately
express my strong disapointment that a bug serious enough to prevent
effective installation for many users remains on a live LTS distro some
6 months after release even after revision to 18.04.1 I was able to fix
it, (sudo edit of grub) but most affected users would be unable to and
simply walk away. How many people walked and therefore never escalated
this bug because they never got far enough to be able to?? Come on
development team! Please remember that Ubuntu is supposed to be about
ease of use and the users!!! Should do better

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

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

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  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.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: 

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-10-28 Thread Bored Individual
Forgot the quotes around 'EOF', tested and it works for me.
Make sure you check if the service is enabled

Run the following commands:
---
cat<<'EOF'>bugfix-1759836.service
[Unit]
Description=Fix for 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836

[Service]
Type=oneshot
ExecStart=/bin/bash -c "services='systemd-udevd systemd-udevd-kernel.socket 
systemd-udevd-control.socket';systemctl stop $services;systemctl start 
$services"

[Install]
WantedBy=multi-user.target
EOF

sudo cp bugfix-1759836.service /etc/systemd/system
sudo systemctl enable bugfix-1759836.service

systemctl status bugfix-1759836.service
---
It should display something like:
  Loaded: loaded (/etc/systemd/system/bugfix-1759836.service; enabled; vendor 
preset: enabled)

After a reboot again run:
systemctl status bugfix-1759836.service

Hopefully they get this fixed soon.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash

2018-10-28 Thread Talat Batheesh
The patch fixes the issue and we tested it.

Thanks,
Talat

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

Title:
  [bionic]mlx5: reading SW stats through ifstat cause kernel crash

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

Bug description:
  Description of problem:
  Attempting to read SW stats (ifstat -x cpu_hit) on a system with probed VFs 
will crash the system.

  How reproducible:
  Always

  Steps to Reproduce:
  1. Create a VF
  echo 1 > /sys/bus/pci/devices/\:82\:00.0/sriov_numvfs

  2. read SW stats:
  ifstat -x cpu_hit

  
  Actual results:
  System will crash

  Expected results:
  No system crash

  Additional info:
  The reason for the crash is insufficient check on the helper that determines 
if a netdev is vf rep.

  will crash:
  $ ifstat -x cpu_hit 

  will not crash:
  $ ifstat -x cpu_hit $VF_REP 
  $ ifstat -x cpu_hit $UPLINK_REP

  We already have a fix for this issue, and it is accepted upstream.
  https://patchwork.ozlabs.org/patch/935193/

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

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


[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

2018-10-28 Thread Cam Cope
Also, I have to fully power off the laptop before booting again or else
the devices won't come back (rebooting alone doesn't work).

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 
12133 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: 

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

2018-10-28 Thread Cam Cope
Attached more logs here. File contains dmesg for wifi crash, PCI device
list and USB device list. Search for === to find section separators.

** Attachment added: "dmesg, lspci, lsusb"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+attachment/5206472/+files/combined.txt

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 
12133 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice 

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

2018-10-28 Thread Cam Cope
I am also experiencing that both bluetooth and wifi are missing after
setting mem_sleep to deep. My laptop also refuses to actually stay
asleep in s2idle, I can see the screen come back on after I close the
lid.

Ubuntu 18.04
Kernel 4.15.0-36-generic
XPS 9370

** Attachment added: "Firmware versions"
   
https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+attachment/5206471/+files/fw.txt

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross 

[Kernel-packages] [Bug 1291969] Re: No usb on resume from suspend

2018-10-28 Thread adihezral
Hi, i'm not sure if this is same bug or not but symptom is similar. I managed 
to get it working but wasn't sure which actually made it worked but now it 
stopped working again. 
I have a Dell Latitude E7250 and i boot into the 18.04 based elementaryOS from 
usb, so after resume the filesystem becomes read-only and i can't save the 
dmesg output. 

What i've done
1. Added #32 workaround
2. Added udev rules to set power/control for my usb device to auto. 
3. Enabled USB Powershare in the bios (not sure this was the one but the issue 
was gone after i set this after the above 2, 2 days later issue came back)
4. Set usbcore.autosuspend=-1 in grub
5. Upgrade to 4.19LTS

Symptom:
1. On AC: suspend/resume works perfectly
2. On Battery: if resume from suspend while AC succeded, the second resume 
while on Battery works but the subsequent suspend/resume fails in system 
read-only again. 
3. On Battery: suspend/resume does not work resulting in system read-only. 

I've been trying to reproduce my earlier success but to no avail. 
Even a fresh install, the system will become read-only
Right now, suspend/resume only works on AC which leads me to suspect the USB 
hub/device is making this fail.

p/s sorry if i'm not following the right bug reporting etiquettes. i've
done a lot of searching and tried multiple solutions but still can't fix
this. Any help would be greatly appreciated and i will provide any help
i can.

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

Title:
  No usb on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My XPS13 running 14.04 sometimes loses its USB ports after resume from
  suspend. When this happens the entire bus seems dead - both external
  ports do not work, and internal USB devices (webcam, touchscreen) are
  also non-functional. Furthermore lsusb shows no devices attached.
  Rebooting or performing another suspend/resume cycle will clear the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  2868 F pulseaudio
   /dev/snd/controlC0:  steve  2868 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 13 08:36:46 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f
  InstallationDate: Installed on 2013-12-02 (100 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (28 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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