date:20181016

Still seeing this on 4.4.0-138.164~14.04.1 Trusty, P8 does not affected
as this is not supported:

AMD64:
 tag=execveat03 stime=1538879774
 cmdline="execveat03"
 contacts=""
 analysis=exit
 <<>>
 tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
 execveat03.c:74: FAIL: execveat() returned unexpected errno: EINVAL

P8:
 tag=execveat03 stime=1539075477
 cmdline="execveat03"
 contacts=""
 analysis=exit
 <<>>
 tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
 ../../../../include/lapi/execveat.h:37: CONF: syscall(-1) __NR_execveat not 
supported

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

Title:
  execveat03 in ubuntu_ltp_syscalls failed on X/B

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New

Bug description:
  This is a POTENTIAL REGRESSION.

  PASSED with 4.4.0-1063-aws
  FAILED with 4.4.0-1064-aws in proposed

  This is a new test case added 4 days ago.
  From the commit message it looks like this is a test case for commit 
8db6c34f1dbc:
  The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
  file capabilities"). Overlayfs and possibly other networking filesystems
  unhash the dentry on unlink, fail on this test with above change.

  However this commit has been applied in the Xenial AWS kernel
  (14985d791) with bug 1778286

  This might have something to do with the way how we backport it (the
  EINVAL return value is the clue)

  
  <<>>
  tag=execveat03 stime=1534135632
  cmdline="execveat03"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
  execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
  ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
  Uname: Linux 4.4.0-1064-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Aug 13 04:51:09 2018
  Ec2AMI: ami-529fb82a
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: x1e.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786729/+subscriptions

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

[Kernel-packages] [Bug 1798251] Re: Cannot boot from USB pen drive

2018-10-16 Thread John Bester

I just tried booting the USB drive of ubuntu-18.04-desktop-amd64.iso on
a different workstation. The drive was picked up for the boot menu and
the grub boot menu was displayed. I selected "Try Ubuntu without
installing" and it seemed to start booting (flash screen appeared). Then
after a while it dropped down to BusyBox. The message it gave might be
of some help: "(initramfs) Unable to find medium containing a live file
system". I then switched off the PC and booted again. This time I
selected "Install Ubuntu" from the grub boot menu, but it dropped down
to BusyBox again with the same message. If there is any way I can get
more information from BusyBox, please let me know.

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

Title:
  Cannot boot from USB pen drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have not been able to successfully create a bootable USB flash drive
  for about two years using modern desktop versions of Ubuntu. This
  weekend I tried again by booting from an Ubuntu Desktop 18.04 amd64
  workstation and using ubuntu-18.04-desktop-amd64.iso. The qemu test
  run seemed to boot, but after a while the boot splash screen just
  remained open. The PC I intended to do a clean install on simply
  dropped down to BusyBox. I tried various BIOS settings such as booting
  from UEFI, booting from legacy etc with no success. In the past I got
  different results on different workstations, but never got a USB stick
  booting (I forgot which version of Ubuntu this started becoming an
  issue, because I have created USB boot disks for older versions of
  Ubuntu many times). I have tried UNetbootin, MultiWriter, usb-creator-
  gtk and even tried Rufus on a Windows VM on KVM. None of the options
  worked (actually, UNetbootin did not even start up correctly). Up to
  now the workstations I built up had DVD drives, so I simply made a
  bootable CD - which has never let me down. However this last
  workstation did not have a DVD drive so in the end I booted Ubuntu
  16.04 which it had installed on a different drive and used grml-
  rescueboot to boot the ISO and perform the installation. If you google
  "Ubuntu does not boot from usb" you will find that it seems there this
  is an existing issue for many people. I would seriously consider
  having a standard USB image with grml preinstalled and allowing users
  to put whichever ISO they want to boot in a specific folder on the USB
  drive. There are a number of web sites explaining how to create a USB
  drive which is bootable in both UEFI and Legacy modes, and since
  Windows 10 ships on a single USB pen drive it should be totally
  possible to have a solution for Linux as well.

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

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

[Kernel-packages] [Bug 1793451] Re: mlock203 test in ubuntu_ltp_syscalls failed with X-AWS

Found on 4.4 Trusty as well.

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  mlock203 test in ubuntu_ltp_syscalls failed with X-AWS

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
  15:11:31 DEBUG| [stdout] <<>>
  15:11:31 DEBUG| [stdout] tag=mlock203 stime=1537369891
  15:11:31 DEBUG| [stdout] cmdline="mlock203"
  15:11:31 DEBUG| [stdout] contacts=""
  15:11:31 DEBUG| [stdout] analysis=exit
  15:11:31 DEBUG| [stdout] <<>>
  15:11:31 DEBUG| [stdout] tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s
  15:11:31 DEBUG| [stdout] mlock203.c:63: FAIL: Locking one memory again 
increased VmLck
  15:11:31 DEBUG| [stdout] 
  15:11:31 DEBUG| [stdout] Summary:
  15:11:31 DEBUG| [stdout] passed   0
  15:11:31 DEBUG| [stdout] failed   1
  15:11:31 DEBUG| [stdout] skipped  0
  15:11:31 DEBUG| [stdout] warnings 0
  15:11:31 DEBUG| [stdout] <<>>
  15:11:31 DEBUG| [stdout] initiation_status="ok"
  15:11:31 DEBUG| [stdout] duration=0 termination_type=exited termination_id=1 
corefile=no
  15:11:31 DEBUG| [stdout] cutime=0 cstime=0
  15:11:31 DEBUG| [stdout] <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78
  ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144
  Uname: Linux 4.4.0-1068-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Sep 20 06:44:13 2018
  Ec2AMI: ami-0e32ec5bc225539f5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: c3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1793451/+subscriptions

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

[Kernel-packages] [Bug 1798027] Re: openat03 in ubuntu_ltp_syscalls failed with T

Found on 4.4 Trusty as well.

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

Title:
  openat03 in ubuntu_ltp_syscalls failed with T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  <<>>
  incrementing stop
  openat030  TINFO  :  creating a file with O_TMPFILE flag
  openat030  TINFO  :  writing data to the file
  openat030  TINFO  :  file size is '4096'
  openat030  TINFO  :  looking for the file in '.'
  openat030  TINFO  :  file not found, OK
  openat030  TINFO  :  renaming '/tmp/ltp-iOozsTIX0F/ope3ZWDbU/#1179659 
(deleted)' -> 'tmpfile'
  openat030  TINFO  :  found a file: tmpfile
  openat031  TPASS  :  single file tests passed
  openat030  TINFO  :  create files in multiple directories
  openat030  TINFO  :  removing test directories
  openat030  TINFO  :  writing/reading temporary files
  openat030  TINFO  :  closing temporary files
  openat032  TPASS  :  multiple files tests passed
  openat030  TINFO  :  create multiple directories, link files into them
  openat030  TINFO  :  and check file permissions
  openat033  TFAIL  :  openat03.c:223: file mode read 0, but expected 
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
   crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 16 06:45:06 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798027/+subscriptions

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

[Kernel-packages] [Bug 1793451] Missing required logs.

2018-10-16 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1793451

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  mlock203 test in ubuntu_ltp_syscalls failed with X-AWS

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
  15:11:31 DEBUG| [stdout] <<>>
  15:11:31 DEBUG| [stdout] tag=mlock203 stime=1537369891
  15:11:31 DEBUG| [stdout] cmdline="mlock203"
  15:11:31 DEBUG| [stdout] contacts=""
  15:11:31 DEBUG| [stdout] analysis=exit
  15:11:31 DEBUG| [stdout] <<>>
  15:11:31 DEBUG| [stdout] tst_test.c:1063: INFO: Timeout per run is 0h 05m 00s
  15:11:31 DEBUG| [stdout] mlock203.c:63: FAIL: Locking one memory again 
increased VmLck
  15:11:31 DEBUG| [stdout] 
  15:11:31 DEBUG| [stdout] Summary:
  15:11:31 DEBUG| [stdout] passed   0
  15:11:31 DEBUG| [stdout] failed   1
  15:11:31 DEBUG| [stdout] skipped  0
  15:11:31 DEBUG| [stdout] warnings 0
  15:11:31 DEBUG| [stdout] <<>>
  15:11:31 DEBUG| [stdout] initiation_status="ok"
  15:11:31 DEBUG| [stdout] duration=0 termination_type=exited termination_id=1 
corefile=no
  15:11:31 DEBUG| [stdout] cutime=0 cstime=0
  15:11:31 DEBUG| [stdout] <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1068-aws 4.4.0-1068.78
  ProcVersionSignature: User Name 4.4.0-1068.78-aws 4.4.144
  Uname: Linux 4.4.0-1068-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Sep 20 06:44:13 2018
  Ec2AMI: ami-0e32ec5bc225539f5
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: c3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1793451/+subscriptions

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

[Kernel-packages] [Bug 1798251] Missing required logs.

2018-10-16 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1798251

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Cannot boot from USB pen drive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have not been able to successfully create a bootable USB flash drive
  for about two years using modern desktop versions of Ubuntu. This
  weekend I tried again by booting from an Ubuntu Desktop 18.04 amd64
  workstation and using ubuntu-18.04-desktop-amd64.iso. The qemu test
  run seemed to boot, but after a while the boot splash screen just
  remained open. The PC I intended to do a clean install on simply
  dropped down to BusyBox. I tried various BIOS settings such as booting
  from UEFI, booting from legacy etc with no success. In the past I got
  different results on different workstations, but never got a USB stick
  booting (I forgot which version of Ubuntu this started becoming an
  issue, because I have created USB boot disks for older versions of
  Ubuntu many times). I have tried UNetbootin, MultiWriter, usb-creator-
  gtk and even tried Rufus on a Windows VM on KVM. None of the options
  worked (actually, UNetbootin did not even start up correctly). Up to
  now the workstations I built up had DVD drives, so I simply made a
  bootable CD - which has never let me down. However this last
  workstation did not have a DVD drive so in the end I booted Ubuntu
  16.04 which it had installed on a different drive and used grml-
  rescueboot to boot the ISO and perform the installation. If you google
  "Ubuntu does not boot from usb" you will find that it seems there this
  is an existing issue for many people. I would seriously consider
  having a standard USB image with grml preinstalled and allowing users
  to put whichever ISO they want to boot in a specific folder on the USB
  drive. There are a number of web sites explaining how to create a USB
  drive which is bootable in both UEFI and Legacy modes, and since
  Windows 10 ships on a single USB pen drive it should be totally
  possible to have a solution for Linux as well.

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

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

[Kernel-packages] [Bug 1798251] [NEW] Cannot boot from USB pen drive

2018-10-16 Thread John Bester

Public bug reported:

I have not been able to successfully create a bootable USB flash drive
for about two years using modern desktop versions of Ubuntu. This
weekend I tried again by booting from an Ubuntu Desktop 18.04 amd64
workstation and using ubuntu-18.04-desktop-amd64.iso. The qemu test run
seemed to boot, but after a while the boot splash screen just remained
open. The PC I intended to do a clean install on simply dropped down to
BusyBox. I tried various BIOS settings such as booting from UEFI,
booting from legacy etc with no success. In the past I got different
results on different workstations, but never got a USB stick booting (I
forgot which version of Ubuntu this started becoming an issue, because I
have created USB boot disks for older versions of Ubuntu many times). I
have tried UNetbootin, MultiWriter, usb-creator-gtk and even tried Rufus
on a Windows VM on KVM. None of the options worked (actually, UNetbootin
did not even start up correctly). Up to now the workstations I built up
had DVD drives, so I simply made a bootable CD - which has never let me
down. However this last workstation did not have a DVD drive so in the
end I booted Ubuntu 16.04 which it had installed on a different drive
and used grml-rescueboot to boot the ISO and perform the installation.
If you google "Ubuntu does not boot from usb" you will find that it
seems there this is an existing issue for many people. I would seriously
consider having a standard USB image with grml preinstalled and allowing
users to put whichever ISO they want to boot in a specific folder on the
USB drive. There are a number of web sites explaining how to create a
USB drive which is bootable in both UEFI and Legacy modes, and since
Windows 10 ships on a single USB pen drive it should be totally possible
to have a solution for Linux as well.

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

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

Title:
  Cannot boot from USB pen drive

Status in linux package in Ubuntu:
  New

Bug description:
  I have not been able to successfully create a bootable USB flash drive
  for about two years using modern desktop versions of Ubuntu. This
  weekend I tried again by booting from an Ubuntu Desktop 18.04 amd64
  workstation and using ubuntu-18.04-desktop-amd64.iso. The qemu test
  run seemed to boot, but after a while the boot splash screen just
  remained open. The PC I intended to do a clean install on simply
  dropped down to BusyBox. I tried various BIOS settings such as booting
  from UEFI, booting from legacy etc with no success. In the past I got
  different results on different workstations, but never got a USB stick
  booting (I forgot which version of Ubuntu this started becoming an
  issue, because I have created USB boot disks for older versions of
  Ubuntu many times). I have tried UNetbootin, MultiWriter, usb-creator-
  gtk and even tried Rufus on a Windows VM on KVM. None of the options
  worked (actually, UNetbootin did not even start up correctly). Up to
  now the workstations I built up had DVD drives, so I simply made a
  bootable CD - which has never let me down. However this last
  workstation did not have a DVD drive so in the end I booted Ubuntu
  16.04 which it had installed on a different drive and used grml-
  rescueboot to boot the ISO and perform the installation. If you google
  "Ubuntu does not boot from usb" you will find that it seems there this
  is an existing issue for many people. I would seriously consider
  having a standard USB image with grml preinstalled and allowing users
  to put whichever ISO they want to boot in a specific folder on the USB
  drive. There are a number of web sites explaining how to create a USB
  drive which is bootable in both UEFI and Legacy modes, and since
  Windows 10 ships on a single USB pen drive it should be totally
  possible to have a solution for Linux as well.

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-10-16 Thread Kai-Heng Feng

Boris,

Does it work after S3?

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system

2018-10-16 Thread frank

Confirmed on Ubuntu cosmic catlefish (beta) Dell G3 3779

fanf@fanf-G3-3779:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 27c6:5301  
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 046d:c521 Logitech, Inc. Cordless Mouse Receiver
Bus 001 Device 006: ID 8087:0aaa Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
fanf@fanf-G3-3779:~$ uname -a
Linux fanf-G3-3779 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/1721909

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  kernel/system

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

Bug description:
  The Goodix GF3208 is not being recognised by the system (Dell Inspiron
  15 7577). What's worse is that it isn't even showing the manufacturer
  vendor id information when doing:

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5301
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Note that the vendor id 27c6 should at least say "Shenzhen Huiding
  Technology Co., Ltd." as per
  
https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings
  /vendor-prefixes.txt

  Will/has support been made for the Goodix GF3208 Fingerprint
  reader/scanner?

  Thanks in advance,
  Haz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  7 04:03:25 2017
  InstallationDate: Installed on 2017-10-01 (5 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Leonardo Müller

This kernel has the bug fixed. After one hour open, a game using DXVK
did not allocate any memory it couldn't free when closed. It would leak
around 600 MB in the same time previously.

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1798013] Re: xattr length returned by vfs_getxattr() is not correct in Trusty kernel

** Description changed:

+ == Justification ==
+ This issue has been addressed in other kernels in bug 1789746
+ 
+ When the getxattr05 test in ubuntu_ltp_syscalls test suite, the test
+ will failed with:
+ 
  tag=getxattr05 stime=1539663573
  cmdline="getxattr05"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  getxattr05.c:80: FAIL: Got different data(00 != ) at 16
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  
  Summary:
  passed   2
  failed   1
  skipped  0
  warnings 0
  
+ 
+ running in a container with a user namespace, if you call getxattr with name 
= "system.posix_acl_access" and size % 8 != 4, then getxattr silently skips the 
user namespace fixup that it normally does resulting in un-fixed-up data being 
returned.
+ 
+ This is caused by posix_acl_fix_xattr_to_user() being passed the total buffer 
size and not the actual size of the xattr as returned by vfs_getxattr().
+ 
+ This issue can be triggered by running the getxattr05 test in
+ ubuntu_ltp_syscalls test suite.
+ 
+ == Fix ==
+ 82c9a927bc5d ("getxattr: use correct xattr length")
+ 
+ A test kernel could be found here:
+ http://people.canonical.com/~phlin/kernel/lp-1798013-getxattr05/
+ 
+ == Regression Potential ==
+ Low, this fix just passes the actual length of the xattr as returned by 
vfs_getxattr() down.
+ 
+ 
+ == Test Case ==
+ Run the getxattr05 test in ubuntu_ltp_syscalls test suite.
+ 
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
-  crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
+  crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 16 04:19:43 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
-  
+ 
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-160-generic N/A
-  linux-backports-modules-3.13.0-160-generic  N/A
-  linux-firmware  1.127.24
+  linux-restricted-modules-3.13.0-160-generic N/A
+  linux-backports-modules-3.13.0-160-generic  N/A
+  linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

** Description changed:

  == Justification ==
- This issue has been addressed in other kernels in bug 1789746
+ This issue has been addressed in bug 1789746 for other kernels 
  
  When the getxattr05 test in ubuntu_ltp_syscalls test suite, the test
  will failed with:
  
  tag=getxattr05 stime=1539663573
  cmdline="getxattr05"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  getxattr05.c:80: FAIL: Got different data(00 != ) at 16
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  
  Summary:
  passed   2
  failed   1
  skipped  0
  warnings 0
  
+ running in a container with a user namespace, if you call getxattr with
+ name = "system.posix_acl_access" and size % 8 != 4, then getxattr
+ silently skips the user namespace fixup that it normally does resulting
+ in un-fixed-u

[Kernel-packages] [Bug 1787357] Re: Freeze

[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/1787357

Title:
  Freeze

Status in linux package in Ubuntu:
  Expired

Bug description:
  don't know what happen, but i have a lot of problem with power
  management. hibernate won't work. resume  from suspend broke wifi
  connection, and i lost wifi driver.

  Often i have a complete freeze on my desktop. can't move to other
  terminal (ALT-Fx didn't work).

  My laptop is new, i bought Dell new XPS 15.

  Some bugs seems to be known like :
  [0.064000] ACPI Exception: Could not find/resolve named package element: 
LNKA (20170831/dspkginit-381)
  [0.064000] ACPI Exception: Could not find/resolve named package element: 
LNKB (20170831/dspkginit-381)
  [0.064000] ACPI Exception: Could not find/resolve named package element: 
LNKC (20170831/dspkginit-381)
  [0.064000] ACPI Exception: Could not find/resolve named package element: 
LNKD (20170831/dspkginit-381)

  [0.247233] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [0.247244] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)

  
  [  531.106337] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun

  
  lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-30-generic 4.15.0-30.32
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  2863 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 10:38:26 2018
  HibernationDevice: RESUME=UUID=340c4c20-b850-4faa-96a5-5526916293a4
  InstallationDate: Installed on 2018-08-08 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=fd3c151c-941a-412d-b135-a641f4cea7d0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/12/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1625912] Re: Kernel option usbhid.mousepoll=1 is now ignored

Now tracking upstream kernel bug:

  https://bugzilla.kernel.org/show_bug.cgi?id=82571

which sounds more appropriate.

** Bug watch added: Linux Kernel Bug Tracker #82571
   https://bugzilla.kernel.org/show_bug.cgi?id=82571

** Changed in: linux
   Importance: Medium => Unknown

** Changed in: linux
   Status: Confirmed => Unknown

** Changed in: linux
 Remote watch: Linux Kernel Bug Tracker #60586 => Linux Kernel Bug Tracker 
#82571

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

Title:
  Kernel option usbhid.mousepoll=1 is now ignored

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

Bug description:
  Kernel option usbhid.mousepoll=1 is now ignored.

  I can see in /proc/cmdline that I still have usbhid.mousepoll=1 but in
  real testing with Mir clients I'm only getting 125Hz input instead of
  the expected 1000Hz.

  Just a few months ago at least it was working (with the same mouse but
  different PC).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D2c', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 21 11:59:24 2016
  HibernationDevice: RESUME=UUID=14362a37-9d65-44cb-af81-5694ee7c17c1
  InstallationDate: Installed on 2016-07-11 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160710)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: LENOVO 30AJS05700
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=81044886-888d-4a06-893c-d740f91759e0 ro quiet splash 
usbhid.mousepoll=1 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.161
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on

OK. Please test Ubuntu version 18.04, or 18.10 (release tomorrow!).

In the meantime this bug will automatically close in 60 days if there
are no more comments.

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

Title:
  Interrupt audio on bluetooth headset when wifi is on

Status in bcmwl package in Ubuntu:
  Incomplete
Status in broadcom-sta package in Ubuntu:
  Incomplete

Bug description:
  When WiFi and Bluetooth is on, this have conflict!
  Sound on bluetooth headset is interrupted, ping is high.
  In syslog:
  Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream
  Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream
  Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream
  Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream
  Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream
  Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream
  Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology 
Corp. )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:55:20 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on

2018-10-16 Thread Saleh

The last I was using Ubuntu it was version 17.04! I had to switch back
to Windows because bluetooth is very important to me.

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

Title:
  Interrupt audio on bluetooth headset when wifi is on

Status in bcmwl package in Ubuntu:
  Incomplete
Status in broadcom-sta package in Ubuntu:
  Incomplete

Bug description:
  When WiFi and Bluetooth is on, this have conflict!
  Sound on bluetooth headset is interrupted, ping is high.
  In syslog:
  Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream
  Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream
  Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream
  Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream
  Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream
  Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream
  Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology 
Corp. )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:55:20 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1798013] Re: xattr length returned by vfs_getxattr() is not correct in Trusty kernel

** Summary changed:

- getxattr05 in ubuntu_ltp_syscalls failed with T
+ xattr length returned by vfs_getxattr() is not correct in Trusty kernel

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

Title:
  xattr length returned by vfs_getxattr() is not correct in Trusty
  kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  tag=getxattr05 stime=1539663573
  cmdline="getxattr05"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice
  getxattr05.c:80: FAIL: Got different data(00 != ) at 16
  getxattr05.c:85: PASS: Got same data when acquiring the value of 
system.posix_acl_access twice

  Summary:
  passed   2
  failed   1
  skipped  0
  warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
   crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 16 04:19:43 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798013/+subscriptions

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

[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on

** Project changed: broadcom-sta => ubuntu

** No longer affects: ubuntu

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

Title:
  Interrupt audio on bluetooth headset when wifi is on

Status in bcmwl package in Ubuntu:
  Incomplete
Status in broadcom-sta package in Ubuntu:
  Incomplete

Bug description:
  When WiFi and Bluetooth is on, this have conflict!
  Sound on bluetooth headset is interrupted, ping is high.
  In syslog:
  Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream
  Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream
  Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream
  Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream
  Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream
  Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream
  Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology 
Corp. )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:55:20 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  Interrupt audio on bluetooth headset when wifi is on

Status in bcmwl package in Ubuntu:
  Incomplete
Status in broadcom-sta package in Ubuntu:
  Incomplete

Bug description:
  When WiFi and Bluetooth is on, this have conflict!
  Sound on bluetooth headset is interrupted, ping is high.
  In syslog:
  Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream
  Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream
  Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream
  Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream
  Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream
  Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream
  Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology 
Corp. )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:55:20 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on

The "main" Bluetooth skipping problem was fixed a few months ago in Ubuntu 
18.04 here:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.1

That fixed the main bug in PulseAudio but there may remain some driver-
specific bugs in the kernel like this one...

Are you using 18.04 or later?


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

** Changed in: broadcom-sta (Ubuntu)
   Status: New => Incomplete

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

Title:
  Interrupt audio on bluetooth headset when wifi is on

Status in bcmwl package in Ubuntu:
  Incomplete
Status in broadcom-sta package in Ubuntu:
  Incomplete

Bug description:
  When WiFi and Bluetooth is on, this have conflict!
  Sound on bluetooth headset is interrupted, ping is high.
  In syslog:
  Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream
  Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream
  Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream
  Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream
  Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream
  Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream
  Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology 
Corp. )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:55:20 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on

2018-10-16 Thread Saleh

Still no solution for this problem?!

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

Title:
  Interrupt audio on bluetooth headset when wifi is on

Status in Broadcom 802.11 Linux STA driver:
  New
Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  New

Bug description:
  When WiFi and Bluetooth is on, this have conflict!
  Sound on bluetooth headset is interrupted, ping is high.
  In syslog:
  Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream
  Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream
  Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream
  Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream
  Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream
  Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] 
module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream
  Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology 
Corp. )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:55:20 2015
  InstallationDate: Installed on 2015-11-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/broadcom-sta/+bug/1518408/+subscriptions

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

[Kernel-packages] [Bug 1767706] Re: Ubuntu 18.04 no guest session available in gdm

2018-10-16 Thread Robert Ancell

** Changed in: gdm3 (Ubuntu)
 Assignee: Robert Ancell (robert-ancell) => (unassigned)

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

Title:
  Ubuntu 18.04 no guest session available in gdm

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04 no option to switch to a guest session.
  Regression against 16.04 LTS.
  Usecase: let someone try Ubuntu, when giving a presentation

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

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

[Kernel-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

** Tags added: bionic nvidia

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

Bug description:
  Lenovo ideapad 510-15IKB
  OS: Ubuntu 18.04 bionic
  Kernel: x86_64 Linux 4.15.0-20-generic
  DE: GNOME
  CPU: Intel Core i5-7200U @ 4x 3.1GHz
  GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
  UEFI boot, Secure Boot disabled.

  I installed the proprietary graphics driver with Software Properties and 
Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, 
Dolphin) were working fine.
  To get rid of tearing I added nvidia-drm.modeset=1 to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && 
update-initramfs -u and rebooted.
  After doing that, Vulkan applications stopped working because they couldn't 
initialize the Vulkan swap chain until I reverted the changes to GRUB.

  Everything works as expected if lightdm is used instead of gdm3.

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

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

[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

This bug was fixed in the package gdm3 - 3.30.1-1ubuntu5

---
gdm3 (3.30.1-1ubuntu5) cosmic; urgency=medium

  * Remove accidental addition of Install/Alias info in gdm service
file.

 -- Adam Conrad   Tue, 16 Oct 2018 14:06:38 -0600

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

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Fix Released
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Fix Released
Status in gdm3 source package in Cosmic:
  Fix Released
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed
Status in xserver-xorg-video-fbdev source package in Cosmic:
  Fix Released

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty.
  Switching to another tty then back also starts gdm.

  It happens on bare metal and VM.

  Originally, when this issue happened there was a plymouth crash
  reported in bug 1794292 but this issue is still happening without the
  plymouth crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2018-10-16 Thread royden

"I built the next test kernel, up to the following commit:
6a9a27d5397fc6c52f90c09ddab91e65053584aa

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997";

>From #55, this kernel has poor wifi reception, both ant_sel=1 and 2.

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

... it's interesting that [practically?] the same kernel version that
fails consistently with Bionic works just fine with Xenial.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

I just tried Xenial with the HWE kernel - same result (success). FYI.

https://paste.ubuntu.com/p/WpqHnzbsS7/

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

Good idea @rharper. It's easy for MAAS to attempt commissioning on
Xenial or Bionic, so I gave Xenial a try. It works fine![1]

[1]: Console log -
https://paste.ubuntu.com/p/58hfBX6BhY/

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

2018-10-16 Thread Mariusz Domański

I can confirm this is still an issue.

My setup is:
Ubuntu 18.04
MSI GE60
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Intel HD 4600 + GeForce GTX 760M
nvidia-driver-396 (396.54-0ubuntu0~gpu18.04.1 from grphics-drivers PPA)
nvidia-prime for switching cards

With nvidia-drm.modeset=1 until some vulkan app is run as root the
vulkaninfo crashes like this:

==
VULKANINFO
==

Vulkan Instance Version: 1.1.82

ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
INTEL-MESA: warning: Haswell Vulkan support is incomplete
INTEL-MESA: warning: ../../../src/intel/vulkan/anv_device.c:1150: FINISHME: 
Implement pop-free point clipping



Instance Extensions:

Instance Extensions count = 17
VK_EXT_acquire_xlib_display : extension revision  1
VK_EXT_debug_report : extension revision  9
VK_EXT_debug_utils  : extension revision  1
VK_EXT_direct_mode_display  : extension revision  1
VK_EXT_display_surface_counter  : extension revision  1
VK_KHR_device_group_creation: extension revision  1
VK_KHR_display  : extension revision 23
VK_KHR_external_fence_capabilities  : extension revision  1
VK_KHR_external_memory_capabilities : extension revision  1
VK_KHR_external_semaphore_capabilities: extension revision  1
VK_KHR_get_display_properties2  : extension revision  1
VK_KHR_get_physical_device_properties2: extension revision  1
VK_KHR_get_surface_capabilities2: extension revision  1
VK_KHR_surface  : extension revision 25
VK_KHR_wayland_surface  : extension revision  6
VK_KHR_xcb_surface  : extension revision  6
VK_KHR_xlib_surface : extension revision  6
Layers: count = 3
===
VK_LAYER_LUNARG_standard_validation (LunarG Standard Validation Layer) Vulkan 
version 1.0.82, layer version 1
Layer Extensionscount = 0
Devices count = 2
GPU id   : 0 (Intel(R) Haswell Mobile)
Layer-Device Extensions count = 0
GPU id   : 1 (GeForce GTX 760M)
Layer-Device Extensions count = 0

VK_LAYER_VALVE_steam_overlay_32 (Steam Overlay Layer) Vulkan version 1.1.73, 
layer version 1
Layer Extensionscount = 0
Devices count = 2
GPU id   : 0 (Intel(R) Haswell Mobile)
Layer-Device Extensions count = 0
GPU id   : 1 (GeForce GTX 760M)
Layer-Device Extensions count = 0

VK_LAYER_VALVE_steam_overlay_64 (Steam Overlay Layer) Vulkan version 1.1.73, 
layer version 1
Layer Extensionscount = 0
Devices count = 2
GPU id   : 0 (Intel(R) Haswell Mobile)
Layer-Device Extensions count = 0
GPU id   : 1 (GeForce GTX 760M)
Layer-Device Extensions count = 0

Presentable Surfaces:
=
GPU id   : 0 (Intel(R) Haswell Mobile)
Surface type : VK_KHR_xcb_surface
Formats:count = 2
B8G8R8A8_SRGB
B8G8R8A8_UNORM
Present Modes:  count = 3
IMMEDIATE_KHR
MAILBOX_KHR
FIFO_KHR

VkSurfaceCapabilitiesKHR:
=
minImageCount   = 2
maxImageCount   = 0
currentExtent:
width   = 256
height  = 256
minImageExtent:
width   = 256
height  = 256
maxImageExtent:
width   = 256
height  = 256
maxImageArrayLayers = 1
supportedTransform:
VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR
currentTransform:
VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR
supportedCompositeAlpha:
VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR
VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR
supportedUsageFlags:
VK_IMAGE_USAGE_TRANSFER_SRC_BIT
VK_IMAGE_USAGE_TRANSFER_DST_BIT
VK_IMAGE_USAGE_SAMPLED_BIT
VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT

VkSurfaceCapabilities2EXT:
==
supportedSurfaceCounters:
None
GPU id   : 1 (GeForce GTX 760M)
Surface type : VK_KHR_xcb_surface
vulkaninfo: 
/build/vulkan-tools-WIuZIg/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253:
 AppDumpSurfaceFormats: Assertion `!err' failed.
Aborted (core dumped)


I have added some logs to vulkaninfo to check what is the value of 
vkGetPhysicalDeviceSurfaceFormatsKHR function that leads to abort and it is: -3
 (VK_ERROR_INITIALIZATION_FAILED)
Ac

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-10-16 Thread Ryan Harper

Does this fail with other releases? like trusty?  I was wondering if
initrd size plays a factor here:

precise/hwe-t: 25M
trusty/hwe-x:  35M
xenial/ga: 39M
xenial/hwe:53M
xenial/edge:   53M
bionic/ga: 55M
cosmic/ga: 57M

That might be faster for you to test than for us to replicate setup.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

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

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1798208] Missing required logs.

2018-10-16 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1798208

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  smartpqi updates for ubuntu 18.04.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
  pulling the following patches from upstream kernel version 4.19-rc7.

  Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date 
with kernel.org and to 
  correct issues seen particularly on ARM systems.

  These patches cherry-pick cleanly from:
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  0001-scsi-smartpqi-add-in-new-supported-controllers.patch
   commit b0f9408b14838566b2a9b26434fab667c2afb0ea
   No functionality change.
   Add in more supported controllers.
  0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
   commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
   Correct PQI operational queue deletion.
   Operational queues are deleted during resets.
  0003-scsi-smartpqi-update-driver-version.patch
   commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
   No functionality change.
   Need context for the next version change patch below.
  0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
   commit 957c5ab108c7d98369b7524daea532c0ebbcf845
   Correct driver active thread count when submitting internal commands.
  0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
   commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
   Retry INQUIRY operations.
  0006-scsi-smartpqi-add-inspur-advantech-ids.patch
   commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
   No functionality change.
   Add in more supported controllers.
  0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
   commit dac12fbc7b0a433a160b89212a56e155c94f3a80
   Critical bug fix for ARM.
   ARM does not handle volatile variables.
  0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
   commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
   No functionality change.

  There are some other patches but they are kernel-wide patches that affect 
other modules:
  blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch
   commit f23f5bece686a76598335141a091934f7eb0998c
   This is a kernel-wide patch that affects multiple modules:
 block/blk-mq-pci.c
 drivers/nvme/host/pci.c
 drivers/scsi/qla2xxx/qla_os.c
 drivers/scsi/smartpqi/smartpqi_init.c
 include/linux/blk-mq-pci.h

  commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb
  Author: Kees Cook 
  Date:   Tue Jun 12 14:03:40 2018 -0700

  treewide: kzalloc() -> kcalloc()

  
  commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57
  Author: Kees Cook 
  Date:   Tue Jun 12 13:55:00 2018 -0700

  treewide: kmalloc() -> kmalloc_array()

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

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

[Kernel-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gdm3 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

Bug description:
  Lenovo ideapad 510-15IKB
  OS: Ubuntu 18.04 bionic
  Kernel: x86_64 Linux 4.15.0-20-generic
  DE: GNOME
  CPU: Intel Core i5-7200U @ 4x 3.1GHz
  GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
  UEFI boot, Secure Boot disabled.

  I installed the proprietary graphics driver with Software Properties and 
Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, 
Dolphin) were working fine.
  To get rid of tearing I added nvidia-drm.modeset=1 to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && 
update-initramfs -u and rebooted.
  After doing that, Vulkan applications stopped working because they couldn't 
initialize the Vulkan swap chain until I reverted the changes to GRUB.

  Everything works as expected if lightdm is used instead of gdm3.

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

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

[Kernel-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

Bug description:
  Lenovo ideapad 510-15IKB
  OS: Ubuntu 18.04 bionic
  Kernel: x86_64 Linux 4.15.0-20-generic
  DE: GNOME
  CPU: Intel Core i5-7200U @ 4x 3.1GHz
  GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
  UEFI boot, Secure Boot disabled.

  I installed the proprietary graphics driver with Software Properties and 
Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, 
Dolphin) were working fine.
  To get rid of tearing I added nvidia-drm.modeset=1 to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && 
update-initramfs -u and rebooted.
  After doing that, Vulkan applications stopped working because they couldn't 
initialize the Vulkan swap chain until I reverted the changes to GRUB.

  Everything works as expected if lightdm is used instead of gdm3.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

I agree that this doesn't look like a QEMU issue, and I agree that it
doesn't look like a [general] networking hiccup.

@paelzer, the easiest way to get the exact configs you need would be to
install MAAS similar to how I've described on our discourse forum[1].
The PXE config will be /similar/ to this[2] (copied/pasted from
/usr/lib/maas/maas-test-enlistment on my MAAS server).

[1]: MAAS setup instructions
https://discourse.maas.io/t/setting-up-a-flexible-virtual-maas-test-environment/142

[2]: PXE config
https://paste.ubuntu.com/p/KBsCHCfKBD/

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1798208] [NEW] smartpqi updates for ubuntu 18.04.2

2018-10-16 Thread Don Brace

Public bug reported:

This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
pulling the following patches from upstream kernel version 4.19-rc7.

Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date 
with kernel.org and to 
correct issues seen particularly on ARM systems.

These patches cherry-pick cleanly from:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

0001-scsi-smartpqi-add-in-new-supported-controllers.patch
 commit b0f9408b14838566b2a9b26434fab667c2afb0ea
 No functionality change.
 Add in more supported controllers.
0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
 commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
 Correct PQI operational queue deletion.
 Operational queues are deleted during resets.
0003-scsi-smartpqi-update-driver-version.patch
 commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
 No functionality change.
 Need context for the next version change patch below.
0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
 commit 957c5ab108c7d98369b7524daea532c0ebbcf845
 Correct driver active thread count when submitting internal commands.
0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
 commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
 Retry INQUIRY operations.
0006-scsi-smartpqi-add-inspur-advantech-ids.patch
 commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
 No functionality change.
 Add in more supported controllers.
0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
 commit dac12fbc7b0a433a160b89212a56e155c94f3a80
 Critical bug fix for ARM.
 ARM does not handle volatile variables.
0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
 commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
 No functionality change.

There are some other patches but they are kernel-wide patches that affect other 
modules:
blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch
 commit f23f5bece686a76598335141a091934f7eb0998c
 This is a kernel-wide patch that affects multiple modules:
   block/blk-mq-pci.c
   drivers/nvme/host/pci.c
   drivers/scsi/qla2xxx/qla_os.c
   drivers/scsi/smartpqi/smartpqi_init.c
   include/linux/blk-mq-pci.h

commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb
Author: Kees Cook 
Date:   Tue Jun 12 14:03:40 2018 -0700

treewide: kzalloc() -> kcalloc()


commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57
Author: Kees Cook 
Date:   Tue Jun 12 13:55:00 2018 -0700

treewide: kmalloc() -> kmalloc_array()

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

** Attachment added: "Patches for Ubuntu 18.04.2"
   
https://bugs.launchpad.net/bugs/1798208/+attachment/5201901/+files/ubuntu_180402.tar

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

Title:
  smartpqi updates for ubuntu 18.04.2

Status in linux package in Ubuntu:
  New

Bug description:
  This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
  pulling the following patches from upstream kernel version 4.19-rc7.

  Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date 
with kernel.org and to 
  correct issues seen particularly on ARM systems.

  These patches cherry-pick cleanly from:
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  0001-scsi-smartpqi-add-in-new-supported-controllers.patch
   commit b0f9408b14838566b2a9b26434fab667c2afb0ea
   No functionality change.
   Add in more supported controllers.
  0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
   commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
   Correct PQI operational queue deletion.
   Operational queues are deleted during resets.
  0003-scsi-smartpqi-update-driver-version.patch
   commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
   No functionality change.
   Need context for the next version change patch below.
  0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
   commit 957c5ab108c7d98369b7524daea532c0ebbcf845
   Correct driver active thread count when submitting internal commands.
  0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
   commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
   Retry INQUIRY operations.
  0006-scsi-smartpqi-add-inspur-advantech-ids.patch
   commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
   No functionality change.
   Add in more supported controllers.
  0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
   commit dac12fbc7b0a433a160b89212a56e155c94f3a80
   Critical bug fix for ARM.
   ARM does not handle volatile variables.
  0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
   commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
   No functionality change.

  There are some

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

** No longer affects: gnome-settings-daemon

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

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

** Description changed:

  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.
  
  The bug manifests as a lack of progress in the boot process of the kdump
  kernel, and a storm of kernel messages like:
  
  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]
  
- The root cause of the the issue is that the kdump kernel kexec process
- does not ensure PCI devices are reset and/or MSI capabilities are
- disabled, so a PCI device could produce a huge amount of PCI irqs which
- would take all the processing time for the CPU (specially since we
- restrict the kdump kernel to use one single CPU only).
+ The root cause of the issue is that the kdump kernel kexec process does
+ not ensure PCI devices are reset and/or MSI capabilities are disabled,
+ so a PCI device could produce a huge amount of PCI irqs which would take
+ all the processing time for the CPU (specially since we restrict the
+ kdump kernel to use one single CPU only).
  
  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

https://marc.info/?l=linux-usb&m=153971734920554&w=2
--
Cristian Aravena Romero (caravena)

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

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

** Attachment added: "lspci tree output of a single root bridge PCI topology"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5201885/+files/lspci_single_root.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/1797990

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

** Attachment added: "lspci tree output of a multi root bridge PCI topology"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5201886/+files/lspci_multi_root.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/1797990

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1798185] Re: Enable CONFIG_INFINIBAND_USER_MAD

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect -p linux-azure 1798185

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

Title:
  Enable CONFIG_INFINIBAND_USER_MAD

Status in linux-azure package in Ubuntu:
  Incomplete

Bug description:
  Please enable CONFIG_INFINIBAND_USER_MAD in the linux-azure kernels.

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

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

One problem faced during this approach was that the early-quirks code in
x86 performs a recursive search in the PCI bus descending from the
"first" bus :00, and walking through all secondary busses by jumping
between bridges. For historical perspective about this code's evolution,
see [0].

This is not enough in multi-processor systems, which may have multiple PCIe 
root complexes, exposing many root ports and so describing multiple hierarchy 
domains. The PCIe spec even doesn't guarantee those hierarchies are capable of 
communicating; from PCIe spec 3.0, section 1.3.1: "[...] The capability to 
route peer-to-peer transactions between hierarchy domains through a Root
Complex is optional and implementation dependent. For example, an 
implementation may
incorporate a real or virtual Switch internally within the Root Complex to 
enable full peer-to-
peer support in a software transparent way."

Usually we don't see PCI devices unable to communicate to each other if
they are under different host bridges (aka root complexes in PCIe
terminology). But from a software perspective, what Linux sees are
multiple PCI devices organized in a tree way. The naive recursion from
check_dev_quirk() in arch/x86 can't reach all root complexes starting
always from bus :00.

To exemplify how this tree would look like with a single or with multi root 
bridges, we'll attach outputs of "lspci -t" for 2 system next.
That said, we needed to change the bus scanning process to be comprehensive and 
walk through all buses. Good references for multi-root-complex PCIe BIOS probe 
(like its numbering rationale), [1] and [2].


[0] The early PCI scan dates back to BitKeeper, added by Andi Kleen's "[PATCH] 
APIC fixes for x86-64", on October/2003. It initially restricted the search to 
the first 32 busses and slots. Due to a potential bug found in Nvidia chipsets, 
the scan was changed to run only in the first root bus: see commit 8659c406ade3 
("x86: only scan the root bus in early PCI quirks").
Finally, secondary busses reachable from the first bus were re-added back by: 
commit 850c321027c2 ("x86/quirks: Reintroduce scanning of secondary buses").

[1] https://codywu2010.wordpress.com/2015/11/29/how-modern-multi-
processor-multi-root-complex-system-assigns-pci-bus-number/

[2] PCI Firmware Specification and the ACPI spec.

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1798185] Re: Enable CONFIG_INFINIBAND_USER_MAD

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect -p linux 1798185

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

Title:
  Enable CONFIG_INFINIBAND_USER_MAD

Status in linux-azure package in Ubuntu:
  Incomplete

Bug description:
  Please enable CONFIG_INFINIBAND_USER_MAD in the linux-azure kernels.

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

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

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

I built the next test kernel, up to the following commit:
6a9a27d5397fc6c52f90c09ddab91e65053584aa

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

I built a test kernel with commit 337fe9f5c1e7d.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1798165

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

** Merge proposal linked:
   https://code.launchpad.net/~3v1n0/ubuntu/+source/gdm3/+git/gdm3/+merge/356861

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Incomplete
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-fbdev package in Ubuntu:
  Fix Released
Status in gdm3 source package in Cosmic:
  Incomplete
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed
Status in xserver-xorg-video-fbdev source package in Cosmic:
  Fix Released

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty.
  Switching to another tty then back also starts gdm.

  It happens on bare metal and VM.

  Originally, when this issue happened there was a plymouth crash
  reported in bug 1794292 but this issue is still happening without the
  plymouth crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

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

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

[Kernel-packages] [Bug 1798185] [NEW] Enable CONFIG_INFINIBAND_USER_MAD

2018-10-16 Thread Joshua R. Poulson

Public bug reported:

Please enable CONFIG_INFINIBAND_USER_MAD in the linux-azure kernels.

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Changed in: linux-azure (Ubuntu)
   Status: New => Confirmed

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

Title:
  Enable CONFIG_INFINIBAND_USER_MAD

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  Please enable CONFIG_INFINIBAND_USER_MAD in the linux-azure kernels.

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

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

During the investigation, we've noticed that PCI specification mentions
the need of MSI/MSI-X capability to be disabled during a system
boot/reset; from PCI Local Bus specification 3.0, sections 6.8.1.3 and
6.8.2.3: "[...] MSI Enable: This bit’s state after reset is 0 (MSI is
disabled)."

PCI layer in the Linux kernel ensures this bit is 0 during its
initialization [0], but for our case it is too late, give we had an IRQ
storm during early stages in the kdump kernel boot process.

The idea to resolve the issue was then to disable MSI/MSI-X early in boot, 
using the early-quirks infrastructure in arch/x86, which proved to be a 
successful approach.
Patches will be attached here soon.

[0]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/probe.c?h=v4.18#n1511

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

Earlier I used rechargeable batteries, I just recharged them when this
notification appeared.

Kernel upgraded, problem still persists.
4.19.0-041900rc8-generic


** Tags added: kernel-bug-exists-upstream

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

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

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798182] [NEW] Update ENA driver to version 2.0.1K

2018-10-16 Thread Kamal Mostafa

Public bug reported:

The following commits from mainline and linux-next:

Arthur Kiyanovski (16):
  net: ena: fix warning in rmmod caused by double iounmap
  net: ena: fix rare bug when failed restart/resume is followed by driver 
removal
  net: ena: fix NULL dereference due to untimely napi initialization
  net: ena: fix auto casting to boolean
  net: ena: minor performance improvement
  net: ena: complete host info to match latest ENA spec
  net: ena: introduce Low Latency Queues data structures according to ENA 
spec
  net: ena: add functions for handling Low Latency Queues in ena_com
  net: ena: add functions for handling Low Latency Queues in ena_netdev
  net: ena: use CSUM_CHECKED device indication to report skb's checksum 
status
  net: ena: explicit casting and initialization, and clearer error handling
  net: ena: limit refill Rx threshold to 256 to avoid latency issues
  net: ena: change rx copybreak default to reduce kernel memory pressure
  net: ena: remove redundant parameter in ena_com_admin_init()
  net: ena: update driver version to 2.0.1
  net: ena: fix indentations in ena_defs for better readability

Eric Dumazet (1):
  net: ena: remove ndo_poll_controller

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

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

Title:
  Update ENA driver to version 2.0.1K

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  The following commits from mainline and linux-next:

  Arthur Kiyanovski (16):
net: ena: fix warning in rmmod caused by double iounmap
net: ena: fix rare bug when failed restart/resume is followed by driver 
removal
net: ena: fix NULL dereference due to untimely napi initialization
net: ena: fix auto casting to boolean
net: ena: minor performance improvement
net: ena: complete host info to match latest ENA spec
net: ena: introduce Low Latency Queues data structures according to ENA 
spec
net: ena: add functions for handling Low Latency Queues in ena_com
net: ena: add functions for handling Low Latency Queues in ena_netdev
net: ena: use CSUM_CHECKED device indication to report skb's checksum 
status
net: ena: explicit casting and initialization, and clearer error 
handling
net: ena: limit refill Rx threshold to 256 to avoid latency issues
net: ena: change rx copybreak default to reduce kernel memory pressure
net: ena: remove redundant parameter in ena_com_admin_init()
net: ena: update driver version to 2.0.1
net: ena: fix indentations in ena_defs for better readability

  Eric Dumazet (1):
net: ena: remove ndo_poll_controller

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

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

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

https://bugzilla.kernel.org/show_bug.cgi?id=201445
--
Cristian Aravena Romero (caravena)

** Bug watch added: Linux Kernel Bug Tracker #201445
   https://bugzilla.kernel.org/show_bug.cgi?id=201445

** Also affects: gnome-settings-daemon via
   https://bugzilla.kernel.org/show_bug.cgi?id=201445
   Importance: Unknown
   Status: Unknown

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

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

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

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

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

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

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

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1796949] Re: [Bionic] CPPC bug fixes

2018-10-16 Thread Manoj Iyer

Built kernel with patches that fix CPPC issues, and re-run the test.

== Enable CPPC control in firmware ==

CAVM_CN99xx# env set cppccontrol 1

== Bionic kernel with patches ==

ubuntu@starbuck:~$ uname -a
Linux starbuck 4.15.0-38-generic #41~lp1796949+build.1 SMP Tue Oct 16 17:06:56 
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$ ls -lR /sys/devices/system/cpu/cpu1/acpi_cppc/
/sys/devices/system/cpu/cpu1/acpi_cppc/:
total 0
-r--r--r-- 1 root root 4096 Oct 16 18:45 feedback_ctrs
-r--r--r-- 1 root root 4096 Oct 16 18:45 highest_perf
-r--r--r-- 1 root root 4096 Oct 16 18:45 lowest_nonlinear_perf
-r--r--r-- 1 root root 4096 Oct 16 18:45 lowest_perf
-r--r--r-- 1 root root 4096 Oct 16 18:45 nominal_perf
-r--r--r-- 1 root root 4096 Oct 16 18:45 reference_perf
-r--r--r-- 1 root root 4096 Oct 16 18:45 wraparound_time
ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/highest_perf
250
ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/lowest_perf
100
ubuntu@starbuck:~$ cat /sys/devices/system/cpu/cpu1/acpi_cppc/feedback_ctrs 
ref:2240139584 del:2315092606
ubuntu@starbuck:~$

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

Title:
  [Bionic] CPPC bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  A number of CPPC related fixes from upstream needed for Cavium ThunderX2 
systems.

  [Fix]

  58e1c03536c9 ACPI / CPPC: Fix invalid PCC channel status errors
  b8b10bc2015c cpufreq: CPPC: Don't set transition_latency
  d29abc836843 ACPI / CPPC: Update all pr_(debug/err) messages to log the 
susbspace id

  [Test]
  A test kernel is available in ppa:yarmouth-team/cppc-tx2. This kernel was 
successfully tested on a CN99XX system.

  [Regression Potential]
  The cppcontrol feature needs to be explicitly enabled in firmware (default is 
disabled) for these patches to be in effect. Risk of regression is low.

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

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

[Kernel-packages] [Bug 1798070] Re: HP laptops - Battery capacity always reported as 100%

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

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

Title:
  HP laptops - Battery capacity always reported as 100%

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ###HP laptop models affected so far:
  HP EliteBook 840G1/G2
  HP EliteBook 850G1/G2
  HP ProBook 650G1
  HP EliteBook 8460p
  HP EliteBook 8470p
  HP 650 Notebook PC
  HP ZBook 15 G1/G2

  Battery capacity always reported as 100% by upower command in Ubuntu 16.04.5 
LTS - 4.15.0-36-generic (tested with older kernels as well).
  Upower info:
Installed: 0.99.4-2ubuntu0.3
Candidate: 0.99.4-2ubuntu0.3
Version table:
   *** 0.99.4-2ubuntu0.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.99.4-2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  HP Support Assistant utility detects the correct capacity in Windows.

  ###Information collected from one of the laptops:
  HP EliteBook 8460p - battery CC06XL - 4910mAh

  
  ### upower -d

  Device: /org/freedesktop/UPower/devices/line_power_AC
native-path: AC
power supply: yes
updated: Tue 02 Oct 2018 01:39:35 PM CEST (21 seconds ago)
has history: no
has statistics: no
line-power
  warning-level: none
  online: yes
  icon-name: 'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: Hewlett-Packard
model: Primary
serial: 00824 2012/06/09
power supply: yes
updated: Tue 02 Oct 2018 01:39:39 PM CEST (17 seconds ago)
has history: yes
has statistics: yes
battery
  present: yes
  rechargeable: yes
  state: fully-charged
  warning-level: none
  energy: 48.9348 Wh
  energy-empty: 0 Wh
  energy-full: 49.2156 Wh
  energy-full-design: 49.2156 Wh
  energy-rate: 0 W
  voltage: 12.475 V
  percentage: 99%
  capacity: 100%
  technology: lithium-ion
  icon-name: 'battery-full-charged-symbolic'
History (charge):
  1538480376 99.000 fully-charged
  1538480375 0.000 unknown
History (rate):
  1538480375 0.000 unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated: Tue 02 Oct 2018 01:39:35 PM CEST (21 seconds ago)
has history: no
has statistics: no
battery
  present: yes
  state: fully-charged
  warning-level: none
  energy: 48.9348 Wh
  energy-full: 49.2156 Wh
  energy-rate: 0 W
  percentage: 99%
  icon-name: 'battery-full-charged-symbolic'

  Daemon:
daemon-version: 0.99.4
on-battery: no
lid-is-closed: no
lid-is-present: yes
critical-action: PowerOff

  
  ### acpi -V

  Battery 0: Unknown, 99%
  Battery 0: design capacity 4557 mAh, last full capacity 4557 mAh = 100%
  Adapter 0: on-line
  Thermal 0: ok, 0.0 degrees C
  Thermal 0: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 1: ok, 43.0 degrees C
  Thermal 1: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 1: trip point 1 switches to mode hot at temperature 99.0 degrees C
  Thermal 2: ok, 42.0 degrees C
  Thermal 2: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 3: ok, 29.0 degrees C
  Thermal 3: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 3: trip point 1 switches to mode passive at temperature 55.0 degrees C
  Thermal 4: ok, 45.0 degrees C
  Thermal 4: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Thermal 4: trip point 1 switches to mode passive at temperature 105.0 degrees 
C
  Thermal 5: ok, 41.0 degrees C
  Thermal 5: trip point 0 switches to mode critical at temperature 128.0 
degrees C
  Cooling 0: Processor 0 of 10
  Cooling 1: Processor 0 of 10
  Cooling 2: LCD 0 of 20
  Cooling 3: x86_pkg_temp no state information available
  Cooling 4: Processor 0 of 10
  Cooling 5: Processor 0 of 10
  Cooling 6: intel_powerclamp no state information available

  
  ### cat /sys/class/power_supply/BAT0/uevent

  POWER_SUPPLY_NAME=BAT0
  POWER_SUPPLY_STATUS=Unknown
  POWER_SUPPLY_PRESENT=1
  POWER_SUPPLY_TECHNOLOGY=Li-ion
  POWER_SUPPLY_CYCLE_COUNT=0
  POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
  POWER_SUPPLY_VOLTAGE_NOW=12475000
  POWER_SUPPLY_CURRENT_NOW=0
  POWER_SUPPLY_CHARGE_FULL_DESIGN=4557000
  POWER_SUPPLY_CHARGE_FULL=4557000
  POWER_SUPPLY_CHARGE_NOW=4531000
  POWER_SUPPLY_CAPACITY=99
  POWER_SUPPLY_CAPACITY_LEVEL=Normal
  POWER_SUPPLY_MODEL_NAME=Primary
  POWER_SUPPLY_MANUFACTURER=Hewlett-Packard
  POWE

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

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

** Also affects: linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
   Status: Confirmed

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

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

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

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

[Kernel-packages] [Bug 1798082] Re: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Title:
  package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to
  install/upgrade: installed linux-image-4.15.0-34-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have made:
  sudo apt-get install cheese

  
  than apt promted that there are packages that are no longer used, and should 
be removed

  so i have made

  sudo apt autoremove

  
  and than the window showed to me , i have accepted and it failed with a bug.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   n372155 F...m pulseaudio
   /dev/snd/controlC0:  n372155 F pulseaudio
  Date: Tue Oct 16 14:21:18 2018
  ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=846ef064-2ad8-4a28-bfaf-8fd0f4c89158
  InstallationDate: Installed on 2018-08-12 (64 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  MachineType: Dell Inc. Latitude 7280
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=76eb8d35-4d70-4ac9-a9ff-62488bed2637 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.
  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: grub-pc 2.02-2ubuntu8.6
  SourcePackage: linux
  Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to 
install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.name: 0KK5D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 13004837
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd07/12/2018:svnDellInc.:pnLatitude7280:pvr:rvnDellInc.:rn0KK5D1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7280
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1797975] Re: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting

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

** Tags added: kernel-da-key

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

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  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:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1798110] Re: xenial: virtio-scsi: CPU soft lockup due to loop in virtscsi_target_destroy()

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

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

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

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

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

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

Title:
  xenial: virtio-scsi: CPU soft lockup due to loop in
  virtscsi_target_destroy()

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

Bug description:
  [Impact]

   * Detaching virtio-scsi disk in Xenial guest can cause
     CPU soft lockup in guest (and take 100% CPU in host).

   * It may prevent further progress on other tasks that
     depend on resources locked earlier in the SCSI target
     removal stack, and/or impact other SCSI functionality.

   * The fix resolves a corner case in the requests counter
     in the virtio SCSI target, which impacts a downstream
     (SAUCE) patch in the virtio-scsi target removal handler
     that depends on the requests counter value to be zero.

  [Test Case]

   * See LP #1798110 (this bug)'s comment #3 (too long for
     this section -- synthetic case with GDB+QEMU) and
     comment #4 (organic test case in cloud instance).

  [Regression Potential]

   * It seem low -- this only affects the SCSI command requeue
     path with regards to the reference counter, which is only
     used with real chance of problems in our downstream patch
     (which is now passing this testcase).

   * The other less serious issue would be decrementing it to
     a negative / < 0 value, which is not possible with this
     driver logic (see commit message), because the reqs counter
     is always incremented before calling virtscsi_queuecommand(),
     where this decrement operation is inserted.

  [Original Description]

  A customer reported a CPU soft lockup on Trusty HWE kernel from Xenial
  when detaching a virtio-scsi drive, and provided a crashdump that shows
  2 things:

  1) The soft locked up CPU is waiting for another CPU to finish something,
  and that does not happen because the other CPU is infinitely looping in
  virtscsi_target_destroy().

  2) The loop happens because the 'tgt->reqs' counter is non-zero, and that
  probably happened due to a missing decrement in SCSI command requeue path,
  exercised when the virtio ring is full.

  The reported problem itself happens because of a downstream/SAUCE patch,
  coupled with the problem of the missing decrement for the reqs counter.

  Introducing a decrement in the SCSI command requeue path resolves the
  problem, verified synthetically with QEMU+GDB and with test-case/loop
  provided by the customer as problem reproducer.

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

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

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

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-rc8

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

Title:
“Mouse battery low” notification appears even when all notifications
disabled

Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Incomplete

Bug description:
I have a wireless mouse powered by non-rechargeable battery. The mouse
works absolutely fine even with low battery level. Problem is, Ubuntu
gives notifications about the battery level all the time.

I have had this issue for almost two months now, and mouse is working
perfectly. I had to click away the notification almost every time I
moved the mouse. I was then able to make the notifications appear less
frequently, but the notification still always appear after some
interval, and always after I log in.

Here are some specific things I have tried, they have not helped.

https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
low-notification-in-ubuntu-18-04

1)
Description: Ubuntu 18.04.1 LTS
Release: 18.04

2)
I assume the packet in question is notify-osd, not sure.
notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
0.9.35+16.04.20160415-0ubuntu2 500
500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

3) I expected that no notifications would appear when notifications
are set to off

4) Mouse battery low - notification always appears
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio
/dev/snd/controlC0: ohto 2927 F pulseaudio
/dev/snd/controlC1: ohto 2927 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-07-28 (79 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-UP5 TH-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798127] Re: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS

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-rc8


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

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

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

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

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

** Tags added: kernel-da-key

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

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

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as
  root FS

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

Bug description:
  This was reported by a hardware partner.  The system set up is a
  server with 512GB RAM and an M.2 NVMe drive as the root
  filesystem/boot device.

  Per the customer, when running the certification Memory Stress test
  (utilizing several stress-ng stressors run in sequence) the system
  freezes with CPU Soft Lockup errors appearing on console whe the
  "stack" stressor is run.

  Tester has tried with 2.5” SATA (1TB), 2.5” NVMe (800GB), and M.2 NVMe
  (1.9TB).

  So far, this only seems to affect the 4.15 kernel.  The tester has
  tried using the 2.5" SATA SSD as the RootFS/Boot device and the tests
  pass on all attempts.  It is ONLY when using the M.2 NVMe as the root
  / boot device that the tests cause a lockup.  The tester is re-trying
  now with the 2.5" NVMe device to see if this only occurs with the M.2
  NVMe.

  The tester has tried this on the following while using the M.2 NVMe as the 
rootFS/Boot device:
  Test run #1 – 16.04.5 at kernel 4.15; Result: Failed stress-ng memory on 
stack stressor
  Test run #2 – 18.04.1 at kernel 4.15; Result: Failed stress-ng memory on 
stack stressor
  Test run #3 – 16.04.5 at kernel 4.4; Result: Passed stress-ng memory test

  
  The stress-ng command invoked at the time the soft lockups occur is this:

  'stress-ng -k --aggressive --verify --timeout 300 --stack 0'

  This can be reproduced by running the memory_stress_ng test script
  from the cert suite:

  sudo /usr/lib/plainbox-provider-certification-
  server/bin/memory_stress_ng

  It may be more easily reproducible running the stack stressor alone,
  or the whole memory stress script without dealing with Checkbox.

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

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

S/PDIF is on, like in the case of Felipe, but headphones never worked.

Played around with hdajackretask and hdajacksensetest, found the output
on pin 0x1b, jack insertion and removal is detected properly.
Unfortunately no audio output can be routed to the re-configured pin,
the only "sound" was/is a static bang consisting of a single peak
whenever it is switched on/off, and some static noise like a badly
isolated sound card from the 2000's picking up noises from a HDD cable
running close by.

-- 
You 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 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

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

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

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

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

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

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1798160] Re: Wrong screen refresh AOC G2260VWQ6

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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-rc8

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

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

Title:
  Wrong screen refresh AOC G2260VWQ6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04
  Screen: AOC G2260VWQ6 FreeSync
  GPU: Radeon R9 380 2GB
  Cable: HDMI

  The monitor supports 75Hz refresh. The system misidentifies the
  monitor. There is no 75Hz option. It's only 60Hz. Under Windows 7
  there was the same problem. The monitor drivers from the AOC website
  solved the problem.

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

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

[Kernel-packages] [Bug 1798166] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1798166/+attachment/5201853/+files/CRDA.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201866/+files/WifiSyslog.txt

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

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

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

No, headphones are not detected in my case:

4.15.0-36-lowlatency

[   29.354845] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
[   29.354848] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
[   29.354850] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0) <==
[   29.354851] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   29.354853] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   29.354854] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   29.354856] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
[   29.354857] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

-- 
You 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 1798166] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1798166/+attachment/5201865/+files/UdevDb.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1798166/+attachment/5201864/+files/RfKill.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201862/+files/ProcModules.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201863/+files/PulseList.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201861/+files/ProcInterrupts.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201860/+files/ProcEnviron.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201859/+files/ProcCpuinfoMinimal.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1798166/+attachment/5201856/+files/Lspci.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201855/+files/IwConfig.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201854/+files/CurrentDmesg.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201858/+files/ProcCpuinfo.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1798166/+attachment/5201857/+files/Lsusb.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

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

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

apport information

** Tags added: apport-collected bionic

** Description changed:

  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.
  
  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.
  
  Here are some specific things I have tried, they have not helped.
  
  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04
  
  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  
  3) I expected that no notifications would appear when notifications are
  set to off
  
  4) Mouse battery low - notification always appears
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
+  /dev/snd/controlC0:  ohto   2927 F pulseaudio
+  /dev/snd/controlC1:  ohto   2927 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-07-28 (79 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
+ ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-36-generic N/A
+  linux-backports-modules-4.15.0-36-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  bionic
+ Uname: Linux 4.15.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/15/2014
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F12
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: Z77X-UP5 TH-CF
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: To be filled by O.E.M.
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: To be filled by O.E.M.
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1798166/+attachment/5201852/+files/AlsaInfo.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/1798166

Title:
  “Mouse battery low” notification appears even when all notifications
  disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic

[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification appears even when all notifications disabled

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect -p linux 1798166

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

Title:
“Mouse battery low” notification appears even when all notifications
disabled

Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Incomplete

Here are some specific things I have tried, they have not helped.

https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
low-notification-in-ubuntu-18-04

1)
Description: Ubuntu 18.04.1 LTS
Release: 18.04

3) I expected that no notifications would appear when notifications
are set to off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions

[Kernel-packages] [Bug 1792580] Re: Mounting SOFS SMB shares fails

That is actually good news.  That means the backport of commit
b327a717e50698039 is good.  It also means we are missing a commit in
v4.16-rc1 from Bionic.

Can you confirm v4.16-rc1 does not exhibit the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

If it is good, I can perform a "Reverse" bisect to identify the missing
commit.

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

Title:
  Mounting SOFS SMB shares fails

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Ubuntu 18.04.1 LTS 4.15.0-33.36-generic
  cifs-utils 2:6.8-1

  Mounting scale-out SMB shares is failing.

  mount -t cifs -o 
credentials=/tmp/creds,domain=cbs.com,uid=114,gid=119,vers=3.0,_netdev,nodfs 
//s2dscaleout.cbs.com/glance-images /tmp/test_mount
  mount error(5): Input/output error
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  What works:
  * mounting the share from a 16.04 host
  * mounting standalone smb3 shares

  Relevant error from the log (full logs attached separately):
  Sep 14 11:12:05 r07-u13 kernel: Status code returned 0xc0c9 
STATUS_NETWORK_NAME_DELETED
  Sep 14 11:12:05 r07-u13 kernel: 
/build/linux-81MBYC/linux-4.15.0/fs/cifs/smb2maperror.c: Mapping SMB2 status 
code 0xc0c9 to POSIX err -5

  Share server os: Windows Server 2016 10.0.14393
  PS C:\Users\jujuadmin> get-smbshare glance-images | fl *

  ShareState: Online
  AvailabilityType  : ScaleOut
  ShareType : FileSystemDirectory
  FolderEnumerationMode : Unrestricted
  CachingMode   : Manual
  SmbInstance   : Default
  CATimeout : 0
  ConcurrentUserLimit   : 0
  ContinuouslyAvailable : True
  CurrentUsers  : 2
  Description   :
  EncryptData   : False
  Name  : glance-images
  Path  : C:\ClusterStorage\Volume1\GLANCE-IMAGES
  Scoped: True
  ScopeName : S2DSCALEOUT
  ShadowCopy: False
  Special   : False
  Temporary : False
  Volume: \\?\Volume{5faf880d-d308-4058-9ec2-d19d48089495}\
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  7 16:51 seq
   crw-rw 1 root audio 116, 33 Sep  7 16:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  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:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R710
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=ba74e4cf-9634-4049-abd8-0ed721836a41 ro
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-33-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 07/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 6.4.0
  dmi.board.name: 0YDJK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR710:pvr:rvnDellInc.:rn0YDJK3:rvrA14:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R710
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1798160] Re: Wrong screen refresh AOC G2260VWQ6

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect -p linux 1798160

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

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

Title:
  Wrong screen refresh AOC G2260VWQ6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04
  Screen: AOC G2260VWQ6 FreeSync
  GPU: Radeon R9 380 2GB
  Cable: HDMI

  The monitor supports 75Hz refresh. The system misidentifies the
  monitor. There is no 75Hz option. It's only 60Hz. Under Windows 7
  there was the same problem. The monitor drivers from the AOC website
  solved the problem.

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

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

[Kernel-packages] [Bug 1796591] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package n

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.107-0ubuntu0.18.04.1

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

Bug description:
  install failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-compute-390 (not installed)
  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
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Oct  7 22:12:51 2018
  DpkgTerminalLog:
   Preparing to unpack .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ...
   Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-10-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  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/1796591/+subscriptions

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Leonardo Müller

** Tags added: kernel-fixed-upstream

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

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

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

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1798160] [NEW] Wrong screen refresh AOC G2260VWQ6

You have been subscribed to a public bug:

Ubuntu 18.04
Screen: AOC G2260VWQ6 FreeSync
GPU: Radeon R9 380 2GB
Cable: HDMI

The monitor supports 75Hz refresh. The system misidentifies the monitor.
There is no 75Hz option. It's only 60Hz. Under Windows 7 there was the
same problem. The monitor drivers from the AOC website solved the
problem.

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


** Tags: 75hz aoc freesync
-- 
Wrong screen refresh AOC G2260VWQ6
https://bugs.launchpad.net/bugs/1798160
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

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

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

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

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

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

** Bug watch added: freedesktop.org Bugzilla #107899
   https://bugs.freedesktop.org/show_bug.cgi?id=107899

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=107899
   Importance: Unknown
   Status: Unknown

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

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

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.
  
  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  
  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  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/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1798165] [NEW] Vulkan applications cause permanent memory leak with Intel GPU

2018-10-16 Thread Leonardo Müller

Public bug reported:

Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
memory is never freed and can cause a system crash if the applications
are used for long enough. Certain applications can make the leak be as
high as 10 MB/minute.

Details about this bug can be seen at
https://github.com/doitsujin/dxvk/issues/632 and
https://bugs.freedesktop.org/show_bug.cgi?id=107899

This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18. The
particular commit is:

commit a2cef7d049f07995406b403605119a54881daf15
Author: Jason Ekstrand 
Date:   Wed Sep 26 02:17:03 2018 -0500

drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set

commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.

We attempt to get fences earlier in the hopes that everything will
already have fences and no callbacks will be needed.  If we do succeed
in getting a fence, getting one a second time will result in a duplicate
ref with no unref.  This is causing memory leaks in Vulkan applications
that create a lot of fences; playing for a few hours can, apparently,
bring down the system.

Cc: sta...@vger.kernel.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
Reviewed-by: Chris Wilson 
Signed-off-by: Jason Ekstrand 
Signed-off-by: Sean Paul 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
Signed-off-by: Greg Kroah-Hartman 


On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: 
https://i.imgur.com/qMAvuwl.png

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
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/controlC0:  usuario4655 F pulseaudio
 /dev/snd/seq:usuario4640 F timidity
CurrentDesktop: XFCE
Date: Tue Oct 16 14:16:54 2018
HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
InstallationDate: Installed on 2017-06-13 (489 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-36-generic N/A
 linux-backports-modules-4.15.0-36-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
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 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in linux package in Ubuntu:
  New

Bug description:
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  
  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
  
  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref wi

[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

Hello Daniel,

Within the Cosmic [0]planning, the kernel freeze is detailed (October 4th):
[0] https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseSchedule
[1] https://wiki.ubuntu.com/KernelFreeze

The kernel is already frozen, probably the version that does not exist
yet (Linux 4.18.0-11.x) will work correctly for you.

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  High GPU temperature after kernel 4.18.0.9.10 on AMD RX460

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

Bug description:
  Hello,

  Today I have received an update for Linux kernel which upgraded the
  kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately
  after restart I noticed that the GPU temperature is abnormally High...

  Before Update:
  - GPU fan set to off on idle
  - GPU idle temperature: 29-32 C

  After Update:
  - GPU fan set to off on idle
  - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep 
it on 33 C)

  I have also tried to boot from the older kernel (4.18.0.8) and
  everything is normal there!

  System spec:
  - MB: ASUS Prime x299-deluxe
  - CPU: Intel Corei7 7820x skylake-x
  - GPU: AMD RX460

  glxinfo | grep OpenGL:

  OpenGL vendor string: X.Org
  OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 
3.26.0, 4.18.0-9-generic, LLVM 7.0.0)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1
  OpenGL core profile shading language version string: 4.50
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1
  OpenGL shading language version string: 4.40
  OpenGL context flags: (none)
  OpenGL profile mask: compatibility profile
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
  OpenGL ES profile extensions:

  sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info:

  Clock Gating Flags Mask: 0x37bcf
   Graphics Medium Grain Clock Gating: On
   Graphics Medium Grain memory Light Sleep: On
   Graphics Coarse Grain Clock Gating: On
   Graphics Coarse Grain memory Light Sleep: On
   Graphics Coarse Grain Tree Shader Clock Gating: Off
   Graphics Coarse Grain Tree Shader Light Sleep: Off
   Graphics Command Processor Light Sleep: On
   Graphics Run List Controller Light Sleep: On
   Graphics 3D Coarse Grain Clock Gating: Off
   Graphics 3D Coarse Grain memory Light Sleep: Off
   Memory Controller Light Sleep: On
   Memory Controller Medium Grain Clock Gating: On
   System Direct Memory Access Light Sleep: Off
   System Direct Memory Access Medium Grain Clock Gating: On
   Bus Interface Medium Grain Clock Gating: Off
   Bus Interface Light Sleep: On
   Unified Video Decoder Medium Grain Clock Gating: On
   Video Compression Engine Medium Grain Clock Gating: On
   Host Data Path Light Sleep: Off
   Host Data Path Medium Grain Clock Gating: On
   Digital Right Management Medium Grain Clock Gating: Off
   Digital Right Management Light Sleep: Off
   Rom Medium Grain Clock Gating: On
   Data Fabric Medium Grain Clock Gating: Off

  GFX Clocks and Power:
   1750 MHz (MCLK)
   1212 MHz (SCLK)
   214 MHz (PSTATE_SCLK)
   300 MHz (PSTATE_MCLK)
   1081 mV (VDDGFX)
   18.65 W (average GPU)

  GPU Temperature: 39 C
  GPU Load: 0 %

  UVD: Disabled

  VCE: Disabled

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-9-generic 4.18.0-9.10
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shadowfax   3078 F pulseaudio
   /dev/snd/controlC0:  shadowfax   3078 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 20:27:13 2018
  InstallationDate: Installed on 2018-09-26 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic 
root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-9-generic N/A
   linux-backports-modules-4.18.0-9-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default

[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460