date:20181022

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial)
  derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 
(linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 23. October 2018 06:34 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial)
  derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 
(linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Tuesday, 23. October 2018 06:34 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux: 4.4.0-138.164 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial)
  derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 
(linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795582/+subscriptions

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

2018-10-22 Thread Po-Hsu Lin

** Summary changed:

- mlock203 test in ubuntu_ltp_syscalls failed with X-AWS
+ mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

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

** No longer affects: ubuntu-kernel-tests

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

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

-- 
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 Xenial kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

2018-10-22 Thread Carl Reinke

6a8b25a has the bug.

I also tried 4.18.0-10.11 from cosmic, and it appears to still have the
bug. :(

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

rtimai,

r8169 supports more than 50 different variants. The original bug is for
8168[gh], and yours is r8106e. So it would be better to file a new bug.

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvr

[Kernel-packages] [Bug 1795598] Re: linux: -proposed tracker

2018-10-22 Thread Kleber Sacilotto de Souza

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/prepare-package-lbm
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-lbm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795598/+subscriptions

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

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

> I presume you want me to try the 9 rc's in the `4.15` kernel chain? I
assume the 8 to 9 rc's in `4.13`, 4.14`, `4.16`, `4.17`, `4.18` and `4.19`
rc's don't have to be installed?

Try 4.14 first. If it's bad, then the regression starts in one of the v4.14-rc* 
kernel.
If it's good, then the regression is in v4.15-rc* ~ v4.15.

Find the good and bad (e.g. v4.15-rc1 and v4.15-rc2), then start a
kernel bisect.

Using stable kernel (or LTS kernel) doesn't help, it's not linear
between each kernel releases.

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

Title:
  Laptop wakes up immediately after suspend or hibernation

Status in linux package in Ubuntu:
  Expired

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

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

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

[Kernel-packages] [Bug 1797074] Re: linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker

2018-10-22 Thread Steve Langasek

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797074/+subscriptions

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

[Kernel-packages] [Bug 1798979] Re: Hama "Slim" USB 3.0 Multi Card Reader doesn't work

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel
between v4.16-rc1 to v4.18, from http://kernel.ubuntu.com/~kernel-
ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

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

Title:
  Hama "Slim" USB 3.0 Multi Card Reader doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have problems with Hama "Slim" USB 3.0 Multi Card Reader (model
  number 00114837, https://www.hama.com/00114837/hama-slim-usb-30-multi-
  card-reader-black) attached to a USB 3.0. After attaching the reader
  (or booting the system) the device works for some time, about a minute
  or so. It's blue power led is on. Then CPU load goes up to 30-50% and
  the power led on the reader starts turning off and on with a several
  seconds interval. It looks like the device is being repeatedly
  reinitialized. dmesg shows these lines while this is happening:

  [  147.251654] xhci_hcd :05:00.0: WARN Set TR Deq Ptr cmd failed due to 
incorrect slot or ep state.
  [  147.447251] xhci_hcd :05:00.0: WARN Event TRB for slot 1 ep 4 with no 
TDs queued?
  [  220.546280] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [  220.546283] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [  220.685727] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using 
xhci_hcd
  [  251.266583] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [  251.266584] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [  251.398028] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using 
xhci_hcd
  [  284.045003] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [  284.045006] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [  284.180500] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using 
xhci_hcd
  [  314.761869] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr
  [  314.761873] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending.
  [  314.893338] usb 6-2: reset SuperSpeed Gen 1 USB device number 2 using 
xhci_hcd

  and so on.

  No cards are inserted in the device and no user activity on the
  system, the problem starts happening "on its own". I tried plugging
  the device in a different USB 3.0 slot, it doesn't help. The device
  worked on the same system in Kubuntu 18.04, linux kernel 4.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-generic 4.18.0.10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lastique   3112 F pulseaudio
   /dev/snd/controlC1:  lastique   3112 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 20 19:31:35 2018
  InstallationDate: Installed on 2015-05-01 (1267 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications ab

[Kernel-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

Please raise the issue to alsa-de...@alsa-project.org for ALSA
maintainers' awareness.

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

2018-10-22 Thread Jake Jensen

That's pretty much all you can do unless you're capable of writing
drivers or reading ACPI tables yourself.

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

Title:
  ELAN469D touch pad not working

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

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

2018-10-22 Thread Patrick Van Oosterwijck

All that seems to happen here is that you make me try new BIOSes and
kernels as they come out.  Disappointing.

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

Title:
  ELAN469D touch pad not working

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

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1788500] Re: power goes off on laptop

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

Title:
  power goes off on laptop

Status in linux package in Ubuntu:
  Expired

Bug description:
  my laptop keeps powering off on it's own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134
  Uname: Linux 4.4.0-133-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 22 16:18:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (primary) [1179:ff10]
 Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) [1179:ff10]
  InstallationDate: Installed on 2016-12-13 (617 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: TOSHIBA Satellite A205
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic 
root=UUID=e4590063-6da5-42db-86b2-bfd532bc73c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.70
  dmi.board.name: SANTA ROSA CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.70:bd11/06/2007:svnTOSHIBA:pnSatelliteA205:pvrPSAF3U-0PV00V:rvnIntelCorporation:rnSANTAROSACRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Satellite A205
  dmi.product.version: PSAF3U-0PV00V
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 22 16:02:15 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13893 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Kernel-packages] [Bug 1788455] Re: Issue Creating Files with Equal sign =

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

Title:
  Issue Creating Files with Equal sign =

Status in linux package in Ubuntu:
  Expired

Bug description:
  UBUNTU 18.04LTS

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  touch a=b
  results into file
  'a=b'
  NOTE: single quote (') is part of the filename
  This issue can be made with mkdir on directories as well as tar and other 
tools as well.
  As far as I could see, it is only with equal sign "=" and not with othter 
characters. However, I just checked a few.

  
  In UBUNTU 16.04LTS 
  touch a=b 
  results into file
  a=b

  I assume, that behaviour in UBUNTU 16.04 is correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 21 17:21 seq
   crw-rw 1 root audio 116, 33 Aug 21 17:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  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:
  Date: Wed Aug 22 17:39:24 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=625af5d2-94ba-11e8-ab53-00505698565c ro maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1765035] Re: lttng DKMS module failed to build on Azure StandardA0 instance [gcc: internal compiler error: Killed (program cc1)]

2018-10-22 Thread Po-Hsu Lin

*** This bug is a duplicate of bug 1791032 ***
https://bugs.launchpad.net/bugs/1791032

** This bug has been marked a duplicate of bug 1791032
   Failed to compile lttng module on small Azure nodes

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

Title:
  lttng DKMS module failed to build on Azure StandardA0 instance [gcc:
  internal compiler error: Killed (program cc1)]

Status in ubuntu-kernel-tests:
  New
Status in gcc-6 package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  This issue only occur on the StandardA0 instances for Azure (other
  instances will pass with this test)

  The build process will be interrupted with:
  gcc: internal compiler error: Killed (program cc1)

  
  Here is complete the module build log:
  http://paste.ubuntu.com/p/FWRr9Vycz4/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-1012-azure 4.13.0-1012.15
  ProcVersionSignature: User Name 4.13.0-1012.15-username 4.13.13
  Uname: Linux 4.13.0-1012-azure x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr 18 11:52:20 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1799035] Re: [SKL] My ubuntu doesn't show resolution above 1024x768

That is the problem then. If the kernel can't get EDID data from your
monitor then it has no idea what the supported resolutions are.

First, please try unplugging and re-plugging your monitor a few times.
If that doesn't fix it then please also try a different monitor cable if
you can.

Second, if this is a software bug then we now know it is in the kernel.
So reassigning there...

** Changed in: xorg-server (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/1799035

Title:
  [SKL] My ubuntu doesn't show resolution above 1024x768

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

Bug description:
  my ubuntu doesn't show resolution above 1024X800

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 14:35:55 2018
  DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
  InstallationDate: Installed on 2017-05-01 (537 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd03/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1799035] Re: [SKL] My ubuntu doesn't show resolution above 1024x768

Also, please try:

  sudo cat /sys/class/drm/*/edid

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

Title:
  [SKL] My ubuntu doesn't show resolution above 1024x768

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

Bug description:
  my ubuntu doesn't show resolution above 1024X800

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 14:35:55 2018
  DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
  InstallationDate: Installed on 2017-05-01 (537 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd03/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1799035] Re: [SKL] My ubuntu doesn't show resolution above 1024x768

2018-10-22 Thread Bhushan

out of cat /sys/class/drm/*/edid is blank

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

Title:
  [SKL] My ubuntu doesn't show resolution above 1024x768

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

Bug description:
  my ubuntu doesn't show resolution above 1024X800

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 14:35:55 2018
  DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
  InstallationDate: Installed on 2017-05-01 (537 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd03/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

2018-10-22 Thread Denis

It's true. Linux kernel v4.19 support touchpad. Also scroll works.

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

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

Bug description:
  It seems there might be a new hardware variant of the elan trackpad in
  the newer ASUS machines.

  The issue is the shown here with some reasonably deep investigation.
  Is this something that I can do or am I reduced to having to find out
  a mouse if I want to use Linux?

  https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

  user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
   Virtual core pointer  id=2[master pointer  (3)]
     ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
     ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
     ↳ Logitech USB Receiver id=13   [slave  pointer  (2)]
   Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
  ↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

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

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

[Kernel-packages] [Bug 1799218] Re: brightness controller missing after installing nvidia-390

It looks like your kernel command line has a custom backlight change,
which is unusual:

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash
acpi_backlight=vendor vt.handoff=1

Maybe try:
  1. Removing the "acpi_backlight=vendor" from /etc/default/grub
  2. sudo update-grub
  3. Reboot


** Summary changed:

- brightness controller missing
+ brightness controller missing after installing nvidia-390

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

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

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

Title:
  brightness controller missing after installing nvidia-390

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

Bug description:
  brightness controller gone after installing nvidia drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 18:26:31 2018
  DistUpgraded: 2018-09-13 00:30:24,004 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2018-08-16 (66 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH3AEN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (39 days ago)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH3AEN:pvrC1074QWS:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEH3AEN
  dmi.product.version: C1074QWS
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 17:22:30 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1799228] Re: USB-ports do not work

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

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

Title:
  USB-ports do not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Two out of 3 USB-ports are not regognized anymore (i.e. when I insert
  a USB-stick, it will not be shown in Nautilus). I tried various
  workarounds from ubuntuusers, but they were not successful. Among them
  to use "dpkg-reconfigure x-server". X-org now reported an error,
  docuimented in the attachment.

  Earlier I wanted to create an image with Clonezilla and selected a
  USB-stick at port #2 as target, however, the target was not detected
  successfully and the backup-procedure stopped. I suspect that the
  issues may be relatd.

  Kind regards,
  Stefan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 22 15:57:33 2018
  DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() (E:Nicht 
gesperrt)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.4.0-137-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1ccd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a]
  InstallationDate: Installed on 2016-07-21 (823 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash pci=noaer 
acpi_osi= acpi_backlight=native vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 15:43:15 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1799228] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (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/1799228

Title:
  USB-ports do not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Two out of 3 USB-ports are not regognized anymore (i.e. when I insert
  a USB-stick, it will not be shown in Nautilus). I tried various
  workarounds from ubuntuusers, but they were not successful. Among them
  to use "dpkg-reconfigure x-server". X-org now reported an error,
  docuimented in the attachment.

  Earlier I wanted to create an image with Clonezilla and selected a
  USB-stick at port #2 as target, however, the target was not detected
  successfully and the backup-procedure stopped. I suspect that the
  issues may be relatd.

  Kind regards,
  Stefan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 22 15:57:33 2018
  DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() (E:Nicht 
gesperrt)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.48, 4.4.0-137-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1ccd]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a]
  InstallationDate: Installed on 2016-07-21 (823 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash pci=noaer 
acpi_osi= acpi_backlight=native vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 15:43:15 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1799218] [NEW] brightness controller missing after installing nvidia-390

You have been subscribed to a public bug:

brightness controller gone after installing nvidia drivers

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 22 18:26:31 2018
DistUpgraded: 2018-09-13 00:30:24,004 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
InstallationDate: Installed on 2018-08-16 (66 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Sony Corporation VPCEH3AEN
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-12 (39 days ago)
dmi.bios.date: 11/17/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R0190Z9
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH3AEN:pvrC1074QWS:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEH3AEN
dmi.product.version: C1074QWS
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 17:22:30 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
brightness controller missing after installing nvidia-390
https://bugs.launchpad.net/bugs/1799218
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-390 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 1799228] [NEW] USB-ports do not work

You have been subscribed to a public bug:

Two out of 3 USB-ports are not regognized anymore (i.e. when I insert a
USB-stick, it will not be shown in Nautilus). I tried various
workarounds from ubuntuusers, but they were not successful. Among them
to use "dpkg-reconfigure x-server". X-org now reported an error,
docuimented in the attachment.

Earlier I wanted to create an image with Clonezilla and selected a USB-
stick at port #2 as target, however, the target was not detected
successfully and the backup-procedure stopped. I suspect that the issues
may be relatd.

Kind regards,
Stefan

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompositorRunning: None
Date: Mon Oct 22 15:57:33 2018
DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() (E:Nicht 
gesperrt)
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.48, 4.4.0-137-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1ccd]
   Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a]
InstallationDate: Installed on 2016-07-21 (823 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ASUSTeK COMPUTER INC. X555UB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash pci=noaer 
acpi_osi= acpi_backlight=native vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago)
dmi.bios.date: 01/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555UB.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555UB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555UB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 22 15:43:15 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
USB-ports do not work
https://bugs.launchpad.net/bugs/1799228
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 1773940] Re: Enable AMD PCIe MP2 for AMDI0011

2018-10-22 Thread Yuan-Chen Cheng

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

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

Title:
  Enable AMD PCIe MP2 for AMDI0011

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

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

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

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

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

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

[Kernel-packages] [Bug 1797074] Re: linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797074/+subscriptions

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

2018-10-22 Thread Alec Duroy

Successfully upgraded to 4.19. Stress-ng memory test passed without lockup 
issue. New rebuild kernel 4.19  has fixed the issue. Refer to text below:
---
ubuntu@fluent-orca:~$ uname -r
4.19.0-041900rc8-generic

ubuntu@fluent-orca:~$ sudo stress-ng -k --aggressive --verify --timeout 300 
--stack 0
stress-ng: info:  [3516] dispatching hogs: 112 stack
stress-ng: info:  [3516] successful run completed in 311.37s (5 mins, 11.37 
secs) ubuntu@fluent-orca:~$


-- 
You 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:
  Confirmed
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.

  UPDATE: The tester also confirms that the 2.5" NVMe drives also fail
  with the 4.15 kernel and pass with the 4.4 kernel.  The SSD works on
  all kernels.

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 1798127] Re: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS

2018-10-22 Thread Alec Duroy

'kernel-fixed-upstream'

-- 
You 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:
  Confirmed
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.

  UPDATE: The tester also confirms that the 2.5" NVMe drives also fail
  with the 4.15 kernel and pass with the 4.4 kernel.  The SSD works on
  all kernels.

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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-10-22 Thread NJ

@dr-strangehate

Sorry if this is an obtuse question, but you are saying that this
problem owes to a bug in the Linux 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/1791427

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-10-22 Thread Melvin1981

Texted to NVidia support about the issue. Got reply

Your case is being escalated to our Level 2 Tech Support group. The
Level 2 agents will review the case notes and may attempt to recreate
your issue or find a workaround solution if possible. As this process
may take some time we ask that you be patient and a Level 2 tech will
contact you as soon they can to help resolve your issue.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Kernel-packages] [Bug 1799281] Re: [Bionic][Cosmic] ipmi: Fix timer race with module unload

2018-10-22 Thread Manoj Iyer

-- cosmic testing --
ubuntu@starbuck:~$ uname -a 
Linux starbuck 4.18.0-10-generic #11~lp1799281+cosmic.1 SMP Mon Oct 22 21:45:47 
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$ for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; 
sudo modprobe ipmi_ssif || exit; done

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

Title:
  [Bionic][Cosmic]  ipmi: Fix timer race with module unload

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  If you attempt to remove and insert the ipmi_ssif module a number of times, 
it would result in a kernel panic. This is due to mod_timer from arming a timer 
that was already removed by del_timer during module unload.

  [Fix]
  In linux-next:
  0711e8c1b457 ipmi: Fix timer race with module unload

  [Test]
  -- Test Case --
  for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done
  
  After the patch was applied, no kernel panics were obsereved. Tested on 
Cavium ThunderX2.

  [Regression Risk]
  The patch was applied to bionic and tested tested on a Cavium ThunderX2 and 
no regressions were found. Risk of regression none.

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-10-22 Thread dr_strangehate

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

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)

2018-10-22 Thread Luke Williams

This has been an issue ever since I have used this laptop with any distribution 
of Linux. Up until 18.10 with touchpad would be non-functional. It would jump 
all over the screen and would basicaly be unusable with the laptop. Since 
18.10. and kernel 4.17.4 the touchpad works as far as no longer jumping around 
the screen, but as soon as you touch the touchpad with all 5 fingers, it 
crashes and can no longer use the touchpad. Also, after about 10 minutes of 
use, the touchpad locks up and the only way to get it back is to either reboot 
the laptop or unload the kmods for the elan device and reload them and then you 
can use the touchpad for about 20 minutes again. 
I created a cron job that does this every 5 minutes so that I can use my 
touchpad with out worry or I just use an external mouse.

The troublesome thing about this is that this laptop has been around for
over a year, and with Windows, there are no issues, and with the UEFI
BIOS, the mouse works with no issues. Just 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/1798363

Title:
  i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report
  (16/65535)

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

Bug description:
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid 
i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
  

  Lots of these things

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 2908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 17 20:07:13 2018
  InstallationDate: Installed on 2018-10-10 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1799305] Re: No desktop at boot after upgrade form 18.04 to 18.10

2018-10-22 Thread Paul Broadhead

** Description changed:

  I upgrade from 18.04 to 18.10 and now the desktop does not start on a
  fresh boot.  The console output ends with "Starting GNOME Display
  Manager".  I cannot switch VTs, my keyboard and mouse are unresponsive
  though RESUIB sequence works to reboot.  If I remote login using ssh, I
- can restart run "systemctrl restart gdm3" and I get a working login
- screen and can continue as expected.  If I remove my nvidia drivers the
- desktop start as expected from a clean boot.  Examining /var/log/syslog
- appears to show the nvidia driver failing to load correctly; see below.
+ can run "systemctrl restart gdm3" and I get a working login screen and
+ can continue as expected.  If I remove my nvidia drivers the desktop
+ starts as expected from a clean boot.  Examining /var/log/syslog appears
+ to show the nvidia driver failing to load correctly; see below.
  
  In the failed state "systemctl status gdm3" shows:
  
  ● gdm.service - GNOME Display Manager
-Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: 
enabled)
-Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago
-   Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, 
status=0/SUCCESS)
-   Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
-  Main PID: 1880 (gdm3)
- Tasks: 3 (limit: 4915)
-Memory: 5.7M
-CGroup: /system.slice/gdm.service
-└─1880 /usr/sbin/gdm3
+    Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: 
enabled)
+    Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago
+   Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, 
status=0/SUCCESS)
+   Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
+  Main PID: 1880 (gdm3)
+ Tasks: 3 (limit: 4915)
+    Memory: 5.7M
+    CGroup: /system.slice/gdm.service
+    └─1880 /usr/sbin/gdm3
  
  Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager...
  Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager.
  Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
  Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead.
  Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead.
  root@hagrid:/var/log# grep 2634 syslog
  Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead.
  Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead.
  
  
  This is a section form syslog:
  Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon...
  Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened
  Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon.
  Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and 
group ID 129
  Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling 
drmModeGetResources() failed, assuming we have no outputs
  Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865)
  Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs 
found
  Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered
  Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized
  Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon...
  Oct 22 22:06:54 hagrid kernel: [   86.847749] virbr0: port 1(virbr0-nic) 
entered blocking state
  Oct 22 22:06:54 hagrid kernel: [   86.847753] virbr0: port 1(virbr0-nic) 
entered listening state
  Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
  Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon.
  Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15
  Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed.
  Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked.
  Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not 
needed anymore. Stopping.
  Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed.
  Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121...
  Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced
  Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus...
  Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865)
  Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default.
  Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus.
  Oct 22 22:06:54 hagrid gdm3: Child process -2

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

2018-10-22 Thread Anthony Wong

Qualcomm released new firmware recently that's worth checking out:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/qca?id=534daf431c88b24236d23572039cdd79223b246a

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

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

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

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

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

  My syslog when this happens:

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

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-10-22 Thread whl2

5 days ago I've installed Ubuntu 16.0.1 with kernel 4.4.0-21-generic on
the second disk. No updates to kernel or libs were installed. So far no
fan issue appeared. Also, 16.04 correctly goes to sleep when lid is
closed which was not always the case with 18.04.

Also, probably not related, but I always see one of kworker thread consuming
100% CPU, however it doesn't seem to affect anything, including thermal regime,
most of the times fans are on low RPM.
Running CPU-heavy loads, like games, spins up the fans, but they always
throttle down after the heavy load is over.

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

Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
Incomplete

Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.

Things tried:

Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.

asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.

4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.

Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.

---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1796553] Re: BT mouse getting reset during operation

2018-10-22 Thread Ralf Hildebrandt

btusb.enable_autosuspend=0 seems to have worked (so far)...

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

Title:
  BT mouse getting reset during operation

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

Bug description:
  
  (note: It's unclear to me if that's a kernel regression or an issue with 
bluez)

  
  I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

  It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
  a strange disconnect behaviour:

  1) Mouse is working ok
  2) Mouse suddenly stops
  3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

  when this happens, dmesg reports:

  [57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
  ehci-pci

  Disabling bluetooth and enabling it again results in:

  [57833.455866] usb 1-1.3: USB disconnect, device number 18
  [57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
  [57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
  [57837.016248] usb 1-1.3: New USB device found, idVendor=8087, 
idProduct=07dc, bcdDevice= 0.01
  [57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
  [57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  [57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
  [57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
  [57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
  [57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

  $ bluetoothctl --version
  bluetoothctl: 5.50

  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [TECKNET BM306]# show
  Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
  [TECKNET BM306]# devices
  Device 20:9B:A5:68:AE:67 SoundBuds Flow
  Device DC:2C:26:01:24:23 TECKNET BM306
  Device 88:71:E5:0E:6B:99 Echo-HPT
  Device 00:0B:E4:A0:A2:14 Nokia BH-103
  Device A8:96:75:8B:4F:49 Moto G5S Plus
  Device 00:02:5B:20:75:3C Trust SPK-02
  Device 88:75:98:F2:5C:9E NS9+
  Device 00:E0:4C:D5:E0:F5 SoundCore mini
  [TECKNET BM306]# info DC:2C:26:01:24:23
  Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129

  
  $ rfkill list
  2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
  4: dell-wwan: Wireless WAN
Soft blocked: yes
H

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-10-22 Thread whl2

Oops, sorry for typo. Ubuntu 16.04.1

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1799305] [NEW] No desktop at boot after upgrade form 18.04 to 18.10

2018-10-22 Thread Paul Broadhead

Public bug reported:

I upgrade from 18.04 to 18.10 and now the desktop does not start on a
fresh boot.  The console output ends with "Starting GNOME Display
Manager".  I cannot switch VTs, my keyboard and mouse are unresponsive
though RESUIB sequence works to reboot.  If I remote login using ssh, I
can restart run "systemctrl restart gdm3" and I get a working login
screen and can continue as expected.  If I remove my nvidia drivers the
desktop start as expected from a clean boot.  Examining /var/log/syslog
appears to show the nvidia driver failing to load correctly; see below.

In the failed state "systemctl status gdm3" shows:

● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: 
enabled)
   Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago
  Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, 
status=0/SUCCESS)
  Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1880 (gdm3)
Tasks: 3 (limit: 4915)
   Memory: 5.7M
   CGroup: /system.slice/gdm.service
   └─1880 /usr/sbin/gdm3

Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager...
Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager.
Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead.
Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead.
root@hagrid:/var/log# grep 2634 syslog
Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead.
Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead.


This is a section form syslog:
Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon...
Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened
Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon.
Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and 
group ID 129
Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling 
drmModeGetResources() failed, assuming we have no outputs
Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865)
Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs 
found
Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered
Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized
Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon...
Oct 22 22:06:54 hagrid kernel: [   86.847749] virbr0: port 1(virbr0-nic) 
entered blocking state
Oct 22 22:06:54 hagrid kernel: [   86.847753] virbr0: port 1(virbr0-nic) 
entered listening state
Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon.
Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15
Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed.
Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked.
Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not 
needed anymore. Stopping.
Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed.
Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121...
Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission 
to remove its runtime data directory /var/run/nvidia-persistenced
Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus...
Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865)
Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default.
Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus.
Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead.


Description:Ubuntu 18.10
Release:18.10

nvidia-driver-390:
  Installed: 390.87-0ubuntu1
  Candidate: 390.87-0ubuntu1
  Version table:
 *** 390.87-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nvidia-driver-390 390.87-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 22 22:32:04 2018
InstallationDate: Installed on 2018-07-30 (84 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nvidia-graphics-drivers-390
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (4 days ago)

** Affects: nvidia-gra

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

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 1799237

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

** Tags added: 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/1799237

Title:
  mprotect fails on ext4 with dax

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

Bug description:
  I have a file located on ext4 mounted with "dax". When I call mmap on that 
file with protection flag different than PROT_NONE and pass the returned 
address to mprotect(..., PROT_NONE) it fails with:
  mprotect: Permission denied

  This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu 
kernel-specific.
  Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic

  Below is a code which can be used to reproduce the issue.

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

  int main(int argc, char *argv[])
  {
     if (argc < 3) {
    fprintf(stderr, "usage %s file size\n", 
argv[0]);
    return 1;
     }

     int size = atoi(argv[2]);

     int fd = open(argv[1], O_RDWR);
     if (fd < 0) {
    perror("open");
    return 1;
     }

     void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE, 
MAP_SHARED, fd, 0);
     if (addr == MAP_FAILED) {
    perror("mmap");
    return 1;
     }

     if(mprotect(addr, size, PROT_NONE)) {
    perror("mprotect");
    return 1;
     }

     return 0;
  }

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

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

[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax

2018-10-22 Thread Andreas Hasenack

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

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

Title:
  mprotect fails on ext4 with dax

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

Bug description:
  I have a file located on ext4 mounted with "dax". When I call mmap on that 
file with protection flag different than PROT_NONE and pass the returned 
address to mprotect(..., PROT_NONE) it fails with:
  mprotect: Permission denied

  This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu 
kernel-specific.
  Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic

  Below is a code which can be used to reproduce the issue.

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

  int main(int argc, char *argv[])
  {
     if (argc < 3) {
    fprintf(stderr, "usage %s file size\n", 
argv[0]);
    return 1;
     }

     int size = atoi(argv[2]);

     int fd = open(argv[1], O_RDWR);
     if (fd < 0) {
    perror("open");
    return 1;
     }

     void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE, 
MAP_SHARED, fd, 0);
     if (addr == MAP_FAILED) {
    perror("mmap");
    return 1;
     }

     if(mprotect(addr, size, PROT_NONE)) {
    perror("mprotect");
    return 1;
     }

     return 0;
  }

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

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

[Kernel-packages] [Bug 1759644] Re: [18.04] Regression: wired network does not work upon resume from suspend

2018-10-22 Thread Itai

*** This bug is a duplicate of bug 1752772 ***
https://bugs.launchpad.net/bugs/1752772

Same problem in 4.15.0-38-generic

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

Title:
  [18.04] Regression: wired network does not work upon resume  from
  suspend

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

Bug description:
  After upgrade to 18.04 (bionic) I've encountered the following
  regression: wired network connection does not work, when system is
  resumed from suspend.

  Reloading the kernel driver module seems to help:
  sudo modprobe -r r8169
  sudo modprobe r8169

  Could this be fixed structurally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 20:08:20 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-06 (811 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  ethernet  
1522260260  wo 28 mrt 2018 20:04:20 CEST  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/3  yes enp5s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   dzente  a899e56b-4048-43a8-bc38-9212d0af383b  wifi  
1493769143  wo 03 mei 2017 01:52:23 CEST  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- 
--  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp5s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/4  
Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1673 F pulseaudio
   /dev/snd/controlC0:  alexei 1673 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (812 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (7 days ago)
  UserGroup

[Kernel-packages] [Bug 1798776] Comment bridged from LTC Bugzilla

2018-10-22 Thread bugproxy

--- Comment From stefan.ra...@de.ibm.com 2018-10-22 16:40 EDT---
According to https://legacy.python.org/dev/peps/pep-0373/, end of life for 
Python 2.7 was moved to 2020 - that's still a wee bit!
Still, since kvm_stat should be Python 3 compatible by now, why not just go a 
head and try to convert to "#!/usr/bin/env python3" upstream? Are you folks up 
to submitting a respective patch upstream, or do you want me to...?

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

Title:
  kvm_stat : missing python dependency

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  After installing linux-tools-host, the included kvm_stat utility won't
  work:

  root@ubuntu:~# kvm_stat 
  -bash: /usr/bin/kvm_stat: /usr/bin/python: bad interpreter: No such file or 
directory

  Reason is that there is apparently no dependency on a python package
  from the linux-tools-host package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1798776/+subscriptions

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

[Kernel-packages] [Bug 1799277] Re: package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to install/upgrade: kan ikke åbne '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/li

2018-10-22 Thread Jimmy Merrild Krag

I see nothing that needs translation.

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

Title:
  package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: kan ikke åbne
  '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko
  .dpkg-new': Operationen er ikke tilladt

Status in linux package in Ubuntu:
  Opinion

Bug description:
  I'm pretty sure it was Sophos Antivirus that screwed things up.

  Don't get me started on why I have that piece of crap installed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
  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
  Date: Mon Oct 22 21:04:01 2018
  ErrorMessage: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  HibernationDevice: RESUME=UUID=7c76546e-c678-42c7-8cc2-d46d1228cb45
  InstallationDate: Installed on 2018-09-24 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20L9CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root 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-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET30W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET30W(1.16):bd09/20/2018:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T580
  dmi.product.name: 20L9CTO1WW
  dmi.product.version: ThinkPad T580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1799039] Re: Apple Facetime HD PCI (Broadcom 1570) not accessible

2018-10-22 Thread Wolf Rogner

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

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

Title:
  Apple Facetime HD PCI (Broadcom 1570) not accessible

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a reopened bug report related to #1716673: Apple Facetime HD
  PCI (Broadcom 1570) not accessible

  The camera still is not accessible. In the old report some suggested
  that I should try the latest kernel. Well, with 18.10 the kernel is
  even newer than the one available at the time of reporting.

  If no one writes a driver for the camera, there will never be a module
  for it.

  The module that ships with Ubuntu is not working.

  I do understand that rolling out a new version is tedious. But it should be 
possible to
  a) not permanently produce regressions and
  b) include some improvements beyond some irrelevant GUI overhauls.

  btw. My machine was purchased in 2015. I don't think that PCIe is such
  a new technology.

  (sorry for my serious frustration about 18.10. I thought with 18.04
  onward Canonical might have cought on)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   1914 F pulseaudio
   /dev/snd/controlC0:  wolf   1914 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 12:00:56 2018
  HibernationDevice: RESUME=UUID=539744c7-33c6-44da-a8b5-8bcf95f7845d
  InstallationDate: Installed on 2018-04-30 (174 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1799277] Re: package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to install/upgrade: kan ikke åbne '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/li

2018-10-22 Thread Jimmy Merrild Krag

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

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

Title:
  package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: kan ikke åbne
  '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko
  .dpkg-new': Operationen er ikke tilladt

Status in linux package in Ubuntu:
  Opinion

Bug description:
  I'm pretty sure it was Sophos Antivirus that screwed things up.

  Don't get me started on why I have that piece of crap installed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
  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
  Date: Mon Oct 22 21:04:01 2018
  ErrorMessage: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  HibernationDevice: RESUME=UUID=7c76546e-c678-42c7-8cc2-d46d1228cb45
  InstallationDate: Installed on 2018-09-24 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20L9CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root 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-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET30W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET30W(1.16):bd09/20/2018:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T580
  dmi.product.name: 20L9CTO1WW
  dmi.product.version: ThinkPad T580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1799277] Re: package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to install/upgrade: kan ikke åbne '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/li

2018-10-22 Thread Cristian Aravena Romero

Thank you for taking the time to report this issue and helping to make
Ubuntu better. We noticed that some of the sentences in this bug report
are not in English. If they were translated to English they would be
more understandable to triagers. Could you please translate them?

** 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/1799277

Title:
  package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: kan ikke åbne
  '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko
  .dpkg-new': Operationen er ikke tilladt

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm pretty sure it was Sophos Antivirus that screwed things up.

  Don't get me started on why I have that piece of crap installed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
  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
  Date: Mon Oct 22 21:04:01 2018
  ErrorMessage: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  HibernationDevice: RESUME=UUID=7c76546e-c678-42c7-8cc2-d46d1228cb45
  InstallationDate: Installed on 2018-09-24 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20L9CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root 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-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET30W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET30W(1.16):bd09/20/2018:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T580
  dmi.product.name: 20L9CTO1WW
  dmi.product.version: ThinkPad T580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1797074] Re: linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 22. October 2018 19:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 22. October 2018 19:31 UTC
+ phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1028.29~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1797061
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797074/+subscriptions

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

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

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 1799281

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

** Tags added: 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/1799281

Title:
  [Bionic][Cosmic]  ipmi: Fix timer race with module unload

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  If you attempt to remove and insert the ipmi_ssif module a number of times, 
it would result in a kernel panic. This is due to mod_timer from arming a timer 
that was already removed by del_timer during module unload.

  [Fix]
  In linux-next:
  0711e8c1b457 ipmi: Fix timer race with module unload

  [Test]
  -- Test Case --
  for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done
  
  After the patch was applied, no kernel panics were obsereved. Tested on 
Cavium ThunderX2.

  [Regression Risk]
  The patch was applied to bionic and tested tested on a Cavium ThunderX2 and 
no regressions were found. Risk of regression none.

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

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

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

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 1799276

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

** Tags added: 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/1799276

Title:
  [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The IPMI spec states:

  The purpose of the SPMI Table is to provide a mechanism that can be
  used by the OSPM (an ACPI term for “OS Operating System-directed
  configuration and Power Management” essentially meaning an ACPI-aware
  OS or OS loader) very early in the boot process, e.g., before the
  ability to execute ACPI control methods in the OS is available.

  When we are probing IPMI in Linux, ACPI control methods are available,
  so we shouldn't be probing using SPMI. It could cause some confusion
  during the probing process.

  [Fix]
  Fixed upstream in 4.17:
  commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
  Author: Corey Minyard 
  Date: Thu Mar 8 15:00:28 2018 -0600

  ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

  [Test]
  -- Test case --
  for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done
  --

  -- Before Applying the patch --
  Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new 
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
  Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of 
dmi-ipmi-ssif.1 failed with error -17

  -- With patch applied --
  Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
  Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying 
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave 
address 0x20
  Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new 
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)

  [Regression Potential]
  This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium 
ThunderX2 platform and no regressions were found.

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

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

[Kernel-packages] [Bug 1799277] [NEW] package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to install/upgrade: kan ikke åbne '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/

2018-10-22 Thread Jimmy Merrild Krag

Public bug reported:

I'm pretty sure it was Sophos Antivirus that screwed things up.

Don't get me started on why I have that piece of crap installed.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
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
Date: Mon Oct 22 21:04:01 2018
ErrorMessage: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
HibernationDevice: RESUME=UUID=7c76546e-c678-42c7-8cc2-d46d1228cb45
InstallationDate: Installed on 2018-09-24 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20L9CTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root 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-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N27ET30W (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET30W(1.16):bd09/20/2018:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T580
dmi.product.name: 20L9CTO1WW
dmi.product.version: ThinkPad T580
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package 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/1799277

Title:
  package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: kan ikke åbne
  '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko
  .dpkg-new': Operationen er ikke tilladt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm pretty sure it was Sophos Antivirus that screwed things up.

  Don't get me started on why I have that piece of crap installed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
  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
  Date: Mon Oct 22 21:04:01 2018
  ErrorMessage: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  HibernationDevice: RESUME=UUID=7c76546e-c678-42c7-8cc2-d46d1228cb45
  InstallationDate: Installed on 2018-09-24 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20L9CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root 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-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET30W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET30W(1.16):bd09/20/2018:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T

[Kernel-packages] [Bug 1799277] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (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/1799277

Title:
  package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: kan ikke åbne
  '/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko
  .dpkg-new': Operationen er ikke tilladt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm pretty sure it was Sophos Antivirus that screwed things up.

  Don't get me started on why I have that piece of crap installed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
  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
  Date: Mon Oct 22 21:04:01 2018
  ErrorMessage: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  HibernationDevice: RESUME=UUID=7c76546e-c678-42c7-8cc2-d46d1228cb45
  InstallationDate: Installed on 2018-09-24 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20L9CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root 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-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: kan ikke åbne 
'/lib/modules/4.15.0-38-generic/kernel/drivers/input/gameport/lightning.ko.dpkg-new':
 Operationen er ikke tilladt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N27ET30W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET30W(1.16):bd09/20/2018:svnLENOVO:pn20L9CTO1WW:pvrThinkPadT580:rvnLENOVO:rn20L9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T580
  dmi.product.name: 20L9CTO1WW
  dmi.product.version: ThinkPad T580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1799281] [NEW] [Bionic][Cosmic] ipmi: Fix timer race with module unload

2018-10-22 Thread Manoj Iyer

Public bug reported:

[Impact]
If you attempt to remove and insert the ipmi_ssif module a number of times, it 
would result in a kernel panic. This is due to mod_timer from arming a timer 
that was already removed by del_timer during module unload.

[Fix]
In linux-next:
0711e8c1b457 ipmi: Fix timer race with module unload

[Test]
-- Test Case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done

After the patch was applied, no kernel panics were obsereved. Tested on Cavium 
ThunderX2.

[Regression Risk]
The patch was applied to bionic and tested tested on a Cavium ThunderX2 and no 
regressions were found. Risk of regression none.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Incomplete


** Tags: bionic cavium

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

Title:
  [Bionic][Cosmic]  ipmi: Fix timer race with module unload

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  If you attempt to remove and insert the ipmi_ssif module a number of times, 
it would result in a kernel panic. This is due to mod_timer from arming a timer 
that was already removed by del_timer during module unload.

  [Fix]
  In linux-next:
  0711e8c1b457 ipmi: Fix timer race with module unload

  [Test]
  -- Test Case --
  for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done
  
  After the patch was applied, no kernel panics were obsereved. Tested on 
Cavium ThunderX2.

  [Regression Risk]
  The patch was applied to bionic and tested tested on a Cavium ThunderX2 and 
no regressions were found. Risk of regression none.

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

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

[Kernel-packages] [Bug 1799276] [NEW] [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

2018-10-22 Thread Manoj Iyer

Public bug reported:

[Impact]
The IPMI spec states:

The purpose of the SPMI Table is to provide a mechanism that can be used
by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management” essentially meaning an ACPI-aware OS
or OS loader) very early in the boot process, e.g., before the ability
to execute ACPI control methods in the OS is available.

When we are probing IPMI in Linux, ACPI control methods are available,
so we shouldn't be probing using SPMI. It could cause some confusion
during the probing process.

[Fix]
Fixed upstream in 4.17:
commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
Author: Corey Minyard 
Date: Thu Mar 8 15:00:28 2018 -0600

ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

[Test]
-- Test case --
for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done
--

-- Before Applying the patch --
Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new BMC 
(man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of 
dmi-ipmi-ssif.1 failed with error -17

-- With patch applied --
Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying 
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave 
address 0x20
Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new BMC 
(man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)

[Regression Potential]
This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium ThunderX2 
platform and no regressions were found.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New


** Tags: cavium

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

Title:
  [Bionic] ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  The IPMI spec states:

  The purpose of the SPMI Table is to provide a mechanism that can be
  used by the OSPM (an ACPI term for “OS Operating System-directed
  configuration and Power Management” essentially meaning an ACPI-aware
  OS or OS loader) very early in the boot process, e.g., before the
  ability to execute ACPI control methods in the OS is available.

  When we are probing IPMI in Linux, ACPI control methods are available,
  so we shouldn't be probing using SPMI. It could cause some confusion
  during the probing process.

  [Fix]
  Fixed upstream in 4.17:
  commit 4866b1dce0389013a268f0ab63f7229b30c6e5fe
  Author: Corey Minyard 
  Date: Thu Mar 8 15:00:28 2018 -0600

  ipmi: Remove ACPI SPMI probing from the SSIF (I2C) driver

  [Test]
  -- Test case --
  for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ; sudo modprobe 
ipmi_ssif || exit; done
  --

  -- Before Applying the patch --
  Jun 19 18:53:04 starbuck kernel: [ 126.351580] ipmi_ssif 0-000e: Found new 
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)
  Jun 19 18:53:06 starbuck kernel: [ 128.725391] ipmi_ssif: probe of 
dmi-ipmi-ssif.1 failed with error -17

  -- With patch applied --
  Oct 19 19:59:49 starbuck kernel: [ 1501.699109] IPMI SSIF Interface driver
  Oct 19 19:59:49 starbuck kernel: [ 1501.730439] ipmi_ssif: Trying 
SMBIOS-specified SSIF interface at i2c address 0xe, adapter xlp9xx-i2c, slave 
address 0x20
  Oct 19 19:59:49 starbuck kernel: [ 1501.862509] ipmi_ssif 0-000e: Found new 
BMC (man_id: 0x00, prod_id: 0x0202, dev_id: 0x20)

  [Regression Potential]
  This patch applies to ipmi_ssif driver and was tested on ARM64 Cavium 
ThunderX2 platform and no regressions were found.

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

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

[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

2018-10-22 Thread Frank Heimes

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

** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1797367

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Athira Rajeev 
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.
   
  Contact Information = Athira Rajeev , Waiki Wright < 
wa...@us.ibm.com > 
   
  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39
   
  Machine Type = This issue is observed on z13 system 
   ---Debugger---
  A debugger was configured, 
   
  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72 
  dump was configured and crash dump is available. 
  Results of few crash commands like bt, log are added in Attachment 

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)
0037cc98: e320d004lg  
%r2,0(%r13)
0037cc9e: ecc2001a4065clgrj   
%r12,%r2,4,37ccd2
0037cca4: b9040013lgr 
%r1,%r3
0037cca8: ec31ff868064cgrj
%r3,%r1,8,37cbb4
  [14746.977458] Call Trace:
  [14746.977460] ([<0037cc8e>] __check_object_size+0x156/0x1e0)
  [14746.977462]  [<0010ac40>] debug_output+0x150/0x2f8
  [14746.977464]  [<004e02c0>] full_proxy_read+0x80/0xe0
  [14746.977466]  [<00382592>] vfs_read+0x8a/0x150
  [14746.977467]  [<00382b2e>] SyS_read+0x66/0xe0
  [14746.977469]  [<008e3c94>] system_call+0xd8/0x2c8
  [14746.977470] Last Breaking-Event-Address:
  [14746.977472]  [<0037cc8e>] __check_object_size+0x156/0x1e0
  [14746.977473]
  <<>>

  Adding one more occurrence of panic_on_oops below which appears to correlate 
to above .
   
  Stack trace output:
  Available traces added below
   
  Oops output:
   [ 2140.467261] 8021q: adding VLAN 0 to HW filter on device bond0
  [ 2140.467979] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
  [ 2140.471609] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
  [ 2140.471610] 8021q: adding VLAN 0 to HW filter on device bond0
  [ 2140.472797] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
  [ 2143.278986] Unable to handle kernel pointer der

[Kernel-packages] [Bug 1791953] Re: Xenial update to 4.4.146 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1788222] Re: Bugfix for handling of shadow doorbell buffer

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792340] Re: Xenial update to 4.4.151 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1793430] Re: Page leaking in cachefiles_read_backing_file while vmscan is active

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1793461] Re: Improvements to the kernel source package preparation

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792044] Re: update ENA driver to latest mainline version

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792109] Re: Xenial update to 4.4.147 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792383] Re: Xenial update to 4.4.153 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792310] Re: Xenial update to 4.4.149 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792174] Re: Xenial update to 4.4.148 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792392] Re: Xenial update to 4.4.154 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792419] Re: Xenial update to 4.4.155 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1792377] Re: Xenial update to 4.4.152 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 22. October 2018 16:37 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 22. October 2018 16:37 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux: 4.15.0-38.41 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 
(linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 
1797082 (linux-azure)
  derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 
(linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 
(linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions

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

[Kernel-packages] [Bug 1793841] Re: IP_SET modules not included in kernel build, prevents container functionality

This bug was fixed in the package linux-kvm - 4.15.0-1025.25

---
linux-kvm (4.15.0-1025.25) bionic; urgency=medium

  * linux-kvm: 4.15.0-1025.25 -proposed tracker (LP: #1797065)

  [ Ubuntu: 4.15.0-38.41 ]

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux-kvm (4.15.0-1024.24) bionic; urgency=medium

  * linux-kvm: 4.15.0-1024.24 -proposed tracker (LP: #1795572)

  * kvm kernel missing nbd module (LP: #1793976)
- kvm: [Config] enable BLK_DEV_NBD

  * IP_SET modules not included in kernel build, prevents container
functionality (LP: #1793841)
- kvm: [Config] enable IP_SET_* modules

  [ Ubuntu: 4.15.0-37.40 ]

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)
  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K
  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel
  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw
  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function
  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()
  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw
  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout
  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length
  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume
  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests
  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer
  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72
  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver
  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()
  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF
  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex
  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active
  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces
  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4
  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume
  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA
  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
-

[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer

2018-10-22 Thread Sasikumar

Yes , It seems that bug is still not fixed

FYI - We also observed page fault in 4.18 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/1795453

Title:
  IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  
  Here is the data we captured in our driver (Printed the SGE details which was 
sent by OS)

  sgl_ptr->Address = f000 
  [14547.313240] 
  sgl_ptr->Length = 1000 
  [14547.313241] 
  sge_count = 18 
  [14547.313242] 
  cmd->index = 9d9

  
  Note : This issue is observed only when virtualization is enabled 

  Product : Broadcom (LSI) Megaraid H840 controller
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  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 R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  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 R7415
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64

[Kernel-packages] [Bug 1795582] Re: linux: 4.4.0-138.164 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial)
  derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 
(linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Monday, 22. October 2018 16:39 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial)
  derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 
(linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Monday, 22. October 2018 16:39 UTC

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

Title:
  linux: 4.4.0-138.164 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial)
  derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 
(linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795582/+subscriptions

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

[Kernel-packages] [Bug 1792336] Re: Xenial update to 4.4.150 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1793086] Re: qeth: use vzalloc for QUERY OAT buffer

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by regression introduced by commit 287922eb0b18

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 22. October 2018 18:00 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 22. October 2018 18:00 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp: 4.15.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions

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

[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

2018-10-22 Thread Stefan Bader

So with the script we are able to re-create the panic on one of our
systems. Which is good because I was not yet able to extract anything
from the uploaded dump (using makedumpfile to convert from kdump_flat
format seems to fail finding an end marker).

Generally from the data seen so far all point to a race between
disabling a qeth device and accessing debugfs. Since tear down of
network device structures is handled asynchronously there is a chance
that this might be racing with the access to debug data. This is
something that is generally known to upstream but did not receive that
much attention either. Access to debugfs should be rather limited to, as
its name indicates, debug use.

In that light, the question is whether this really should be treated
release critical. Trying to get this race free might turn into a bigger
task and at the same time should not be something any customer should
run into during normal operation.

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

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - Athira Rajeev 
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.
   
  Contact Information = Athira Rajeev , Waiki Wright < 
wa...@us.ibm.com > 
   
  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39
   
  Machine Type = This issue is observed on z13 system 
   ---Debugger---
  A debugger was configured, 
   
  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72 
  dump was configured and crash dump is available. 
  Results of few crash commands like bt, log are added in Attachment 

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)
0037cc98: e320d004lg  
%r2,0(%r13)
0037cc9e: ecc2001a4065clgrj   
%r12,%r2,4,37ccd2
0037cca4: b9040013lgr 
%r1,%r3
0037cca8: ec31ff868064cgrj
%r3,%r1,8,37cbb4
  [14746.977458] Call Trace:
  [14746.977460] ([<0037cc8e>] __check_object_size+0x156/0x1e0)
  [14746.977462]  [<0010ac40>] debug_output+0x150/0x2f8
  [14746.977464]  [<004e02c0>] full_proxy_read+0x80/0xe0
  [14746.977466]  [<00382592>] vfs_read+0x8a/0x150
  [14746.977467]  [<00382

[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Monday, 22. October 2018 16:40 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Monday, 22. October 2018 16:40 UTC

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

Title:
  linux-aws: 4.4.0-1032.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795582
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795583/+subscriptions

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

[Kernel-packages] [Bug 1791942] Re: Xenial update to 4.4.145 stable release

This bug was fixed in the package linux - 4.4.0-138.164

---
linux (4.4.0-138.164) xenial; urgency=medium

  * linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)

  * Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump registration fails

  * Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18 (LP: #1791790)
- block: Fix a race between blk_cleanup_queue() and timeout handling

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * Bugfix for handling of shadow doorbell buffer (LP: #1788222)
- nvme-pci: add a memory barrier to nvme_dbbuf_update_and_check_event

  * Xenial update to 4.4.155 stable release (LP: #1792419)
- net: 6lowpan: fix reserved space for single frames
- net: mac802154: tx: expand tailroom if necessary
- 9p/net: Fix zero-copy path in the 9p virtio transport
- net: lan78xx: Fix misplaced tasklet_schedule() call
- spi: davinci: fix a NULL pointer dereference
- drm/i915/userptr: reject zero user_size
- powerpc/fadump: handle crash memory ranges array index overflow
- powerpc/pseries: Fix endianness while restoring of r3 in MCE handler.
- fs/9p/xattr.c: catch the error of p9_client_clunk when setting xattr 
failed
- 9p/virtio: fix off-by-one error in sg list bounds check
- net/9p/client.c: version pointer uninitialized
- net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
  kfree()
- dm cache metadata: save in-core policy_hint_size to on-disk superblock
- iio: ad9523: Fix displayed phase
- iio: ad9523: Fix return value for ad952x_store()
- vmw_balloon: fix inflation of 64-bit GFNs
- vmw_balloon: do not use 2MB without batching
- vmw_balloon: VMCI_DOORBELL_SET does not check status
- vmw_balloon: fix VMCI use when balloon built into kernel
- tracing: Do not call start/stop() functions when tracing_on does not 
change
- tracing/blktrace: Fix to allow setting same value
- kthread, tracing: Don't expose half-written comm when creating kthreads
- uprobes: Use synchronize_rcu() not synchronize_sched()
- 9p: fix multiple NULL-pointer-dereferences
- PM / sleep: wakeup: Fix build error caused by missing SRCU support
- pnfs/blocklayout: off by one in bl_map_stripe()
- ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
- mm/tlb: Remove tlb_remove_table() non-concurrent condition
- iommu/vt-d: Add definitions for PFSID
- iommu/vt-d: Fix dev iotlb pfsid use
- osf_getdomainname(): use copy_to_user()
- sys: don't hold uts_sem while accessing userspace memory
- userns: move user access out of the mutex
- ubifs: Fix memory leak in lprobs self-check
- Revert "UBIFS: Fix potential integer overflow in allocation"
- ubifs: Check data node size before truncate
- ubifs: Fix synced_i_size calculation for xattr inodes
- pwm: tiehrpwm: Fix disabling of output of PWMs
- fb: fix lost console when the user unplugs a USB adapter
- udlfb: set optimal write delay
- getxattr: use correct xattr length
- bcache: release dc->writeback_lock properly in bch_writeback_thread()
- perf auxtrace: Fix queue resize
- fs/quota: Fix spectre gadget in do_quotactl
- x86/io: add interface to reserve io memtype for a resource range. (v1.1)
- drm/drivers: add support for using the arch wc mapping API.
- Linux 4.4.155

  * Xenial update to 4.4.154 stable release (LP: #1792392)
- sched/sysctl: Check user input value of sysctl_sched_time_avg
- Cipso: cipso_v4_optptr enter infinite loop
- vti6: fix PMTU caching and reporting on xmit
- xfrm: fix missing dst_release() after policy blocking lbcast and multicast
- xfrm: free skb if nlsk pointer is NULL
- mac80211: add stations tied to AP_VLANs during hw reconfig
- nl80211: Add a missing break in parse_station_flags
- drm/bridge: adv7511: Reset registers on hotplug
- scsi: libiscsi: fix possible NULL pointer dereference in case of TMF
- drm/imx: imx-ldb: disable LDB on driver bind
- drm/imx: imx-ldb: check if channel is enabled before printing warning
- usb: gadget: r8a66597: Fix two possible sleep-in-atomic-context bugs in
  init_controller()
- usb: gadget: r8a66597: Fix a possible sleep-in-atomic-context bugs in
  r8a66597_queue()
- usb/phy: fix PPC64 build errors in phy-fsl-usb.c
- tools: usb: ffs-test: Fix build on big endian systems
- usb: gadget: f_uac2: fix endianness of 'struct cntrl_*_lay3'
- tools/power turbostat: fix -S on UP systems
- net: caif: Add a missing rcu_read_unlock() in caif_flow_cb
- qed: Fix possible race for the link state value.

[Kernel-packages] [Bug 1799252] [NEW] Cursor jumping randomly

2018-10-22 Thread Dipjyoti Ghosh

Public bug reported:

Hi,

I am on Ubuntu 16.04 and kernel version 4.4.0-137.
I am facing issue with the cursor going haywire while typing.
What could be possible fix for the same?


VERSION :
lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04


Thanks

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


** Tags: cursor keyboard

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

Title:
  Cursor jumping randomly

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I am on Ubuntu 16.04 and kernel version 4.4.0-137.
  I am facing issue with the cursor going haywire while typing.
  What could be possible fix for the same?

  
  VERSION :
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  
  Thanks

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

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

[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there

2018-10-22 Thread Peter Brandon

The issue began after a fresh system install on a new computer.
Admittedly, the first system I installed was Qubes, with Fedora (24 I
believe).  When I decided Qubes wasn't adequate for my needs, I wiped
the system (reformatted using gparted) and installed the latest Ubuntu
(as of a month ago).  The kworker process was out of control in both
Fedora and Ubuntu.

I have tried kernels 16, 17, and 18, latest as of about a week ago.  16
is no different than my current 15 (4.15).  17 and 18 show a 5% decrease
in the kworker process.  I haven't tried 4.19-rc8 yet because I thought
rc was too rough for testing, but I'll try it on next boot.  Am not
hopeful that the problem is fixed.  And, even if it is fixed in 4.19,
that may not do me much good.  I need virtualbox but I doubt it would
run in 4.19.  Plus I imagine there are more security vulnerabilities and
compatibility issues with mainline testing kernels.  It will probably
take months to years for 18.04 to be using 4.19.  Just a thought

Best wishes,
Peter

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

Title:
  kworker process starts at 85% of cpu and stays there

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu starts, w/ /sbin/init, a kworker process that never stops
  running below 85%:

  pb@pb-tower:~/Downloads$ ps -elf
  F S UIDPID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY  TIME CMD
  4 S root 1 0  0  80   0 - 56471 -  18:30 ?00:00:01 
/sbin/init splash
  1 S root 2 0  0  80   0 - 0 -  18:30 ?00:00:00 
[kthreadd]

  1 R root85 2 63  80   0 - 0 -  18:30 ?
  00:03:03 [kworker/0:1+kac]

  
  After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of 
millions of interrupts.

  The following command line stops the kworker process:
  echo "disable" > /sys/firmware/acpi/interrupts/gpe6F

  On the other hand, I haven't been able to properly shut down my system
  after this command (power never goes off except manually).

  I believe the bug is related to the one discussed here:
  https://superuser.com/questions/1117992/acpi-exception-ae-not-found-
  while-evaluating-gpe-method-floods-syslog

  The dmesg w/ this report may be somewhat confusing because there is an
  unsigned module.  But w/ the module removed, dmesg gives the
  following:

  [0.097480] ACPI: Dynamic OEM Table Load:
  [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef  ApHwp
3000 INTL 20160527)
  [0.097480] ACPI: Executed 1 blocks of module-level executable AML code
  [0.100180] ACPI: Dynamic OEM Table Load:
  [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef  ApCst
3000 INTL 20160527)
  [0.100473] ACPI: Executed 1 blocks of module-level executable AML code
  [0.102187] ACPI: Interpreter enabled
  [0.10] ACPI: (supports S0 S3 S4 S5)
  [0.102223] ACPI: Using IOAPIC for interrupt routing
  [0.102275] HEST: Table parsing has been initialized.
  [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug
  [0.103580] ACPI: GPE 0x20 active on init
  [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) 
[GenericSerialBus] (20170831/evregion-166)
  [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20170831/exfldio-299)
  [0.104040] 
 Initialized Local Variables for Method [PAS1]:
  [0.104041]   Local0: (ptrval)Integer 
0001
  [0.104045] No Arguments are initialized for method [PAS1]
  [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, 
AE_NOT_EXIST (20170831/psparse-550)
  [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, 
AE_NOT_EXIST (20170831/psparse-550)
  [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method 
[_L20] (20170831/evgpe-646)
  [0.104005] ACPI: GPE 0x6F active on init
  [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F
  [0.212126] ACPI: Power Resource [USBC] (on)

  
  [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot
  [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320
  [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff]
  [0.444278] pci :06:00.1: supports D1 D2
  [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot
  [0.444278] pci :05:00.0: PCI bridge to [bus 06]
  [0.444278] pci :05:00.0:   bridge window [mem 0xa200-0xa20f]
  [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0
  [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1
  [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0
  [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1
  [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1
  [0.456183] A

[Kernel-packages] [Bug 1795595] Re: linux: 3.13.0-161.211 -proposed tracker

This bug was fixed in the package linux - 3.13.0-161.211

---
linux (3.13.0-161.211) trusty; urgency=medium

  * linux: 3.13.0-161.211 -proposed tracker (LP: #1795595)

  * CVE-2017-0794
- scsi: sg: protect accesses to 'reserved' page array
- scsi: sg: reset 'res_in_use' after unlinking reserved array
- scsi: sg: recheck MMAP_IO request length with lock held

  * CVE-2017-15299
- KEYS: don't let add_key() update an uninstantiated key

  * CVE-2015-8539
- KEYS: Fix handling of stored error in a negatively instantiated user key

  * CVE-2018-7566
- ALSA: seq: Fix racy pool initializations
- ALSA: seq: More protection for concurrent write and ioctl races

  * CVE-2018-104. // CVE-2018-7566
- ALSA: seq: Don't allow resizing pool in use

  * CVE-2018-104
- ALSA: seq: Make ioctls race-free

  * CVE-2017-18216
- ocfs2: subsystem.su_mutex is required while accessing the item->ci_parent

  * CVE-2016-7913
- tuner-xc2028: Don't try to sleep twice
- xc2028: avoid use after free
- xc2028: unlock on error in xc2028_set_config()
- xc2028: Fix use-after-free bug properly

  * The VM hang happens because of pending interrupts not reinjected when
migrating the VM several times (LP: #1791286)
- KVM: ioapic: merge ioapic_deliver into ioapic_service
- KVM: ioapic: clear IRR for edge-triggered interrupts at delivery
- KVM: ioapic: extract body of kvm_ioapic_set_irq
- KVM: ioapic: reinject pending interrupts on KVM_SET_IRQCHIP

  * CVE-2018-5390
- SAUCE: tcp: Correct the backport of the CVE-2018-5390 fix

  * CVE-2018-9518
- NFC: llcp: Limit size of SDP URI

  * Improvements to the kernel source package preparation (LP: #1793461)
- [Packaging] startnewrelease: add support for backport kernels

 -- Stefan Bader   Wed, 03 Oct 2018 16:41:42
+0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-8539

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-7913

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-0794

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15299

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18216

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-104

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-5390

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7566

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-9518

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

Title:
  linux: 3.13.0-161.211 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1795596 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795595/+subscriptions

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

[Kernel-packages] [Bug 1795595] Re: linux: 3.13.0-161.211 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1795596 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Monday, 22. October 2018 16:05 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1795596 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Monday, 22. October 2018 16:05 UTC

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

Title:
  linux: 3.13.0-161.211 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1795596 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795595/+subscriptions

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

[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

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

Title:
  linux-kvm: 4.15.0-1025.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797065/+subscriptions

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

[Kernel-packages] [Bug 1795596] Re: linux-lts-trusty: 3.13.0-161.211~precise1 -proposed tracker

2018-10-22 Thread Steve Langasek

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

Title:
  linux-lts-trusty: 3.13.0-161.211~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1795595
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795596/+subscriptions

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

[Kernel-packages] [Bug 1791569] Re: some nvidia p1000 graphic cards hang during the boot

This bug was fixed in the package linux - 4.15.0-38.41

---
linux (4.15.0-38.41) bionic; urgency=medium

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)

  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux (4.15.0-37.40) bionic; urgency=medium

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)

  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K

  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel

  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw

  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function

  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()

  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw

  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout

  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver

  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()

  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF

  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces

  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA

  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s390/smsgiucv: disable SMSG on module unload
- isofs: fix potential memory leak in mount option parsing
- MIPS: dts: Boston: Fix PCI bus dtc warnings:
- spi: sh-msiof: Fix bit field overflow writes to TSCR/RSCR
- doc: Add vendor prefix for Kieback & Peter GmbH
- dt-bindings: pi

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

2018-10-22 Thread Chris Gregan

@jsalsbury We are still seeing the issue, given ridsaim has not replied
lets move forward. I'd like to get some movement on this issue without
marking as a Field Critical

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

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

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001

[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker

This bug was fixed in the package linux-gcp - 4.15.0-1023.24

---
linux-gcp (4.15.0-1023.24) bionic; urgency=medium

  * linux-gcp: 4.15.0-1023.24 -proposed tracker (LP: #1797062)

  [ Ubuntu: 4.15.0-38.41 ]

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux-gcp (4.15.0-1022.23) bionic; urgency=medium

  * linux-gcp: 4.15.0-1022.23 -proposed tracker (LP: #1795571)

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- [Config] Unset CONFIG_DELL_UART_BACKLIGHT

  [ Ubuntu: 4.15.0-37.40 ]

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)
  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K
  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel
  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw
  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function
  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()
  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw
  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout
  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length
  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume
  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests
  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer
  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72
  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver
  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()
  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF
  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex
  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active
  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces
  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4
  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume
  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA
  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s

[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 22. October 2018 17:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 22. October 2018 17:31 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-aws: 4.15.0-1025.25 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions

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

[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 22. October 2018 17:33 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 22. October 2018 17:33 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1797061
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797080/+subscriptions

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

[Kernel-packages] [Bug 1795578] Re: linux-gcp: 4.15.0-1022.23~16.04.1 -proposed tracker

*** This bug is a duplicate of bug 1797080 ***
https://bugs.launchpad.net/bugs/1797080

This bug was fixed in the package linux-gcp - 4.15.0-1023.24~16.04.1

---
linux-gcp (4.15.0-1023.24~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker (LP: #1797080)

  [ Ubuntu: 4.15.0-38.41 ]

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux-gcp (4.15.0-1022.23~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1022.23~16.04.1 -proposed tracker (LP: #1795578)

  * Improvements to the kernel source package preparation (LP: #1793461)
- Packaging: update-from-master: allow rebase to be skipped

  [ Ubuntu: 4.15.0-37.40 ]

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)
  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K
  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel
  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw
  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function
  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()
  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw
  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout
  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length
  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume
  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests
  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer
  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72
  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver
  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()
  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF
  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex
  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active
  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces
  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4
  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume
  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA
  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switchi

[Kernel-packages] [Bug 1799252] Re: Cursor jumping randomly

2018-10-22 Thread Dipjyoti Ghosh

There may be a possible fix already available so converting this to a
question

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/linux/+question/675460

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

Title:
  Cursor jumping randomly

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I am on Ubuntu 16.04 and kernel version 4.4.0-137.
  I am facing issue with the cursor going haywire while typing.
  What could be possible fix for the same?

  
  VERSION :
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  
  Thanks

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

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

[Kernel-packages] [Bug 1795571] Re: linux-gcp: 4.15.0-1022.23 -proposed tracker

*** This bug is a duplicate of bug 1797062 ***
https://bugs.launchpad.net/bugs/1797062

This bug was fixed in the package linux-gcp - 4.15.0-1023.24

---
linux-gcp (4.15.0-1023.24) bionic; urgency=medium

  * linux-gcp: 4.15.0-1023.24 -proposed tracker (LP: #1797062)

  [ Ubuntu: 4.15.0-38.41 ]

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux-gcp (4.15.0-1022.23) bionic; urgency=medium

  * linux-gcp: 4.15.0-1022.23 -proposed tracker (LP: #1795571)

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- [Config] Unset CONFIG_DELL_UART_BACKLIGHT

  [ Ubuntu: 4.15.0-37.40 ]

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)
  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K
  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel
  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw
  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function
  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()
  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw
  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout
  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length
  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume
  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests
  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer
  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72
  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver
  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()
  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF
  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex
  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active
  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces
  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4
  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume
  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA
  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask

[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker

This bug was fixed in the package linux-gcp - 4.15.0-1023.24~16.04.1

---
linux-gcp (4.15.0-1023.24~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker (LP: #1797080)

  [ Ubuntu: 4.15.0-38.41 ]

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux-gcp (4.15.0-1022.23~16.04.1) xenial; urgency=medium

  * linux-gcp: 4.15.0-1022.23~16.04.1 -proposed tracker (LP: #1795578)

  * Improvements to the kernel source package preparation (LP: #1793461)
- Packaging: update-from-master: allow rebase to be skipped

  [ Ubuntu: 4.15.0-37.40 ]

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)
  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K
  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel
  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw
  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function
  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()
  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw
  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout
  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length
  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume
  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests
  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer
  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72
  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver
  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()
  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF
  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex
  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active
  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces
  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4
  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume
  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA
  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
-

[Kernel-packages] [Bug 1796542] Re: Silent data corruption in Linux kernel 4.15

This bug was fixed in the package linux - 4.15.0-38.41

---
linux (4.15.0-38.41) bionic; urgency=medium

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)

  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux (4.15.0-37.40) bionic; urgency=medium

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)

  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K

  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel

  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw

  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function

  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()

  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw

  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout

  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver

  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()

  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF

  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces

  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA

  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s390/smsgiucv: disable SMSG on module unload
- isofs: fix potential memory leak in mount option parsing
- MIPS: dts: Boston: Fix PCI bus dtc warnings:
- spi: sh-msiof: Fix bit field overflow writes to TSCR/RSCR
- doc: Add vendor prefix for Kieback & Peter GmbH
- dt-bindings: pi

[Kernel-packages] [Bug 1793086] Re: qeth: use vzalloc for QUERY OAT buffer

This bug was fixed in the package linux - 4.15.0-38.41

---
linux (4.15.0-38.41) bionic; urgency=medium

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)

  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux (4.15.0-37.40) bionic; urgency=medium

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)

  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K

  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel

  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw

  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function

  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()

  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw

  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout

  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver

  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()

  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF

  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces

  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA

  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s390/smsgiucv: disable SMSG on module unload
- isofs: fix potential memory leak in mount option parsing
- MIPS: dts: Boston: Fix PCI bus dtc warnings:
- spi: sh-msiof: Fix bit field overflow writes to TSCR/RSCR
- doc: Add vendor prefix for Kieback & Peter GmbH
- dt-bindings: pi

[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend

This bug was fixed in the package linux - 4.15.0-38.41

---
linux (4.15.0-38.41) bionic; urgency=medium

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)

  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux (4.15.0-37.40) bionic; urgency=medium

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)

  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K

  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel

  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw

  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function

  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()

  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw

  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout

  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver

  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()

  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF

  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces

  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA

  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s390/smsgiucv: disable SMSG on module unload
- isofs: fix potential memory leak in mount option parsing
- MIPS: dts: Boston: Fix PCI bus dtc warnings:
- spi: sh-msiof: Fix bit field overflow writes to TSCR/RSCR
- doc: Add vendor prefix for Kieback & Peter GmbH
- dt-bindings: pi

[Kernel-packages] [Bug 1793221] Re: hns3: Retrieve RoCE MSI-X config from firmware

This bug was fixed in the package linux - 4.15.0-38.41

---
linux (4.15.0-38.41) bionic; urgency=medium

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)

  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux (4.15.0-37.40) bionic; urgency=medium

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)

  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K

  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel

  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw

  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function

  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()

  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw

  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout

  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver

  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()

  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF

  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces

  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA

  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s390/smsgiucv: disable SMSG on module unload
- isofs: fix potential memory leak in mount option parsing
- MIPS: dts: Boston: Fix PCI bus dtc warnings:
- spi: sh-msiof: Fix bit field overflow writes to TSCR/RSCR
- doc: Add vendor prefix for Kieback & Peter GmbH
- dt-bindings: pi

[Kernel-packages] [Bug 1793338] Re: Fix unusable NVIDIA GPU after S3

This bug was fixed in the package linux - 4.15.0-38.41

---
linux (4.15.0-38.41) bionic; urgency=medium

  * linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)

  * Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
- block: bio_iov_iter_get_pages: fix size of last iovec
- blkdev: __blkdev_direct_IO_simple: fix leak in error case
- block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

linux (4.15.0-37.40) bionic; urgency=medium

  * linux: 4.15.0-37.40 -proposed tracker (LP: #1795564)

  * hns3: enable ethtool rx-vlan-filter on supported hw (LP: #1793394)
- net: hns3: Add vlan filter setting by ethtool command -K

  * hns3: Modifying channel parameters will reset ring parameters back to
defaults (LP: #1793404)
- net: hns3: Fix desc num set to default when setting channel

  * hisi_sas: Add SATA FIX check for v3 hw (LP: #1794151)
- scsi: hisi_sas: Add SATA FIS check for v3 hw

  * Fix potential corruption using SAS controller on HiSilicon arm64 boards
(LP: #1794156)
- scsi: hisi_sas: add memory barrier in task delivery function

  * hisi_sas: Reduce unnecessary spin lock contention (LP: #1794165)
- scsi: hisi_sas: Tidy hisi_sas_task_prep()

  * Add functional level reset support for the SAS controller on HiSilicon D06
systems (LP: #1794166)
- scsi: hisi_sas: tidy host controller reset function a bit
- scsi: hisi_sas: relocate some common code for v3 hw
- scsi: hisi_sas: Implement handlers of PCIe FLR for v3 hw

  * HiSilicon SAS controller doesn't recover from PHY STP link timeout
(LP: #1794172)
- scsi: hisi_sas: tidy channel interrupt handler for v3 hw
- scsi: hisi_sas: Fix the failure of recovering PHY from STP link timeout

  * getxattr: always handle namespaced attributes (LP: #1789746)
- getxattr: use correct xattr length

  * Fix unusable NVIDIA GPU after S3 (LP: #1793338)
- PCI: Reprogram bridge prefetch registers on resume

  * Fails to boot under Xen PV: BUG: unable to handle kernel paging request at
edc21fd9 (LP: #1789118)
- x86/EISA: Don't probe EISA bus for Xen PV guests

  * qeth: use vzalloc for QUERY OAT buffer (LP: #1793086)
- s390/qeth: use vzalloc for QUERY OAT buffer

  * SRU: Enable middle button of touchpad on ThinkPad P72 (LP: #1793463)
- Input: elantech - enable middle button of touchpad on ThinkPad P72

  * Dell new AIO requires a new uart backlight driver (LP: #1727235)
- SAUCE: platform/x86: dell-uart-backlight: new backlight driver for DELL 
AIO
- updateconfigs for Dell UART backlight driver

  * [Ubuntu] s390/crypto: Fix return code checking in cbc_paes_crypt.
(LP: #1794294)
- s390/crypto: Fix return code checking in cbc_paes_crypt()

  * hns3: Retrieve RoCE MSI-X config from firmware (LP: #1793221)
- net: hns3: Fix MSIX allocation issue for VF
- net: hns3: Refine the MSIX allocation for PF

  * net: hns: Avoid hang when link is changed while handling packets
(LP: #1792209)
- net: hns: add the code for cleaning pkt in chip
- net: hns: add netif_carrier_off before change speed and duplex

  * Page leaking in cachefiles_read_backing_file while vmscan is active
(LP: #1793430)
- SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while 
vmscan
  is active

  * some nvidia p1000 graphic cards hang during the boot (LP: #1791569)
- drm/nouveau/gr/gf100-: virtualise tpc_mask + apply fixes from traces

  * Error reported when creating ZFS pool with "-t" option, despite successful
pool creation (LP: #1769937)
- SAUCE: (noup) Update zfs to 0.7.5-1ubuntu16.4

  * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309)
- HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen
- HID: i2c-hid: Don't reset device upon system resume

  * ipmmu is always registered (LP: #1783746)
- iommu/ipmmu-vmsa: Don't register as BUS IOMMU if machine doesn't have 
IPMMU-
  VMSA

  * Bionic update: upstream stable patchset 2018-09-27 (LP: #1794889)
- clocksource/drivers/imx-tpm: Correct some registers operation flow
- Input: synaptics-rmi4 - fix an unchecked out of memory error path
- KVM: X86: fix incorrect reference of trace_kvm_pi_irte_update
- x86: Add check for APIC access address for vmentry of L2 guests
- MIPS: io: Prevent compiler reordering writeX()
- nfp: ignore signals when communicating with management FW
- perf report: Fix switching to another perf.data file
- fsnotify: fix ignore mask logic in send_to_group()
- MIPS: io: Add barrier after register read in readX()
- s390/smsgiucv: disable SMSG on module unload
- isofs: fix potential memory leak in mount option parsing
- MIPS: dts: Boston: Fix PCI bus dtc warnings:
- spi: sh-msiof: Fix bit field overflow writes to TSCR/RSCR
- doc: Add vendor prefix for Kieback & Peter GmbH
- dt-bindings: pi

[Kernel-packages] [Bug 1793394] Re: hns3: enable ethtool rx-vlan-filter on supported hw