[Kernel-packages] [Bug 1810097] Re: HDMI is not recognized

[Brad Figg]

** Tags added: cscc

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

Title:
  HDMI is not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 598mm x 336mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1440x900  59.89  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 800x600   72.1975.0060.3256.25  
 640x480   75.0072.8159.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)

  with friendly greetings from Germany
  Heinz Köhler

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Dec 30 17:27:38 2018
  DistUpgraded: 2018-08-21 18:00:51,886 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2014-12-09 (1482 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. Z97-HD3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=79c3b9e1-5aa7-47b0-8673-5fc4a350c917 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (131 days ago)
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97-HD3
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 21 14:19:34 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:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810097/+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 1810388] Re: syslog filled with drm messages 40 times per second

[Brad Figg]

** Tags added: cscc

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

Title:
  syslog filled with drm messages 40 times per second

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

Bug description:
  Hi all,

  I don't really know when it exactly began.
  From /var/log/syslog :
  Jan  3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] 
[FB:74]
  Jan  3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] 
[FB:89]

  There are similar bugs that have been already noticed, but none of
  them helped me.

  Changing desktop environment to a non-gnome desktop stops messages.

  My environment (export cmd) :
  declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg"
  declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME"
  declare -x 
XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop"
  declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile"
  declare -x XDG_MENU_PREFIX="gnome-"
  declare -x XDG_RUNTIME_DIR="/run/user/1000"
  declare -x XDG_SEAT="seat0"
  declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0"
  declare -x XDG_SESSION_DESKTOP="ubuntu"
  declare -x XDG_SESSION_ID="c2"
  declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0"
  declare -x XDG_SESSION_TYPE="x11"
  declare -x XDG_VTNR="7"

  My kernel : 4.15.0-43-generic
  Ubuntu 18.04.01 LTS
  Graphic : Intel Haswell Mobile

  Any help is appreciated
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jan  3 09:38:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
   virtualbox, 5.2.18, 4.19.0-041900-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2016-12-20 (743 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. XPS13 9333
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=19d7298f-74c8-4a78-9f17-88b9f04bbc3a ro net.ifnames=0 biosdevname=0 
acpi=force plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810388/+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 1810390] Re: 78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed on B

[Brad Figg]

** Tags added: cscc

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

Title:
  78a017a2c92df9b571db0a55a016280f9019c65e in btrfs_kernel_fixes failed
  on B

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The test failed with file attribute not match,
  for "file", we're expecting:
  "c--- a/file", but lsattr shows:
  "c- a/file"

  for "file2", we're expecting:
  " a/file2", but lsattr shows:
  "-- a/file2"

  for "directory", we're expecting:
  " a", but lsattr shows:
  "-- a"

  
  This patch could be found in the Bionic tree.
  
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=78a017a2c92df9b571db0a55a016280f9019c65e

  So this might be a test case issue.

  fix 78a017a2c92df9b571db0a55a016280f9019c65e

  Btrfs: add missing compression property remove in
  btrfs_ioctl_setflags

  The behaviour of a 'chattr -c' consists of getting the current flags,
  clearing the FS_COMPR_FL bit and then sending the result to the set
  flags ioctl - this means the bit FS_NOCOMP_FL isn't set in the flags
  passed to the ioctl. This results in the compression property not being
  cleared from the inode - it was cleared only if the bit FS_NOCOMP_FL
  was set in the received flags.

  Incorrect attributes on file, got: c- a/file
  Incorrect attributes on file2, got: -- a/file2
  Incorrect attributes on directory, got: -- a

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  3 08:42 seq
   crw-rw 1 root audio 116, 33 Jan  3 08:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  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: Thu Jan  3 08:47:04 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1810390/+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 1787973] Re: Cosmic update to 4.17.17 stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Cosmic update to 4.17.17 stable release

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.17.17 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.17.17 stable release shall be
  applied:

  
  fa535b8a3759 Linux 4.17.17
  a4ae511d8600 x86/speculation/l1tf: Exempt zeroed PTEs from inversion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787973/+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 1788151] Re: ubuntu_ramfs_stress will get killed with Bionic generic kernel on KVM node

[Brad Figg]

** Tags added: cscc

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

Title:
  ubuntu_ramfs_stress will get killed with Bionic generic kernel on KVM
  node

Status in Stress-ng:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  It looks like this issue won't happen with Bionic KVM kernel on KVM nodes.
  Only with Bionic generic kernel on KVM nodes (1G ram)

  Output from syslog indicates this test was killed due to OOM:
  https://pastebin.ubuntu.com/p/wcY4DtDFtT/

   Running 'ls -al /home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress'
   [stdout] total 28
   [stdout] drwxrwxr-x   2 ubuntu ubuntu 4096 Aug 21 11:16 .
   [stdout] drwxrwxr-x 165 ubuntu ubuntu 4096 Aug 21 11:14 ..
   [stdout] -rw-rw-r--   1 ubuntu ubuntu  501 Aug 21 11:14 control
   [stdout] -rw-rw-r--   1 ubuntu ubuntu 2303 Aug 21 11:14 
ubuntu_ramfs_stress.py
   [stdout] -rw-r--r--   1 root   root   2834 Aug 21 11:16 
ubuntu_ramfs_stress.pyc
   [stdout] -rwxrwxr-x   1 ubuntu ubuntu 4169 Aug 21 11:14 
ubuntu_ramfs_stress.sh
   true'
GOODubuntu_ramfs_stress.setup   
ubuntu_ramfs_stress.setup   timestamp=1534850377localtime=Aug 21 
11:19:37   completed successfully
END GOODubuntu_ramfs_stress.setup   
ubuntu_ramfs_stress.setup   timestamp=1534850377localtime=Aug 21 
11:19:37   
   Persistent state client._record_indent now set to 1
   Persistent state client.unexpected_reboot deleted
   Test has timeout: 18000 sec.
START   ubuntu_ramfs_stress.ramfs-stress
ubuntu_ramfs_stress.ramfs-stresstimestamp=1534850377timeout=18000   
localtime=Aug 21 11:19:37   
   Persistent state client._record_indent now set to 2
   Persistent state client.unexpected_reboot now set to 
('ubuntu_ramfs_stress.ramfs-stress', 'ubuntu_ramfs_stress.ramfs-stress')
   Waiting for pid 10774 for 18000 seconds
   Running 'LOG=/tmp/ramfs-falure.log 
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng
 DURATION=15s bash -c 
/home/ubuntu/autotest/client/tests/ubuntu_ramfs_stress/ubuntu_ramfs_stress.sh 
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src 2>&1'
   [stdout] Total of 229376 KB free memory
   [stdout] Making ram disk of 256K
   [stdout]  
   [stdout] 

   [stdout] Stress test:   
/home/ubuntu/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng/stress-ng 
--verify --times --metrics-brief --syslog --keep-name -t 15s --link 4 --symlink 
4 --lockf 4 --seek 4 --aio 4 --aio-requests 32 --dentry 4 --dir 4 --fstat 4 
--io 4 --dentries 4 --lease 4 --mmap-file --mmap-async --open 4 --rename 4 
--chdir 4 --chmod 4 --filename 4 --rename 4 --hdd 4 --hdd-opts 
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --hdd-write-size 512
   [stdout] Mount point:   /mnt/ramfs-test-10779
   [stdout] Date:  Tue Aug 21 11:19:37 UTC 2018
   [stdout] Host:  zeppo
   [stdout] Kernel:4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 
UTC 2018
   [stdout] Machine:   zeppo x86_64 x86_64
   [stdout] CPUs online:   2
   [stdout] CPUs total:2
   [stdout] Page size: 4096
   [stdout] Pages avail:   203847
   [stdout] Pages total:   252219
   [stdout] 

   [stdout]  
   [stdout]  
   [stdout] stress-ng: info:  [10827] dispatching hogs: 4 link, 4 symlink, 4 
lockf, 4 seek, 4 aio, 4 dentry, 4 dir, 4 fstat, 4 io, 4 lease, 4 open, 4 
rename, 4 chdir, 4 chmod, 4 filename, 4 rename, 4 hdd
  Killed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: User Name 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 11:13 seq
   crw-rw 1 root audio 116, 33 Aug 21 11:13 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: Tue Aug 21 11:23:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware   

[Kernel-packages] [Bug 1633223] Re: rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker

[Brad Figg]

** Tags added: cscc

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

Title:
  rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and
  docker

Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 
3.19.0-58. The system is running docker containers, and has the NVIDIA GPU 
driver loaded. We've seen about 4 stalls in the last month, all with the 
3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers.

  ---uname output---
  Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  2 x NVIDIA K80 GPU adapter:
  $ lspci | grep NV
  0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 

   
  Machine Type = 8247-42L 
   
  ---System Hang---
   Usual symptom is that the system is unresponsive except maybe for ping and 
writing the stall-detection messages to the console. Login/getty isn't 
available either via ssh nor on the console. System must be power cycled to 
recover.
   
  Attached is the kernel log from a stall detection on May 18th. The detection 
first occurs at: May 18 15:17:55.

  The system is later rebooted and those messages indicate the kernel
  (3.19.0-58) and NVIDIA driver version (352.93) that were active at the
  time.

  We've suffered 3 or 4 stalls since, all with the same kernel, but some
  with a newer NVIDIA driver (361.49).

  Unfortunately, information about the newer stalls wasn't preserved in
  the various log files (and we're not capturing the console
  constantly), so we don't have detailed data for those.

  We'd welcome any suggestions for how to collect additional data for
  these occurrences.

  I can't say for sure that we haven't seen the stalls on other systems,
  but they're occuring fairly frequently on this system, and it's
  unusual in that it's running both Docker and NVIDIA GPU driver. So
  maybe aufs or the NVIDIA driver are somehow involved.

  From the kern.log,

  The Call trace points to some kind of deadlock in aufs -

  May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3:
  May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R  running 
task0 99183  99173 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] 
[c00cf004] wake_up_worker+0x44/0x60 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] 
[c00fa64675d0] 0xc00fa64675d0
  May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] 
[c00fa6467850] 0xc00fa6467850
  May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75:
  May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 
105d9410 0 99427  99405 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] 
[c017efdd34a0] 0xc017efdd34a0 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] 
[c017efdd3690] 0xc017efdd3690
  May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] 
[c0a1f128] rwsem_down_write_failed+0x288/0x400
  May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] 
[c0a1e538] down_write+0x88/0x90
  May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] 
[d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] 
[d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] 
[d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] 
[c02c88f8] lookup_fast+0x368/0x3b0
  May 18 15:17:55 dldev1 kernel: [713670.798740] [c017efdd3b10] 
[c02cb620] path_lookupat+0x180/0x970
  May 18 15:17:55 dldev1 kernel: [713670.798743] [c017efdd3be0] 
[c02cbe68] filename_lookup+0x58/0x140
  May 18 15:17:55 dldev1 kernel: [713670.798746] [c017efdd3c30] 
[c02cde04] user_path_at_empty+0x84/0xe0
  May 18 15:17:55 dldev1 kernel: [713670.798749] [c017efdd3d20] 
[c02be744] vfs_fstatat+0x84/0x140
  May 18 15:17:55 dldev1 kernel: 

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Brad Figg]

** Tags added: ubuntu-certified

** Tags added: cscc

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

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1632049] Re: PSL data cache should be flushed before resetting CAPI adapter

[Brad Figg]

** Tags added: cscc

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

Title:
  PSL data cache should be flushed before resetting CAPI adapter

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

Bug description:
  ---Problem Description---
  The PSL data cache should be flushed before resetting a CAPI adapter.
  If the PSL data cache holds dirty cache line when it is reset, the host 
trying to access that memory when the link is down may face a Uncorrectable 
Error (UE), forcing a reboot of the system.
   
  ---uname output---
  Linux freak 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  CAPI adapter needed + AFU image using the PSL cache (e.g. afu_directed 
memcpy) 

   
  Machine Type = Tuleta 

  ---Steps to Reproduce---
   There's some randomness to it, but triggering a memcpy test + card reset in 
a loop can produce it:

  memcpy_afu_ctx -p100 -l1000
  echo 1 > /sys/class/cxl/card0/reset
  Fix is already upstream under commit ID:
  aaa2245ed836824f21f8e42e0ab63b1637d1cb20 
  "cxl: Flush PSL cache before resetting the adapter"

  We would like the fix released for both 16.04 and 16.10 please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632049/+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 1629872] Re: ISST-LTE:pNV:cap: Call traces dumping continuously after 10+ hours of regression with Leaf IO and SMT tests with SMT fix

[Brad Figg]

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

** Tags added: cscc

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

Title:
  ISST-LTE:pNV:cap: Call traces dumping continuously after 10+ hours of
  regression with Leaf IO and SMT tests with SMT fix

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

Bug description:
  Description:
  
  Call traces dumping continuously with Leaf IO and SMT tests with SMT fix 
(140718) after 10+ hours of regression run and not able to get the prompt.

  Steps to re-create:
  --
  > cap installed with latest ubuntu160401 kernel ,4.4.0-38-generic.

  > Applied SMT kernel patch on system cap for issue:140718

  root@cap:~# ls -l
  total 56572
  -rw-r--r-- 1 root root 18838772 Sep 22 12:24 
linux-image-4.4.0-21-generic_4.4.0-21.37+smt_ppc64el.deb
  -rw-r--r-- 1 root root 39081588 Sep 22 12:24 
linux-image-extra-4.4.0-21-generic_4.4.0-21.37+smt_ppc64el.deb
  -rw--- 1 root root   70 Sep 21 04:24 nohup.out

  > Booted with above kernel

  root@cap:~# uname -a
  Linux cap 4.4.0-21-generic #37+smt SMP Mon Aug 29 15:07:28 CDT 2016 ppc64le 
ppc64le ppc64le GNU/Linux
  root@cap:~# uname -r
  4.4.0-21-generic

  > Enabled sysrq and also xmon before starting tests

  root@cap:~# cat /proc/sys/kernel/sysrq
  1
  root@cap:~# cat /proc/cmdline
  root=UUID=4114e1ef-5e30-45ae-a5fb-a5429946434c ro xmon=on splash quiet 
crashkernel=384M-:128M

  > root@cap:~/fix_140718# ppc64_cpu --smt
  SMT=8

  > Started tests with Leaf IO and SMT. After 10+ hours of run, ipmi console 
dumping call traces continuously and not able to get the prompt.
 ssh cap is hung, ping cap is working fine 

  [ipjoga@kte ~]$ ssh root@cap

  
  ipjoga@kte ~]$ ping cap
  PING cap.isst.aus.stglabs.ibm.com (10.33.17.16) 56(84) bytes of data.
  64 bytes from cap.isst.aus.stglabs.ibm.com (10.33.17.16): icmp_seq=1 ttl=64 
time=0.095 ms
  64 bytes from cap.isst.aus.stglabs.ibm.com (10.33.17.16): icmp_seq=2 ttl=64 
time=0.055 ms
  ^C
   
  > Attached Call traces 

  > Also memory in this system is

  oot@cap:/kte/tools/setup.d# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   1.0T4.4G1.0T 37M9.4G
1.0T
  Swap:   37G  0B 37G
  root@cap:/kte/tools/setup.d# 

  
  UBUNTU  BUILD: 4.4.0-38-generic

  SL Firmware Version :  IBM-garrison-ibm-OP8_v1.10_2.17

  IO team thinks this is related/fixed by commit 135e8c9250dd
  ("sched/core: Fix a race between try_to_wake_up() and a woken up
  task").We built a kernel with that patch applied and asked indira
  to restart the tests.

  Developer provided the fix for above issue . Applied it and restarted
  Leaf IO and SMT tests which has both SMT fix and Memory barrier fix.

  root@cap:~# uname -r
  4.4.0-38.58+ibm-smt1-generic

  Run went fine for more than 60+ hours without any system hang.

  Canonical, we believe the following issue to be fixed by:

  commit 135e8c9250dd ("sched/core: Fix a race between try_to_wake_up()
  and a woken up task")

  Which was marked to the -stable tree.  Can you pull it into your
  kernel?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629872/+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 1628238] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!

[Brad Figg]

** Tags added: cscc

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

Title:
  uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not
  initialized!

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

Bug description:
  [5.525445] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
  [5.525452] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was 
not initialized!
  [5.525456] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2084 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 15:21:42 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1628238/+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 1790457] Re: kernel: improve spectre mitigation

[Brad Figg]

** Tags added: cscc

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

Title:
  kernel: improve spectre mitigation

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * eToken Facility will help to mitigate spectre.
 With it in place use of expolines can be ommitted.

 Kernel
  
https://github.com/torvalds/linux/commit/aeaf7002a76c8da60c0f503badcbddc07650678c

 KVM to pass it to guests:
  https://patchwork.kernel.org/patch/10532197/

   * Backport the changes to Qemu/Kernel so that the impact of the spectre 
 fixes can be minimized.

  [Test Case]

   * First of all you need HW with the facility available.
 For HW without nothing should change at all, well maybe a message that 
 it wasn't detected when the new kernel boots.
   
   * When running on HW with the Facility and a fixed kernel then the 
 facility should be reported as being available.

   * With a fixed Kernel AND Qemu this facility should be passed to the 
 guest so that it can benefit from the improvements as well.

   * Due to a lack of such HW IBM volunteered to do the verification on 
 this bug.

  [Regression Potential]

   * Detection and passing of a Facility is nothing new, s390x has plenty of 
 them and this is in some sense "just one more" so regressions should be 
 minimal. The one thing we thought about was how an enabled Kernel/qemu 
 would behave on systems that do not have the facility, but in all tests 
 that was correctly detected and continues to use expoline.

  [Other Info]
   
   * n/a

  ---

  Description will follow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790457/+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 1790188] Re: Bionic update: upstream stable patchset 2018-08-31

[Brad Figg]

** Tags added: cscc

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

Title:
  Bionic update: upstream stable patchset 2018-08-31

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2018-08-31 (ported from v4.14.50 and v4.16.16)
     from git://git.kernel.org/

  usb: gadget: udc: renesas_usb3: should fail if devm_phy_get() returns error
  usb: gadget: udc: renesas_usb3: should call devm_phy_get() before add udc
  usb: gadget: udc: renesas_usb3: should call pm_runtime_enable() before add udc
  usb: gadget: udc: renesas_usb3: should remove debugfs
  usb: gadget: udc: renesas_usb3: fix double phy_put()
  usb: typec: wcove: Remove dependency on HW FSM
  crypto: omap-sham - fix memleak
  crypto: vmx - Remove overly verbose printk from AES XTS init
  crypto: vmx - Remove overly verbose printk from AES init routines
  crypto: caam - fix size of RSA prime factor q
  crypto: caam/qi - fix IV DMA mapping and updating
  crypto: caam - fix IV DMA mapping and updating
  crypto: caam - fix DMA mapping dir for generated IV
  crypto: caam - strip input zeros from RSA input buffer
  Input: goodix - add new ACPI id for GPD Win 2 touch screen
  kvm: x86: use correct privilege level for sgdt/sidt/fxsave/fxrstor access
  tty: pl011: Avoid spuriously stuck-off interrupts
  vmw_balloon: fixing double free when batching mode is off
  serial: 8250: omap: Fix idling of clocks for unused uarts
  serial: samsung: fix maxburst parameter for DMA transactions
  tty/serial: atmel: use port->name as name in request_irq()
  serial: sh-sci: Stop using printk format %pCr
  usb: gadget: udc: renesas_usb3: disable the controller's irqs for reconnecting
  usb: gadget: function: printer: avoid wrong list handling in printer_write()
  phy: qcom-qusb2: Fix crash if nvmem cell not specified
  Input: xpad - add GPD Win 2 Controller USB IDs
  usb-storage: Add compatibility quirk flags for G-Technologies G-Drive
  usb-storage: Add support for FL_ALWAYS_SYNC flag in the UAS driver
  usbip: vhci_sysfs: fix potential Spectre v1
  NFC: pn533: don't send USB data off of the stack
  staging: android: ion: Switch to pr_warn_once in ion_buffer_destroy
  KVM: x86: pass kvm_vcpu to kvm_read_guest_virt and kvm_write_guest_virt_system
  KVM: x86: introduce linear_{read,write}_system
  KVM: X86: Fix reserved bits check for MOV to CR3
  gpio: No NULL owner
  af_key: Always verify length of provided sadb_key
  blkdev_report_zones_ioctl(): Use vmalloc() to allocate large buffers
  netfilter: nf_tables: fix NULL pointer dereference on nft_ct_helper_obj_dump()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790188/+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 1790521] Re: lxd 3.0.2-0ubuntu3 ADT test failure with linux 4.18.0-7.8

[Brad Figg]

** Tags added: cscc

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

Title:
  lxd 3.0.2-0ubuntu3 ADT test failure with linux 4.18.0-7.8

Status in linux package in Ubuntu:
  Invalid
Status in lxd package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in lxd source package in Cosmic:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/lxd/20180831_072844_6ea94@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/arm64/l/lxd/20180831_074034_6ea94@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/l/lxd/20180831_073216_6ea94@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/lxd/20180831_072127_6ea94@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/s390x/l/lxd/20180831_072401_6ea94@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790521/+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 1789984] Re: Ignore this bug

[Brad Figg]

** Tags added: cscc

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

Title:
  Ignore this bug

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-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed 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 snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  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: bug 1789992 (linux-azure), bug 1789993 (linux-azure), bug 1789994 
(linux-azure-edge), bug 1789996 (linux-gcp), bug 1789997 (linux-hwe), bug 
178 (linux-hwe-edge)
  derivatives: bug 1789985 (linux-raspi2), bug 1789986 (linux-oem), bug 1789987 
(linux-aws), bug 1789988 (linux-azure), bug 1789989 (linux-gcp), bug 1789990 
(linux-kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789984/+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 1790244] Re: Ubuntu dots won't stop appearing/blank screen when unsuspending

[Brad Figg]

** Tags added: cscc

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

Title:
  Ubuntu dots won't stop appearing/blank screen when unsuspending

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

Bug description:
  I have two persistent problems that I haven't been able to resolve with 
Ubuntu 18.04:
  1) the Ubuntu splash screen "dots" that turn white then red then white again 
don't stop appearing after I've booted up and even after I logged in.  They 
keep appearing as I try to do stuff.  They don't seem to stop anything from 
working, but they sure are annoying.
  2) when I unsuspend my computer, it wakes up based on the disk etc. LEDs but 
the monitor screen remains black.  I know my machine supports suspend because 
it worked under 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Aug 31 17:31:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] 
(rev 04) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82915G/GV/910GL Integrated Graphics 
Controller [103c:300c]
  InstallationDate: Installed on 2016-12-03 (636 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Compaq dc5100 MT(PZ583UA)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=c8c2f5c1-ae82-41ac-bd05-9f22b78dbead ro nomodeset=1 vesafb.invalid=1 
mem_sleep_default=deep nomodeset=1 plymouth:debug=1 quiet splash 
vesafb.invalid=1 mem_sleep_default=deep vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786C2 v01.09
  dmi.board.name: 09E0h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL54202Q2
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786C2v01.09:bd08/06/2008:svnHewlett-Packard:pnHPCompaqdc5100MT(PZ583UA):pvr:rvnHewlett-Packard:rn09E0h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc5100 MT(PZ583UA)
  dmi.sys.vendor: Hewlett-Packard
  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 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: Fri Aug 31 17:25:57 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech M525MOUSE, id 8
   inputMicrosoft LifeCam VX-5000: Micr KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  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/linux/+bug/1790244/+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 1790320] Re: system does not recover from hibernation

[Brad Figg]

** Tags added: cscc

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

Title:
  system does not recover from hibernation

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) What you expected to happen

  I walked away from the laptop. The laptop went into sleep mode or
  equivalent.

  4)what should happen is when i move the mouse or type a key or quickly
  press the power button, the machine should come out of sleep mode. It
  does not.

  I have to hard reboot the machine :(

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  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.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Sep  1 19:39:46 2018
  InstallationDate: Installed on 2018-08-24 (8 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790320/+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 1789924] Re: Missing Intel GPU pci-id's

[Brad Figg]

** Tags added: cscc

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Released
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems, if 
possible. Adding new pci-id's is a trivial change which can't regress existing 
hw.

  [Regression potential]
  none, these just add pci-id's and platform definitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1790494] Re: Bug

[Brad Figg]

** Tags added: cscc

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

Title:
  Bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug

  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob3046 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Sep  3 10:27:27 2018
  InstallationDate: Installed on 2018-05-14 (112 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 2349CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=1bbfff25-0936-400c-8302-a421b660c90c ro quiet splash 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: 01/21/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2349CTO:pvrThinkPadT430:rvnLENOVO:rn2349CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790494/+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 1790658] Re: s390/pci: fix out of bounds access during irq setup

[Brad Figg]

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

** Tags added: cscc

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

Title:
  s390/pci: fix out of bounds access during irq setup

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

Bug description:
  == SRU Justification ==

  IBM is requesting this commit (from 4.19) for s390: 
866f3576a72b2233a76dffb80290f8086dc49e17
  It fixes a problem with requesting more interrupts than supported on s390.
  The issue can finally lead to an out of bounds access.

  It needs to be applied to 18.04 and 16.04 (in addition to cosmic).

  == Fix ==

  commit 866f3576a72b2233a76dffb80290f8086dc49e17 upstream.

  During interrupt setup we allocate interrupt vectors, walk the list of msi
  descriptors, and fill in the message data. Requesting more interrupts than
  supported on s390 can lead to an out of bounds access.

  When we restrict the number of interrupts we should also stop walking the
  msi list after all supported interrupts are handled.

  == Regression Potential ==

  Low. The modification is limited to the following two lines in s390/pci:
  ...
  + if (hwirq >= msi_vecs)
  + break;
  ...

  https://lkml.org/lkml/2018/9/3/1125

  == Test Case ==

  A test case will be provided by IBM.
  And the test and verification will also be done by IBM.

  __

  Bug Description:

  s390/pci: fix out of bounds access during irq setup

  During interrupt setup we allocate interrupt vectors, walk the list of msi
  descriptors, and fill in the message data. Requesting more interrupts than
  supported on s390 can lead to an out of bounds access.

  When we restrict the number of interrupts we should also stop walking the
  msi list after all supported interrupts are handled.

  Upstream-ID:  866f3576a72b2233a76dffb80290f8086dc49e17
  kernel 4.19

  Also to be applied to 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790658/+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 1790620] Re: Xenial update to 4.4.141 stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Xenial update to 4.4.141 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.141 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.141 stable release shall be applied:
  * MIPS: Fix ioremap() RAM check
  * ibmasm: don't write out of bounds in read handler
  * vmw_balloon: fix inflation with batching
  * ahci: Disable LPM on Lenovo 50 series laptops with a too old BIOS
  * USB: serial: ch341: fix type promotion bug in ch341_control_in()
  * USB: serial: cp210x: add another USB ID for Qivicon ZigBee stick
  * USB: serial: keyspan_pda: fix modem-status error handling
  * USB: yurex: fix out-of-bounds uaccess in read handler
  * USB: serial: mos7840: fix status-register error handling
  * usb: quirks: add delay quirks for Corsair Strafe
  * xhci: xhci-mem: off by one in xhci_stream_id_to_ring()
  * HID: usbhid: add quirk for innomedia INNEX GENESIS/ATARI adapter
  * tools build: fix # escaping in .cmd files for future Make
  * iw_cxgb4: correctly enforce the max reg_mr depth
  * x86/cpufeature: Move some of the scattered feature bits to x86_capability
  * x86/cpu: Provide a config option to disable static_cpu_has
  * x86/fpu: Add an XSTATE_OP() macro
  * x86/fpu: Get rid of xstate_fault()
  * x86/headers: Don't include asm/processor.h in asm/atomic.h
  * x86/cpufeature: Replace the old static_cpu_has() with safe variant
  * x86/cpufeature: Get rid of the non-asm goto variant
  * x86/alternatives: Add an auxilary section
  * x86/alternatives: Discard dynamic check after init
  * x86/vdso: Use static_cpu_has()
  * x86/boot: Simplify kernel load address alignment check
  * x86/cpufeature: Speed up cpu_feature_enabled()
  * x86/cpufeature, x86/mm/pkeys: Add protection keys related CPUID definitions
  * x86/mm/pkeys: Fix mismerge of protection keys CPUID bits
  * x86/cpu: Add detection of AMD RAS Capabilities
  * x86/cpufeature, x86/mm/pkeys: Fix broken compile-time disabling of pkeys
  * x86/cpufeature: Make sure DISABLED/REQUIRED macros are updated
  * x86/cpufeature: Add helper macro for mask check macros
  * uprobes/x86: Remove incorrect WARN_ON() in uprobe_init_insn()
  * netfilter: nf_queue: augment nfqa_cfg_policy
  * netfilter: x_tables: initialise match/target check parameter struct
  * loop: add recursion validation to LOOP_CHANGE_FD
  * PM / hibernate: Fix oops at snapshot_write()
  * UBUNTU: SAUCE: RDMA/ucm: Blacklist UCM module
  * loop: remember whether sysfs_create_group() was done
  * Linux 4.4.141

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790620/+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 1789949] Re: WiFi-Stick TP-Link T2UH not working

[Brad Figg]

** Tags added: cscc

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

Title:
  WiFi-Stick TP-Link T2UH not working

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

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 

[Kernel-packages] [Bug 1790586] Re: The proposed grub package in Trusty / Bionic overrides the boot order on a MaaS deployed system

[Brad Figg]

** Tags added: cscc

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

Title:
  The proposed grub package in Trusty / Bionic overrides the boot order
  on a MaaS deployed system

Status in ubuntu-kernel-tests:
  Incomplete
Status in grub2 package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Similar to bug 1642298, bug 1750732 and bug 1788539

  This issue was only spotted on ThunderX Cavium ARM64 system and an AMD
  Naples amd64 server in this SRU cycle.

  Steps:
  1. Deploy the ThunderX system with Trusty + T-LTS 4.4 kernel (It works fine 
with just Trusty, however this was tested on the AMD Naples, not ThunderX since 
it does not support 3.13 kernel)
  2. Check the efibootmgr output
  3. Enable proposed, install grub-common
  4. Check efibootmgr again

  Result:
  In step 2, the boot order is correct:
  ubuntu@wright-kernel:~$ sudo efibootmgr
  BootCurrent: 0002
  Timeout: 10 seconds
  BootOrder: 0002,,0003,0004,0001
  Boot* ubuntu
  Boot0001  UEFI: Built-in EFI Shell
  Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
  Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
  Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC

  But in step 4, the boot order will be overridden:
  ubuntu@wright-kernel:~$ sudo efibootmgr
  BootCurrent: 0002
  Timeout: 10 seconds
  BootOrder: ,0002,0003,0004,0001
  Boot* ubuntu
  Boot0001  UEFI: Built-in EFI Shell
  Boot0002* UEFI: IP4 Ethernet vNIC Controller 62:54:CA
  Boot0003* UEFI: IP4 Ethernet vNIC Controller 62:54:CB
  Boot0004* UEFI: IP4 Ethernet vNIC Controller 62:54:CC

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grub-common 2.02~beta2-9ubuntu1.15
  ProcVersionSignature: User Name 4.4.0-134.160~14.04.1-generic 4.4.140
  Uname: Linux 4.4.0-134-generic aarch64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: arm64
  Date: Tue Sep  4 07:45:19 2018
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Brad Figg]

** Tags added: cscc

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

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

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

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

  
  So far this only occurred in MAAS environments and often went away with e.g. 
the next daily images. Therefore to reproduce and finally debug/fix this issue 
we'd need data from anyone being affected. This list will grow as we identify 
more that is needed.

  If you are affected, please attach to the bug
  - the kernel used to boot the guest
  - the initrd used to boot the guest
  - libvirt guest XML used to define the guest
  - PXE config provided to the guest
  - the cloud image used to start the guest (That will likely not fit as bug 
attachment, consider storing it somewhere and contact us)

  TODO: The Maas Team will outline how to get all these artifacts.
  TODO: add reference to the comment outlining this (once added)

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

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

[Kernel-packages] [Bug 1798052] Re: request_key03 in ubuntu_ltp_syscalls failed with T ARM64 / i386 / P8

[Brad Figg]

** Tags added: cscc

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

Title:
  request_key03 in ubuntu_ltp_syscalls failed with T ARM64 / i386 / P8

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

Bug description:
  After bug 1775370, this test is now failing with another error message,
  to me it looks like there is something to do with the test case.

  $ sudo ./request_key03
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted'
  request_key03.c:168: PASS: didn't crash while requesting key of type 
'encrypted'
  request_key03.c:115: BROK: unexpected error adding key of type 'trusted': 
ENOMEM
  request_key03.c:160: BROK: add_key child exited with 2

  Summary:
  passed 2
  failed 0
  skipped 0
  warnings 0
  ubuntu@amaura:/opt/ltp/testcases/bin$ uname -a
  Linux amaura 3.13.0-161-generic #211-Ubuntu SMP Wed Oct 3 14:52:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798052/+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 1801877] Re: lp1153769 in ubuntu_cts_kernel failed on P with logfd error

[Brad Figg]

** Tags added: cscc

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

Title:
  lp1153769 in ubuntu_cts_kernel failed on P with logfd error

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

Bug description:
  If you run it on jenkins remotely:
  ~/kernel-testing/remote --kernel-test-list=ubuntu_cts_kernel ubuntu@rizzo

  It will fail with:
   *** lp1153769 ***
   Running '/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 
eno1'
   [stderr] Failed opening logfd: Invalid argument
   Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File 
"/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/ubuntu_cts_kernel.py", 
line 37, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
    File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
    File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command 
 
failed, rc=234, Command returned non-zero exit status
  * Command:
  /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1
  Exit status: 234
  Duration: 0.056932926178

  This can be reproduced with just ssh on the host to SUT:
  $ myssh rizzo 
"/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1"
  Warning: Permanently added 'rizzo,10.246.72.30' (ECDSA) to the list of known 
hosts.
  Failed opening logfd: Invalid argument


  But if you run this test locally on the SUT, it will pass without any
  issue:

  sudo apt-get install git python-minimal gdb -y

  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  rm -fr autotest/client/tests
  ln -sf ~/autotest-client-tests autotest/client/tests
  AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_cts_kernel/control

  Or just run the test directly on the SUT:
  $ /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1
  autotest  kernel-test-results  kernel-testing

   Performance counter stats for 'ls':

 256 cycles#0.000 GHz

 0.002389283 seconds time elapsed

  I think this has something to do with the perf command and the shell 
redirection:
  https://lore.kernel.org/patchwork/patch/309039/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1801877/+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 1801708] Re: test_cve_2015_8539_2 failed with 3.2 Precise ESM

[Brad Figg]

** Tags added: cscc

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

Title:
  test_cve_2015_8539_2 failed with 3.2 Precise ESM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
==
FAIL: test_cve_2015_8539_2 (__main__.KernelPanicTest)
Verify CVE-2015-8539 is fixed (part 2)
--
Traceback (most recent call last):
  File "./test-kernel-panic.py", line 122, in test_cve_2015_8539_2
output = self.assertShellExitEquals(1, ['keyctl', 'add', 'trusted', 
'user', 'a', '@u'], bare_report=True)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code -9, expected 1
Command: 'keyctl', 'add', 'trusted', 'user', 'a', '@u'
Output:


  $ uname -a
  Linux onibi 3.2.0-137-generic #183-Ubuntu SMP Wed Oct 31 12:00:08 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-126-generic 3.2.0-126.169
  ProcVersionSignature: User Name 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Nov  5 10:28 seq
   crw-rw---T 1 root audio 116, 33 Nov  5 10:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Mon Nov  5 10:46:34 2018
  IwConfig:
   eno2  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. PowerEdge R310
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-126-generic 
root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-126-generic N/A
   linux-backports-modules-3.2.0-126-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1801708/+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 1801900] Re: Xenial update: 4.4.162 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Xenial update: 4.4.162 upstream stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.162 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.162
  HV: properly delay KVP packets when negotiation is in progress
  Drivers: hv: kvp: fix IP Failover
  Drivers: hv: util: Pass the channel information during the init call
  Drivers: hv: utils: Invoke the poll function after handshake
  usb: gadget: serial: fix oops when data rx'd after close
  ARC: build: Get rid of toolchain check
  powerpc/tm: Avoid possible userspace r1 corruption on reclaim
  powerpc/tm: Fix userspace r13 corruption
  net/mlx4: Use cpumask_available for eq->affinity_mask
  Input: atakbd - fix Atari CapsLock behaviour
  Input: atakbd - fix Atari keymap
  clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for 
non-am43 SoCs
  media: af9035: prevent buffer overflow on write
  x86/fpu: Finish excising 'eagerfpu'
  x86/fpu: Remove struct fpu::counter
  x86/fpu: Remove use_eager_fpu()
  KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch
  rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096
  net: systemport: Fix wake-up interrupt race during resume
  net: mvpp2: Extract the correct ethtype from the skb for tx csum offload
  team: Forbid enslaving team device to itself
  qlcnic: fix Tx descriptor corruption on 82xx devices
  net/usb: cancel pending work when unbinding smsc75xx
  netlabel: check for IPV4MASK in addrinfo_get
  net/ipv6: Display all addresses in output of /proc/net/if_inet6
  net: ipv4: update fnhe_pmtu when first hop's MTU changes
  ipv4: fix use-after-free in ip_cmsg_recv_dstaddr()
  ip_tunnel: be careful when accessing the inner header
  ip6_tunnel: be careful when accessing the inner header
  bonding: avoid possible dead-lock
  bnxt_en: Fix TX timeout during netpoll.
  jffs2: return -ERANGE when xattr buffer is too small
  xhci: Don't print a warning when setting link state for disabled ports
  i2c: i2c-scmi: fix for i2c_smbus_write_block_data
  perf script python: Fix export-to-postgresql.py occasional failure
  mach64: detect the dot clock divider correctly on sparc
  mm/vmstat.c: fix outdated vmstat_text
  ext4: add corruption check in ext4_xattr_set_entry()
  drm/amdgpu: Fix SDMA HQD destroy error on gfx_v7
  ARM: dts: at91: add new compatibility string for macb on sama5d3
  net: macb: disable scatter-gather for macb on sama5d3
  stmmac: fix valid numbers of unicast filter entries
  sound: enable interrupt after dma buffer initialization
  mfd: omap-usb-host: Fix dts probe of children
  selftests/efivarfs: add required kernel configs
  ASoC: sigmadsp: safeload should not have lower byte limit
  ASoC: wm8804: Add ACPI support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801900/+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 1801747] Re: External display not recognized, internal one goes to black

[Brad Figg]

** Tags added: cscc

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

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  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: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  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/gdm3/+bug/1801747/+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 1801404] Re: Macbook air, 18.10, fn keys to set keyboard backlight do not work

[Brad Figg]

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

** Tags added: cscc

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

Title:
  Macbook air, 18.10, fn keys to set keyboard backlight do not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The F5/F6 keys used to work to set the keyboard backillumination level
  with 18.04 but they do not work anymore with 18.10 4.18.0-10-generic

  The back illumination can be turned on with : echo 255 >
  /sys/class/leds/smc\:\:kbd_backlight/brightness but not anymore with
  the Fn keys.

  I'm not sure if it is a kernel issue or a keyboard mapping / X issue.
  Which test should I run to try to figure out where the problem is?

  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: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xavier 1452 F pulseaudio
   /dev/snd/controlC1:  xavier 1452 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Nov  2 19:45:26 2018
  InstallationDate: Installed on 2018-10-27 (6 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Apple Inc. MacBookAir7,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/lvm--vg-ubuntu--root ro 
cryptopts=target=CryptDisk,source=/dev/disk/by-uuid/0e4ab982-9511-479c-8a7a-4d933fcd3df1,lvm=lvm-vg
 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA71.88Z.0178.B00.1806051659
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-937CB26E2E02BB01
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir7,2
  dmi.chassis.asset.tag: Chassis Board Asset Tag#
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-937CB26E2E02BB01
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA71.88Z.0178.B00.1806051659:bd06/05/2018:svnAppleInc.:pnMacBookAir7,2:pvr1.0:rvnAppleInc.:rnMac-937CB26E2E02BB01:rvrMacBookAir7,2:cvnAppleInc.:ct9:cvrMac-937CB26E2E02BB01:
  dmi.product.family: Mac
  dmi.product.name: MacBookAir7,2
  dmi.product.sku: System SKU#
  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/1801404/+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 1801246] Re: [AEP]WARN triggered by the device-dax unit test with 4.19-rc1

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]WARN triggered by the device-dax unit test with 4.19-rc1

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  [ +0.003470] WARNING: CPU: 3 PID: 7380 at fs/buffer.c:581 
__set_page_dirty+0xb1/0xc0
  [ +0.001177] Modules linked in: nd_pmem(O) dax_pmem(O) device_dax(O) 
nd_btt(O) nd_e820(O) nfit(O) libnvdimm(O) nfit_test_iomap(O)
  [ 0.001941] CPU: 3 PID: 7380 Comm: lt-device-dax Tainted: G O 4.19.0-rc1 #3
  [ +0.001423] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014
  [ +0.002023] RIP: 0010:__set_page_dirty+0xb1/0xc0
  [ +0.000789] Code: 80 00 5b 4c 89 e6 48 89 ef 5d 41 5c 41 5d 41 5e e9 a4 ac 
82 00 48 8b 00 f6 c4 02 74 d7 48 89 df e8 54 bb f6 ff 48 89 c6 eb ce <0f> 0b eb 
92 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 41 55
  [ +0.003122] RSP: 0018:c90001bbba38 EFLAGS: 00010046
  [ +0.000911] RAX: 007fff800815 RBX: ea0008108000 RCX: eb851eb851eb851f
  [ +0.001212] RDX:  RSI: 880310c51560 RDI: 0046
  [ +0.001203] RBP: 880310c51548 R08:  R09: 0001
  [ +0.001220] R10: c90001bbb9a8 R11: b200 R12: 0246
  [ +0.001202] R13: 880310c51540 R14: 0001 R15: 88016dd68040
  [ +0.001205] FS: 7f418f6cf780() GS:880311a0() 
knlGS:
  [ +0.001363] CS: 0010 DS:  ES:  CR0: 80050033
  [ +0.000975] CR2: 7f418f6ee000 CR3: 0001a1a36003 CR4: 001606e0
  [ +0.001217] Call Trace:
  [ +0.000435] __set_page_dirty_buffers+0xad/0x100
  [ +0.000791] set_page_dirty_lock+0x41/0x60
  [ +0.000709] dio_bio_complete+0x12c/0x160
  [ +0.000693] ? do_blockdev_direct_IO+0x1c8b/0x2b60
  [ +0.000825] do_blockdev_direct_IO+0x1d29/0x2b60
  [ +0.000827] ? ext4_dio_get_block_unwritten_sync+0x50/0x50
  [ +0.000944] ? ext4_direct_IO+0x15a/0x790
  [ +0.000681] ext4_direct_IO+0x15a/0x790
  [ +0.000672] ? touch_atime+0xc6/0xd0
  [ +0.000621] generic_file_read_iter+0xbb/0xd40
  [ +0.000762] ? up_write+0x1c/0x80
  [ +0.000565] ? ext4_file_write_iter+0x20d/0x400
  [ +0.000789] __vfs_read+0x112/0x190
  [ +0.000619] vfs_read+0x9e/0x150
  [ +0.000418] ksys_pread64+0x74/0x90
  [ +0.000505] do_syscall_64+0x60/0x210
  [ +0.000466] entry_SYSCALL_64_after_hwframe+0x49/0xbe
  [ +0.000618] RIP: 0033:0x7f418e7a1f63
  [ +0.000437] Code: f3 a9 f2 ff e8 4e 5b 02 00 66 2e 0f 1f 84 00 00 00 00 00 
0f 1f 40 00 83 3d e9 d8 2d 00 00 75 13 49 89 ca b8 11 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 34 c3 48 83 ec 08 e8 6b 15 02 00 48 89 04 24
  [ +0.002233] RSP: 002b:7ffc3fb777e8 EFLAGS: 0246 ORIG_RAX: 
0011
  [ +0.000916] RAX: ffda RBX: 7f418f6ea000 RCX: 7f418e7a1f63
  [ +0.000879] RDX: 1000 RSI: 7f418f6ea000 RDI: 0005
  [ +0.000896] RBP:  R08: 001b R09: 
  [ +0.000884] R10:  R11: 0246 R12: 0005
  [ +0.000879] R13:  R14: 0004 R15: 2000
  [ +0.000889] irq event stamp: 136672
  [ +0.000443] hardirqs last enabled at (136671): [] 
_raw_spin_unlock_irqrestore+0x32/0x60
  [ +0.001185] hardirqs last disabled at (136672): [] 
_raw_spin_lock_irqsave+0x22/0x80
  [ +0.001120] softirqs last enabled at (136542): [] 
__do_softirq+0x32e/0x428
  [ +0.001028] softirqs last disabled at (136535): [] 
irq_exit+0xf6/0x100
  [ +0.000995] --[ end trace 2dbcab5579c2e08f ]--

  $ git bisect log 
  git bisect start

  good: [021c91791a5e7e85c567452f1be3e4c2c6cb6063] Linux 4.18-rc3
  git bisect good 021c91791a5e7e85c567452f1be3e4c2c6cb6063
  bad: [c953cc987ab87d180e1d5de2f1c217abe33aac77] libnvdimm, pmem: Restore page 
attributes when clearing errors
  git bisect bad c953cc987ab87d180e1d5de2f1c217abe33aac77
  bad: [2fa147bdbf672c53386a8f5f2c7fe358004c3ef8] mm, dev_pagemap: Do not clear 
->mapping on final put
  git bisect bad 2fa147bdbf672c53386a8f5f2c7fe358004c3ef8
  bad: [35de299547d1c3300e078f9f7c6eb01dadae47f9] device-dax: Set page->index
  git bisect bad 35de299547d1c3300e078f9f7c6eb01dadae47f9
  bad: [2232c6382a453db73d2e723df1b52030066e135e] device-dax: Enable 
page_mapping()
  git bisect bad 2232c6382a453db73d2e723df1b52030066e135e
  good: [226ab561075f6f8f3cd5f7b3b7544f3997aab51f] device-dax: Convert to 
vmf_insert_mixed and vm_fault_t
  git bisect good 226ab561075f6f8f3cd5f7b3b7544f3997aab51f
  first bad commit: [2232c6382a453db73d2e723df1b52030066e135e] device-dax: 
Enable page_mapping()
  commit 2232c6382a453db73d2e723df1b52030066e135e
  Author: Dan Williams 
  Date: Fri Jul 13 21:49:40 2018 -0700

  device-dax: Enable page_mapping()

  In support of enabling memory_failure() handling for 

[Kernel-packages] [Bug 1797753] Re: I have lenevo ideapad 130-131KB and in that there is not support for wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad doing xinput)

[Brad Figg]

** Tags added: cscc

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

Title:
  I have lenevo ideapad 130-131KB and in that there is not support for
  wifi-adapter and touchpad (RTL8821CE chip and no detection of mousepad
  doing xinput)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed a fresh ubuntu 18.04 in lenevo ideapad 130-131 and after 
installation there is no wifi adapter and also touchpad not working 
  firstly id lspci and in that the output i found of chip :

  02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter

  secondly id did xinput but there was not device dected as touchpad

  after that i dual boot centos 7 along side ubunt in that touchpad is
  working but again wifi adapter not found

  please solve this issue for both ubuntu (wifi adapter  not found and touchpad 
not detected) and centos
  (wifi adapter not found)

  i searched and read regarding this issue and tried all of the but
  didn't find any solution so at last i have hopes only on u all

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797753/+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 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

[Brad Figg]

** Tags added: cscc

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802021/+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 1801931] Re: Cosmic update: 4.18.13 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Cosmic update: 4.18.13 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.18.13 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * rseq/selftests: fix parametrized test with -fpie
  * mac80211: Run TXQ teardown code before de-registering interfaces
  * mac80211_hwsim: require at least one channel
  * Btrfs: fix unexpected failure of nocow buffered writes after snapshotting 
when
low on space
  * KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function
  * cfg80211: remove division by size of sizeof(struct ieee80211_wmm_rule)
  * btrfs: btrfs_shrink_device should call commit transaction at the end
  * scsi: csiostor: add a check for NULL pointer after kmalloc()
  * scsi: csiostor: fix incorrect port capabilities
  * scsi: libata: Add missing newline at end of file
  * scsi: aacraid: fix a signedness bug
  * bpf, sockmap: fix potential use after free in bpf_tcp_close
  * bpf, sockmap: fix psock refcount leak in bpf_tcp_recvmsg
  * bpf: sockmap, decrement copied count correctly in redirect error case
  * mac80211: correct use of IEEE80211_VHT_CAP_RXSTBC_X
  * mac80211_hwsim: correct use of IEEE80211_VHT_CAP_RXSTBC_X
  * cfg80211: make wmm_rule part of the reg_rule structure
  * mac80211_hwsim: Fix possible Spectre-v1 for hwsim_world_regdom_custom
  * nl80211: Fix nla_put_u8 to u16 for NL80211_WMMR_TXOP
  * nl80211: Pass center frequency in kHz instead of MHz
  * bpf: fix several offset tests in bpf_msg_pull_data
  * gpio: adp5588: Fix sleep-in-atomic-context bug
  * mac80211: mesh: fix HWMP sequence numbering to follow standard
  * mac80211: avoid kernel panic when building AMSDU from non-linear SKB
  * gpiolib: acpi: Switch to cansleep version of GPIO library call
  * gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall
  * gpio: dwapb: Fix error handling in dwapb_gpio_probe()
  * bpf: fix msg->data/data_end after sg shift repair in bpf_msg_pull_data
  * bpf: fix shift upon scatterlist ring wrap-around in bpf_msg_pull_data
  * bpf: fix sg shift repair start offset in bpf_msg_pull_data
  * tipc: switch to rhashtable iterator
  * sh_eth: Add R7S9210 support
  * net: mvpp2: initialize port of_node pointer
  * tc-testing: add test-cases for numeric and invalid control action
  * cfg80211: nl80211_update_ft_ies() to validate NL80211_ATTR_IE
  * mac80211: do not convert to A-MSDU if frag/subframe limited
  * mac80211: always account for A-MSDU header changes
  * tools/kvm_stat: fix python3 issues
  * tools/kvm_stat: fix handling of invalid paths in debugfs provider
  * tools/kvm_stat: fix updates for dead guests
  * gpio: Fix crash due to registration race
  * ARC: atomics: unbork atomic_fetch_##op()
  * Revert "blk-throttle: fix race between blkcg_bio_issue_check() and
cgroup_rmdir()"
  * md/raid5-cache: disable reshape completely
  * RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0
  * selftests: pmtu: maximum MTU for vti4 is 2^16-1-20
  * selftests: pmtu: detect correct binary to ping ipv6 addresses
  * ibmvnic: Include missing return code checks in reset function
  * bpf: Fix bpf_msg_pull_data()
  * bpf: avoid misuse of psock when TCP_ULP_BPF collides with another ULP
  * i2c: uniphier: issue STOP only for last message or I2C_M_STOP
  * i2c: uniphier-f: issue STOP only for last message or I2C_M_STOP
  * net: cadence: Fix a sleep-in-atomic-context bug in macb_halt_tx()
  * fs/cifs: don't translate SFM_SLASH (U+F026) to backslash
  * mac80211: fix an off-by-one issue in A-MSDU max_subframe computation
  * cfg80211: fix a type issue in ieee80211_chandef_to_operating_class()
  * mac80211: fix WMM TXOP calculation
  * mac80211: fix a race between restart and CSA flows
  * mac80211: Fix station bandwidth setting after channel switch
  * mac80211: don't Tx a deauth frame if the AP forbade Tx
  * mac80211: shorten the IBSS debug messages
  * fsnotify: fix ignore mask logic in fsnotify()
  * net/ibm/emac: wrong emac_calc_base call was used by typo
  * nds32: fix logic for module
  * nds32: add NULL entry to the end of_device_id array
  * nds32: Fix empty call trace
  * nds32: Fix get_user/put_user macro expand pointer problem
  * nds32: fix build error 

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

[Brad Figg]

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

** Tags added: cscc

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

Title:
  openat03 in ubuntu_ltp_syscalls failed with T

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

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

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

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

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

[Kernel-packages] [Bug 1798025] Re: keyctl06 in ubuntu_ltp_syscalls failed with T

[Brad Figg]

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

** Tags added: cscc

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

Title:
  keyctl06 in ubuntu_ltp_syscalls failed with T

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

Bug description:
  <<>>
  tag=keyctl06 stime=1539670421
  cmdline="keyctl06"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  keyctl06.c:64: FAIL: KEYCTL_READ overran the buffer

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0

  From the test case, this is for:
  /*
   * Regression test for:
   *
   *commit e645016abc80 ("KEYS: fix writing past end of user-supplied buffer
   *in keyring_read()").
   *
   * as well as its follow-on fix:
   *
   *commit 3239b6f29bdf ("KEYS: return full count in keyring_read() if
   *buffer is too small")
   *
   */

  When running the complete syscalls test suite, it will failed with the 
following error message instead:
  keyctl06.c:41: BROK: Failed to add test key: EDQUOT

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 03:39 seq
   crw-rw 1 root audio 116, 33 Oct 16 03:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 16 06:13:57 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:

  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.name: S1200RP
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798025/+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 1802056] Re: Unable to start KVM, timed out waiting for dnsmasq lease

[Brad Figg]

** Tags added: ubuntu-certified

** Tags added: cscc

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

Title:
  Unable to start KVM, timed out waiting for dnsmasq lease

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

Bug description:
  On node gonzo with Trusty + uvtool (0~bzr92-0ubuntu1.1) and
  0~bzr99~ubuntu14.04.1 from ppa, the kvm smoke test failed with dnsmasq
  lease time out.

  ubuntu@gonzo:~$ uvt-kvm create trusty release=trusty arch=amd64
  ubuntu@gonzo:~$ uvt-kvm wait  trusty  --insecure --ssh-private-key-file 
/home/ubuntu/.ssh/id_rsa
  uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:c9:fe:f5.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-161-generic 3.13.0-161.211
  ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-161-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  7 03:48 seq
   crw-rw 1 root audio 116, 33 Nov  7 03:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  7 07:03:48 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R415
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic 
root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-161-generic N/A
   linux-backports-modules-3.13.0-161-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.3
  dmi.board.name: 08WNM9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.3:bd04/26/2012:svnDellInc.:pnPowerEdgeR415:pvr:rvnDellInc.:rn08WNM9:rvrA02:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R415
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802056/+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 1798332] Re: Support Edge Gateway's Bluetooth LED

[Brad Figg]

** Tags added: cscc

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

Title:
  Support Edge Gateway's Bluetooth LED

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

Bug description:
  == Impact ==
  The Bluetooth LED of Marvell 88W8897 is not enabled by default (there's no 
code for controlling LED). It is requested to be ON and OFF when the radio is 
on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # hciconfig hci0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798332/+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 1801260] Re: USB Type-C Alternate Mode support

[Brad Figg]

** Tags added: cscc

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

Title:
  USB Type-C Alternate Mode support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Let's track here the progress for generic alternate mode support. The 
discovery and entering/exiting the modes is common for all alternate modes, and 
the USB PD code will handle that. The tasks currently related to this task are:

  1) The alternate modes will need custom control that we don't want to
  mix into the generic USB PD code. For example the DP altmode defines
  custom VDM (Vendor Defined Message) for "configure" and "status"
  commands. So we will need to create somekind of API for Alternate Mode
  "drivers".

  2) The Alternate Modes need to keep the underlying components and
  drivers informed about their status, possibly even allow some control.
  For example, with DP altmode the graphics side will need to know the
  cable orientation and the number of lanes (the modes define the pin
  configuration in DP altmode, so the numer of available lanes as well
  AFAIK). So we need API for this.

  *) UCSI may need some special attention, as with UCSI we don't handle
  the USB PD communication. We just get the status of the port. But we
  will know which alternate mode has been enterred, and we can actually
  request enter/exit a mode even with UCSI. But we don't know for
  example the cable orientation.

  Commits:
  0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 
49cbb33dfdeb7651b91c2316a61b644d8e6cfe22 
4ab8c18d4d67321cc7b660559de17511d4fc0237 
8a37d87d72f0c69f837229c04d2fcd7117ea57e7 
93dd2112c7b2fa5512cc4aff2c449420487fcb68 
e9576fe8e605c4413beb91b290b8a473985710de 

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801260/+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 1801875] Re: Power consumption during s2idle is higher than long idle(sk hynix)

[Brad Figg]

** Tags added: cscc

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

Title:
  Power consumption during s2idle is higher than long idle(sk hynix)

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

Bug description:
  [Impact]
  On some Dell XPS models, we observed the power consumption raises higher than 
long idle does during s2idle with sk hynix nvme.

  C2:
  Short idle: 4
  Long idle: 1
  S2I: 3.7
  S5: 0.19

  C3:
  Short idle: 7.2
  Long idle: 4.5
  S2I: 6.22
  S5: 0.18

  C5:
  Short idle: 6.5
  Long idle: 1
  S2I: 2.88
  S5: 0.18

  [Fix]
  From SK hynix FE, MS Windows doesn't put nvme to D3, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on different XPS machines with different sk hynix nvme disks, it 
fixes the power consumption issue with no regression. And the power consumption 
drops to 0.77W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

  [Misc]
  This issue should be fixed by the firmware, and we're pushing sk hynix to fix 
it. But before sk hynix find out how to solve it, we have to preserve these 
commits in our kernel for a while.
  BTW, the patches use pm_suspend_via_s2idle() function from below commit which 
is still under reviewing.
  https://lists.ubuntu.com/archives/kernel-team/2018-October/096141.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801875/+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 1798022] Re: keyctl02 in ubuntu_ltp_syscalls failed with T

[Brad Figg]

** Tags added: cscc

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

Title:
  keyctl02 in ubuntu_ltp_syscalls failed with T

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid

Bug description:
  This test is related to CVE-2015-7550, which has been marked as fix-released 
for Trusty kernel
  (commit b4a1b4f5047e4f54e194681125c74c0aa64d637d)

  <<>>
  tag=cve-2015-7550 stime=1539669622
  cmdline="keyctl02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
  keyctl02.c:80: BROK: Failed to add key: EDQUOT

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798022/+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 1801249] Re: [AEP]softlockup running dax.sh against latest ext4 dev tree

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]softlockup running dax.sh against latest ext4 dev tree

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Investigate the lockup report running dax.sh against ext4.

  [ 17.232155] pmem2: detected capacity change from 0 to 134232408064
  [ 238.399253] EXT4-fs (pmem0): DAX enabled. Warning: EXPERIMENTAL, use at 
your own risk
  [ 238.404495] EXT4-fs (pmem0): mounted filesystem with ordered data mode. 
Opts: dax
  [ 238.460013] Injecting memory failure for pfn 0x208900 at process virtual 
address 0x7f38f190
  [ 238.462987] Memory failure: 0x208900: Killing dax-pmd:12226 due to hardware 
memory corruption
  [ 238.465781] Memory failure: 0x208900: recovery action for dax page: 
Recovered
  [ 264.699441] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! 
[dax-pmd:12226]
  [..]
  [ 264.714244] hardirqs last enabled at (106241291): [] 
_raw_spin_unlock_irq+0x29/0x40
  [ 264.717185] hardirqs last disabled at (106241292): [] 
trace_hardirqs_off_thunk+0x1a/0x1c
  [ 264.720163] softirqs last enabled at (106237250): [] 
__do_softirq+0x32e/0x428
  [ 264.722974] softirqs last disabled at (106237243): [] 
irq_exit+0xf6/0x100
  [ 264.725701] CPU: 6 PID: 12226 Comm: dax-pmd Tainted: G OE 4.19.0-rc3+ #2350
  [ 264.728398] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014
  [ 264.731851] RIP: 0010:lock_is_held_type+0x46/0x60
  [..]
  [ 264.757670] Call Trace:
  [ 264.758745] find_get_entries+0x195/0x3c0
  [ 264.760133] pagevec_lookup_entries+0x1a/0x30
  [ 264.761597] dax_layout_busy_page+0x9c/0x280
  [ 264.763038] ? __lock_acquire+0x12fa/0x1310
  [ 264.764469] ext4_break_layouts+0x48/0x100
  [ 264.765869] ? ext4_punch_hole+0x108/0x5a0
  [ 264.767267] ext4_punch_hole+0x110/0x5a0
  [ 264.768646] ext4_fallocate+0x189/0xa40
  [ 264.76] ? rcu_read_lock_sched_held+0x6b/0x80
  [ 264.771532] ? rcu_sync_lockdep_assert+0x2e/0x60
  [ 264.773040] vfs_fallocate+0x13f/0x270
  [ 264.774373] ksys_fallocate+0x3c/0x70
  [ 264.775694] __x64_sys_fallocate+0x1a/0x20
  [ 264.777094] do_syscall_64+0x60/0x210
  [ 264.778417] entry_SYSCALL_64_after_hwframe+0x49/0xbe

  Commits:
  d7782145e1ad f52afc93cd01

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801249/+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 1801245] Re: [AE{]Prevent any ARS attempts when capabilities are clear

[Brad Figg]

** Tags added: cscc

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

Title:
  [AE{]Prevent any ARS attempts when capabilities are clear

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  The v4.17 ARS reworks broke the kernel's honoring of "no ARS capability" 
responses from the BIOS. The kernel unconditionally schedules ARS for all PMEM 
regions. Fix up the implementation to fail all ARS when no capability is 
present.

  Ideally the BIOS would just not publish the DSMs, for ARS, but we
  should handle capabilities being present or not regardless.

  Target Kernel: 4.20
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801245/+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 1801251] Re: [AEP]Fix badblocks population for 'raw' namespaces

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]Fix badblocks population for 'raw' namespaces

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  The driver is only initializing bb_res in the devm_memremap_pages()
  paths, but the raw namespace case is passing an uninitialized bb_res to
  nvdimm_badblocks_populate().

  Fixes: e8d513483300 ("memremap: change devm_memremap_pages interface...")
  Cc: 
  Cc: Christoph Hellwig 
  Reported-by: Jacek Zloch 
  Reported-by: Krzysztof Rusocki 
  Reviewed-by: Vishal Verma 
  Signed-off-by: Dan Williams 

  Target Release: 19.04
  Target Kernel: 4.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801251/+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 1802023] Re: hns3: map tx ring to tc

[Brad Figg]

** Tags added: cscc

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

Title:
  hns3: map tx ring to tc

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  hns3 supports hardware-based traffic classes. However, this requires that the 
driver map the classes to hardware rings during initialization.

  [Test Case]
  I don't have a way to verify that the hardware is behaving as programmed, so 
this is regression-tested only.

  [Fix]
  1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up

  [Regression Risk]
  Restricted to a single driver, which has been tested on the target SoC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802023/+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 1801975] Re: update to build for 4.19

[Brad Figg]

** Tags added: cscc

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

Title:
  update to build for 4.19

Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in dm-writeboost source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in dm-writeboost source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid

Bug description:
  [Impact]
  dm-writeboost-dkms won't build with bionic/linux-hwe-edge 5.0.

  [Test case]
  Test that the dkms now builds with 5.0 kernel and still builds with 4.15 
kernel.

  [Regression potential]
  The module may not build anymore on older kernels, that has been tested.
  ===

  dm-writeboost-dkms fails to build on linux 4.19.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+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 1802100] Re: Cosmic update: 4.18.16 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Cosmic update: 4.18.16 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.18.16 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * soundwire: Fix duplicate stream state assignment
  * soundwire: Fix incorrect exit after configuring stream
  * soundwire: Fix acquiring bus lock twice during master release
  * media: af9035: prevent buffer overflow on write
  * spi: gpio: Fix copy-and-paste error
  * batman-adv: Avoid probe ELP information leak
  * batman-adv: Fix segfault when writing to throughput_override
  * batman-adv: Fix segfault when writing to sysfs elp_interval
  * batman-adv: Prevent duplicated gateway_node entry
  * batman-adv: Prevent duplicated nc_node entry
  * batman-adv: Prevent duplicated softif_vlan entry
  * batman-adv: Prevent duplicated global TT entry
  * batman-adv: Prevent duplicated tvlv handler
  * batman-adv: fix backbone_gw refcount on queue_work() failure
  * batman-adv: fix hardif_neigh refcount on queue_work() failure
  * cxgb4: fix abort_req_rss6 struct
  * clocksource/drivers/ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for 
non-am43
SoCs
  * scsi: ibmvscsis: Fix a stringop-overflow warning
  * scsi: ibmvscsis: Ensure partition name is properly NUL terminated
  * intel_th: pci: Add Ice Lake PCH support
  * Input: atakbd - fix Atari keymap
  * Input: atakbd - fix Atari CapsLock behaviour
  * selftests: pmtu: properly redirect stderr to /dev/null
  * net: emac: fix fixed-link setup for the RTL8363SB switch
  * ravb: do not write 1 to reserved bits
  * net/smc: fix non-blocking connect problem
  * net/smc: fix sizeof to int comparison
  * qed: Fix populating the invalid stag value in multi function mode.
  * qed: Do not add VLAN 0 tag to untagged frames in multi-function mode.
  * PCI: dwc: Fix scheduling while atomic issues
  * RDMA/uverbs: Fix validity check for modify QP
  * scsi: lpfc: Synchronize access to remoteport via rport
  * drm: mali-dp: Call drm_crtc_vblank_reset on device init
  * scsi: ipr: System hung while dlpar adding primary ipr adapter back
  * scsi: sd: don't crash the host on invalid commands
  * bpf: sockmap only allow ESTABLISHED sock state
  * bpf: sockmap, fix transition through disconnect without close
  * bpf: test_maps, only support ESTABLISHED socks
  * net/mlx4: Use cpumask_available for eq->affinity_mask
  * clocksource/drivers/fttmr010: Fix set_next_event handler
  * RDMA/bnxt_re: Fix system crash during RDMA resource initialization
  * RISC-V: include linux/ftrace.h in asm-prototypes.h
  * iommu/rockchip: Free irqs in shutdown handler
  * pinctrl/amd: poll InterruptEnable bits in amd_gpio_irq_set_type
  * powerpc/tm: Fix userspace r13 corruption
  * powerpc/tm: Avoid possible userspace r1 corruption on reclaim
  * powerpc/numa: Use associativity if VPHN hcall is successful
  * iommu/amd: Return devid as alias for ACPI HID devices
  * x86/boot: Fix kexec booting failure in the SEV bit detection code
  * Revert "vfs: fix freeze protection in mnt_want_write_file() for overlayfs"
  * mremap: properly flush TLB before releasing the page
  * ARC: build: Get rid of toolchain check
  * ARC: build: Don't set CROSS_COMPILE in arch's Makefile
  * Linux 4.18.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802100/+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 1801668] Re: [AEP] ndctl test failed (21/24) and latest commits needed

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP] ndctl test failed (21/24) and latest commits needed

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Description:

  ndctl testing for AEP:

  make --no-print-directory check-TESTS
  FAIL: libndctl
  FAIL: dsm-fail
  PASS: dpa-alloc
  PASS: parent-uuid
  PASS: multi-pmem
  PASS: create.sh
  PASS: clear.sh
  PASS: pmem-errors.sh
  PASS: daxdev-errors.sh
  PASS: multi-dax.sh
  PASS: btt-check.sh
  PASS: label-compat.sh
  PASS: blk-exhaust.sh
  PASS: sector-mode.sh
  PASS: inject-error.sh
  PASS: btt-errors.sh
  PASS: hugetlb
  PASS: btt-pad-compat.sh
  PASS: firmware-update.sh
  PASS: ack-shutdown-count-set
  PASS: rescan-partitions.sh
  FAIL: inject-smart.sh
  PASS: monitor.sh
  PASS: max_available_extent_ns.sh
  make[5]: Nothing to be done for `all'.
  
  Testsuite summary for ndctl 62+
  
  # TOTAL: 24
  # PASS:  21
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  3
  # XPASS: 0
  # ERROR: 0
  
  See test/test-suite.log
  Please report to linux-nvd...@lists.01.org
  
  make[4]: *** [test-suite.log] Error 1
  make[3]: *** [check-TESTS] Error 2
  make[2]: *** [check-am] Error 2
  make[1]: *** [check-recursive] Error 1
  make: *** [check] Error 2

  Reproduce Steps:
  1. Build and install kernel
  when doing ndctl testing, this need kernel ndctl test kernel module support.
  a.Download source kernel
  For exmaple:
  wget https://packages.ubuntu.com/cosmic/linux-source-4.18.0 
  or git clone git://kernel.ubuntu.com/ubuntu/ubuntu-cosmic.git

  b.Configure, build and install kernel
  # yes ''|make oldconfig
  # Ubuntu set CONFIG_LIBNVDIMM to ‘M’
  make menuconfig -> Processor type and features -> Support non-standard 
NVDIMMs and ADR protected memory  set to 'm' (Turn down two pages)

  # make –j`nproc`
  # make M=tools/testing/nvdimm
  # make M=tools/testing/nvdimm modules_install
  # make modules_install
  # make install

  2. download ndctl source package
  download from github
  https://github.com/pmem/ndctl

  3) Build ndctl test package
  # apt install –y autogen autoconf libopenr2-bin automake ranlib nvptx-tools 
libtool asciidoctor libkmod-dev libkmod2 libudev-dev uuid-dev libcjson-dev 
libjson-c-dev
  # rpmbuild –bp ndctl.spec
  # cd ./BUILD/ndctl-62
  # export LC_ALL=C (for Ubuntu)
  # ./autogen.sh
  # ./ configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc 
--libdir=/usr/lib64 --with-systemd-unit-dir  --enable-test
  # export KVER=4.20.0
  # yum install jq
  # make check

  Commits related with failed test case:

  b4d4702f30e0 tools/testing/nvdimm: improve emulation of smart injection
  39611e83a28c tools/testing/nvdimm: Make DSM failure code injection an override
  099b07a25fff acpi, nfit: Prefer _DSM over _LSR for namespace label reads
  08e6b3c6e3a0 libnvdimm: Introduce locked DIMM capacity support
  41cd8b70c37a libnvdimm, btt: add support for blk integrity
  5e096ef3b29e6113a7aa6a7dc4871987efa99bcb nfit_test: when clearing poison, 
also remove badrange entries
  89360b87c3efa5d265a3b43dd8fc245c8f4356e3 libnvdimm, badrange: remove a WARN 
for list_empty
  9fb1a1903345fea598f48277576a3589a972b72e nfit_test: add error injection DSMs
  aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a libnvdimm: move poison list 
functions to a new 'badrange' file

  Target Kernel: 4.19
  Target Release: 19.04

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

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

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

[Brad Figg]

** Tags added: cscc

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

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

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

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108

  ---

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

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

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

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

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

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

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

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

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

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

[Kernel-packages] [Bug 1801263] Re: Update to the latest QAT driver

[Brad Figg]

** Tags added: cscc

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

Title:
  Update to the latest QAT driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Update to the latest QAT driver

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801263/+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 1801287] Re: [VROC] Update MD RAID drivers to the latest upstream version

[Brad Figg]

** Tags added: cscc

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

Title:
  [VROC] Update MD RAID drivers to the latest upstream version

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  Update MD RAID drivers to the latest upstream version
  Include md/bitmap, raid0, raid1, raid10 and raid456.

  This capability takes advantage of MD's long history and extends it to 
support the Intel Matrix metadata format (IMSM).
  MD provides a path to full Intel Matrix feature compatibility with minimal 
kernel changes.

  MD driver extensions are in active development. Final version will be 
included in Shaohua Li's GIT repository:
  https://git.kernel.org/cgit/linux/kernel/git/shli/md.git/

  Target Release: 19.04
  Target Kernel: 5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801287/+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 1711075] Re: [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at Breakpoint overflow signal handler

[Brad Figg]

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

** Tags added: cscc

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

Title:
  [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at
  Breakpoint overflow signal handler

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: # - Shriya R. Kulkarni <> - 2017-06-14 01:11:02 ==
  Problem Description :
  =
  perf test is hung at Breakpoint overflow signal handler.

  Machine details :
  ==
  System : WSP , P9 baremetal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Testing:
  
  root@ltc-wspoon3:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Skip
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler :^C

  root@ltc-wspoon3:~# perf test -v 17
  17: Breakpoint overflow signal handler :
  --- start ---
  test child forked, pid 3802
  failed opening event 0
  failed opening event 0

  Attach : strace output.

  Steps to reproduce :
  
  1. Install perf. 
  2. Run perf test.
  3. When system hangs , exit it by : ^c.

  == Comment: # - Ravikumar B. Bangoria <> - 2017-07-13 04:44:29 ==
  Shriya,

  Can you please check after applying:
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d89ba5353f301971dd7d2f9fdf25c4432728f38e

  == Comment: # - Shriya R. Kulkarni <> - 2017-07-19 06:28:13 ==
  Verified and Tested on Ubuntu 16.04.03:
  =
  uname -a : 4.10.0-27-generic
  System : Boston

  Testing without patch using distro perf:
  
  root@ltc-boston27:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Skip
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler :^C
  root@ltc-boston27:~# 

  
  Testing with Patch using distro perf :
  ==
  root@ltc-boston27:~/linux-hwe-4.10.0/tools/perf# ./perf test
   1: vmlinux symtab matches kallsyms: Ok
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Ok
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler : FAILED!
  18: Breakpoint overflow sampling   : FAILED!
  19: Number of exit events of a simple workload : Ok
  20: Software clock events period values: Ok
  21: Object code reading: FAILED!
  22: Sample parsing   

[Kernel-packages] [Bug 1801244] Re: [AEP]Need to issue quick ARS if ARS came from ACPI uc error notification and ARS is already running

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]Need to issue quick ARS if ARS came from ACPI uc error
  notification and ARS is already running

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  If the poison creation path is executed while ARS is running as a background 
task, the call to Start ARS DSM with Flag1=1 will fail with ARS already in 
progress error. Likewise the following Start ARS DSM would also fail. How does 
linux handle this? After ARS background thread has completed, does linux know 
that there could still be unreported errors and re-execute the quick ARS to 
catch any remaining errors?

  Commits:
  cc3d3458d46f

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801244/+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 1797997] Re: kernel BUG at "/build/linux-lts-xenial-UweaL0/linux-lts-xenial-4.4.0/arch/x86/kvm/mmu.c:1366!"

[Brad Figg]

** Tags added: cscc

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

Title:
  kernel BUG at "/build/linux-lts-xenial-UweaL0/linux-lts-
  xenial-4.4.0/arch/x86/kvm/mmu.c:1366!"

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

Bug description:
  My OpenStack system have just an accident of crash one compute host.

  Compute host information:
  $ lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  $ uname -a
  Linux compute2.hn.vnpt 4.4.0-62-generic #83~14.04.1-Ubuntu SMP Wed Jan 18 
18:10:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  When I checked syslog in this compute, I found this log as issue happened. 
This log begins with:
  "kernel BUG at 
/build/linux-lts-xenial-UweaL0/linux-lts-xenial-4.4.0/arch/x86/kvm/mmu.c:1366!
  Oct 15 14:10:13 compute2 kernel: [12845630.282893] invalid opcode:  [#1] 
SMP "

  And after that, CPUs stuck in turn.

  Could it be a bug in kernel of Ubuntu 14.04.5??

  
  Oct 15 14:10:13 compute2 kernel: [12845630.278635] [ cut here 
]
  Oct 15 14:10:13 compute2 kernel: [12845630.279881] kernel BUG at 
/build/linux-lts-xenial-UweaL0/linux-lts-xenial-4.4.0/arch/x86/kvm/mmu.c:1366!
  Oct 15 14:10:13 compute2 kernel: [12845630.282893] invalid opcode:  [#1] 
SMP 
  Oct 15 14:10:13 compute2 kernel: [12845630.284590] Modules linked in: 
nf_conntrack_netlink xt_multiport xt_set ip6table_raw ip6table_mangle 
nf_conntrack_ipv6 xt_CT xt_connmark xt_mac xt_comment xt_physdev br_netfilter 
ip_set_hash_net ip_set nfnetlink iptable_raw vhost_net vhost macvtap macvlan 
veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter ip_tables x_tables nbd ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi vport_vxlan openvswitch nf_defrag_ipv6 
nf_conntrack intel_rapl x86_pkg_temp_thermal intel_powerclamp ipmi_ssif 
coretemp kvm_intel ipmi_devintf kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel mxm_wmi aes_x86_64 dcdbas dm_multipath lrw 
gf128mul glue_helper ablk_helper cryptd sb_edac shpchp edac_core mei_me ipmi_si 
lpc_ich mei acpi_power_meter 8250_fintek ipmi_msghandler wmi mac_hid 8021q garp 
mrp stp llc bonding lp parport bnx2x vxlan ip6_udp_tunnel tg3 udp_tunnel ahci 
ptp mdio megaraid_sas libahci libcrc32c pps_core fjes
  Oct 15 14:10:13 compute2 kernel: [12845630.336464] CPU: 28 PID: 27482 Comm: 
qemu-system-x86 Not tainted 4.4.0-62-generic #83~14.04.1-Ubuntu
  Oct 15 14:10:13 compute2 kernel: [12845630.346071] Hardware name: Dell Inc. 
PowerEdge R630/02C2CP, BIOS 2.3.4 11/08/2016
  Oct 15 14:10:13 compute2 kernel: [12845630.356285] task: 8820bbc0 ti: 
882753484000 task.ti: 882753484000
  Oct 15 14:10:13 compute2 kernel: [12845630.367252] RIP: 
0010:[]  [] kvm_zap_rmapp+0x53/0x60 [kvm]
  Oct 15 14:10:13 compute2 kernel: [12845630.379079] RSP: 0018:882753487bf8 
 EFLAGS: 00010246
  Oct 15 14:10:13 compute2 kernel: [12845630.385225] RAX: 0001 RBX: 
c90057d1bfa0 RCX: 8827c00d7a40
  Oct 15 14:10:13 compute2 kernel: [12845630.397478] RDX: 8827c00d7a40 RSI: 
88492f36efa0 RDI: 88492f36efa0
  Oct 15 14:10:13 compute2 kernel: [12845630.409829] RBP: 882753487c08 R08: 
 R09: 
  Oct 15 14:10:13 compute2 kernel: [12845630.422338] R10: c9003ae9c000 R11: 
0024 R12: 88154ad1c000
  Oct 15 14:10:13 compute2 kernel: [12845630.434840] R13: c0546930 R14: 
 R15: c9003ae9c008
  Oct 15 14:10:13 compute2 kernel: [12845630.447328] FS:  
7f8bfb7fe700() GS:8827de98() knlGS:
  Oct 15 14:10:13 compute2 kernel: [12845630.459840] CS:  0010 DS:  ES: 
 CR0: 80050033
  Oct 15 14:10:13 compute2 kernel: [12845630.466113] CR2: 0016 CR3: 
0004323fa000 CR4: 003426e0
  Oct 15 14:10:13 compute2 kernel: [12845630.478424] Stack:
  Oct 15 14:10:13 compute2 kernel: [12845630.484373]  0001 
88154ad1c000 882753487c18 c054693e
  Oct 15 14:10:13 compute2 kernel: [12845630.496332]  882753487cb8 
c0542fd9 88154ad1c048 88154ad1c038
  Oct 15 14:10:13 compute2 kernel: [12845630.508296]  7f8be3e0 
7f8bdc40 c9003aea6008 c9003ae9c008
  Oct 15 14:10:13 compute2 kernel: [12845630.520294] Call Trace:
  Oct 15 14:10:13 compute2 kernel: [12845630.526169]  [] 
kvm_unmap_rmapp+0xe/0x20 [kvm]
  Oct 15 14:10:13 compute2 kernel: [12845630.532063]  [] 
kvm_handle_hva_range+0x119/0x170 [kvm]
  Oct 15 14:10:13 compute2 kernel: [12845630.537896]  [] 
kvm_unmap_hva_range+0x17/0x20 [kvm]
 

[Kernel-packages] [Bug 1798083] Re: Nvidia doesn't work after I upgraded to 4.19rc8

[Brad Figg]

** Tags added: cscc

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

Title:
  Nvidia doesn't work after I upgraded to 4.19rc8

Status in linux package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I upgraded my linux to 4.19rc8

  When I logged in ubuntu,It says `Error parsing nvidia-settings: lines[i] is 
undefined`
  Then I checked,nvidia doesn't work.
  $ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.


  gnome-shell[5862]: error: Error parsing nvidia-settings: lines[i] is
  undefined

  nvidia-settings-autostart.desktop[6862]: ERROR: NVIDIA driver is not loaded
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying enabled 
displays on GPU 0 (Missing Extension).
  nvidia-settings-autostart.desktop[6862]: ERROR: Error querying connected 
displays on GPU 0 (Missing Extension).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 20:18:27 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (5 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
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-041900rc8-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  Symptom: display
  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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798083/+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 1797432] Re: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, Left] No sound at all

[Brad Figg]

** Tags added: cscc

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out,
  Left] No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Headphone jack stopped working. Speakers do work. Nevermind issue was
  on my end not sure how to close bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 11 13:12:34 2018
  InstallationDate: Installed on 2018-01-05 (279 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   james  2649 F...m pulseaudio
   /dev/snd/controlC0:  james  2649 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Black Headphone Out, 
Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1797432/+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 1798109] Re: Rendering is lagging

[Brad Figg]

** Tags added: cscc

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

Title:
  Rendering is lagging

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

Bug description:
  
  I installed correct nvidia 390 for my card.But it seems less efficient than 
using Intel integrated graphic card.Window movement and web page scrolling 
aren't smooth.That's vary annoying.If I use Intel card,everything is smooth.

  nvidia-smi says 'Volatile GPU-Util' is not zero.But is it really using
  nvidia for rendering?

  -- Edited

  
  Fixed a lot by removing nvidia indicator.

  But it's still not as smooth as Windows.

  
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 16 22:22:45 2018
  InstallationDate: Installed on 2018-10-10 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 3058 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  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
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 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.
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/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.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (7 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 

[Kernel-packages] [Bug 1801347] Re: ubuntu_vfat_stress will pass even with error reported by stress-ng

[Brad Figg]

** Tags added: cscc

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

Title:
  ubuntu_vfat_stress will pass even with error reported by stress-ng

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The test will pass even with stress-ng complaining about "No space
  left on device", not sure if this is an expected behaviour, but it
  might be confusing to testers.

   stress-ng: info:  [36588] dispatching hogs: 2 hdd, 2 lockf, 2 seek, 2 aio, 2 
dentry, 2 dir, 2 fallocate, 2 fstat, 2 lease, 2 open, 2 rename, 2 chdir, 2 
rename
   stress-ng: fail:  [36609] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36623] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36611] stress-ng-hdd: read failed, errno=28 (No space 
left on device)
   stress-ng: error: [36588] process 36611 (stress-ng-hdd) terminated with an 
error, exit status=1 (stress-ng core failure)
   stress-ng: error: [36588] process [36609] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: error: [36588] process [36623] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: info:  [36588] unsuccessful run completed in 14.35s
   stress-ng: info:  [36588] stressor   bogo ops real time  usr time  sys 
time   bogo ops/s   bogo ops/s
   stress-ng: info:  [36588]   (secs)(secs)
(secs)   (real time) (usr+sys time)
   stress-ng: info:  [36588] hdd   16391  7.39  0.44  
6.44  2218.21  2382.41
   stress-ng: info:  [36588] lockf131604 10.16  0.05 
12.43 12947.00 10545.19
   stress-ng: info:  [36588] seek1987284 10.17  1.33 
10.40195448.06169418.93
   stress-ng: info:  [36588] aio2496 10.15  0.00  
0.00   245.83 0.00
   stress-ng: info:  [36588] dentry  171 10.42  0.00  
0.6116.41   280.33
   stress-ng: info:  [36588] dir2539 14.09  0.00 
15.40   180.14   164.87
   stress-ng: info:  [36588] fallocate   170 10.17  0.04  
5.3516.7131.54
   stress-ng: info:  [36588] fstat  2147 10.00  0.02  
0.26   214.64  7667.86
   stress-ng: info:  [36588] lease66 10.14  0.61  
5.15 6.5111.46
   stress-ng: info:  [36588] open1434208 10.11  0.44 
12.20141807.28113465.82
   stress-ng: info:  [36588] rename 6526 10.01  0.00  
2.94   651.86  2219.73
   stress-ng: info:  [36588] rename 6820 10.00  0.00  
2.49   681.85  2738.96
   stress-ng: info:  [36588] for a 14.35s run time:
   stress-ng: info:  [36588] 114.80s available CPU time
   stress-ng: info:  [36588]   3.05s user time   (  2.66%)
   stress-ng: info:  [36588]  75.50s system time ( 65.77%)
   stress-ng: info:  [36588]  78.55s total time  ( 68.43%)
   stress-ng: info:  [36588] load average: 17.49 10.98 4.90
   Stress-ng stressor failed, error: 2
   umounting vfat /mnt/vfat-test-29590
   umounting tmpfs /mnt/vfat-test-29590
   


   Completed

   Kernel issues: NONE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-139-generic 4.4.0-139.165
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Fri Nov  2 08:20:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1797546] Re: dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

[Brad Figg]

** Tags added: cscc

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

Title:
  dev test in ubuntu_stress_smoke_test cause kernel oops on T-3.13

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  SRU Request [Trusty]

  == Justification ==

  It is possible to cause an oops in drm with an unimplemented ioctl call
  with the following reproducer run as root:

  #include 
  #include 
  #include 
  #include 

  int main(void)
  {
  int ptnum, fd;

  fd = open("/dev/dri/card0", O_RDWR);
  return ioctl(fd, TIOCGPTN, );
  }

  == Fix ==

  A backport (minor wiggle) of upstream commit 1539fb9bd405
  ("drm: fix NULL pointer access by wrong ioctl").

  == Testing ==

  Run the reproducer above as root, it will trip the oops. With the fix
  this oops won't occur.

  == Regression Potential ==

  Minimal, this is an upstream fix to this exact issue and has been in
  the kernel since 3.16

  


  This is a bare-metal node running with 3.13.0-160 amd64 kernel.

  The dev test will cause kernel oops:
    dev STARTING
    dev RETURNED 0
    dev FAILED (kernel oopsed)
    [  222.555784] BUG: unable to handle kernel NULL pointer dereference at 
  (null)
    [  222.564547] IP: [] memset+0x9/0xb0
    [  222.570101] PGD 8004586b1067 PUD 45784a067 PMD 0
    [  222.575767] Oops: 0002 [#1] SMP
    [  222.579385] Modules linked in: macvlan(+) dccp_ipv4 dccp ghash_generic 
salsa20_generic salsa20_x86_64 camellia_generic camellia_aesni_avx2 
camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64 cast6_generic 
cast_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic 
twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 
twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt 
x86_pkg_temp_thermal coretemp kvm_intel kvm joydev lpc_ich shpchp mac_hid 
hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel igb 
aesni_intel aes_x86_64 i915_bdw dca lrw gf128mul ahci intel_ips glue_helper ptp 
ablk_helper drm_kms_helper cryptd pps_core libahci i2c_algo_bit drm video
    [  222.647301] CPU: 0 PID: 23159 Comm: stress-ng-dev Not tainted 
3.13.0-160-generic #210-Ubuntu
    [  222.647301] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS 
S1200RP.86B.03.02.0003.070120151022 07/01/2015
    [  222.647302] task: 880035bf1800 ti: 880453b6 task.ti: 
880453b6
    [  222.647303] RIP: 0010:[]  [] 
memset+0x9/0xb0
    [  222.647306] RSP: 0018:880453b61db8  EFLAGS: 00010246
    [  222.647306] RAX: 88045af55d00 RBX: 880455538000 RCX: 
0004
    [  222.647307] RDX: 0004 RSI:  RDI: 

    [  222.647307] RBP: 880453b61ec0 R08: 81c43740 R09: 

    [  222.647308] R10: a002f260 R11: 880453b61e10 R12: 
880455f07a00
    [  222.647309] R13: 0004 R14:  R15: 
0030
    [  222.647310] FS:  7f64909ef700() GS:88047040() 
knlGS:
    [  222.647310] CS:  0010 DS:  ES:  CR0: 80050033
    [  222.647311] CR2:  CR3: 000458904000 CR4: 
00360770
    [  222.647312] DR0:  DR1:  DR2: 

    [  222.647312] DR3:  DR6: fffe0ff0 DR7: 
0400
    [  222.647313] Stack:
    [  222.647314]  a0010c05 88040001 a003ace4 
00410086
    [  222.647316]  880453b61e10 880453b61e10 a00185d0 
643054506240
    [  222.647317]  7f64909ebce0 88040004 a002f260 

    [  222.647317] Call Trace:
    [  222.647329]  [] ? drm_ioctl+0x4d5/0x630 [drm]
    [  222.647337]  [] ? drm_agp_info_ioctl+0x10/0x10 [drm]
    [  222.647341]  [] do_vfs_ioctl+0x2e3/0x4d0
    [  222.647343]  [] ? SYSC_newfstat+0x25/0x30
    [  222.647344]  [] SyS_ioctl+0x81/0xa0
    [  222.647347]  [] system_call_fastpath+0x26/0x2b
    [  222.647359] Code: 16 fe 66 44 89 1f 66 44 89 54 17 fe eb 0c 48 83 fa 01 
72 06 44 8a 1e 44 88 1f c3 90 90 90 90 90 90 90 49 89 f9 40 88 f0 48 89 d1  
aa 4c 89 c8 c3 0f 1f 84 00 00 00 00 00 0f 1f 84 00 00 00 00
    [  222.647360] RIP  [] memset+0x9/0xb0
    [  222.647361]  RSP 
    [  222.647361] CR2: 
    [  222.647363] ---[ end trace f74524d41bff5843 ]---
    [  222.678166] program stress-ng-dev is using a deprecated SCSI ioctl, 
please convert it to SG_IO
    [  222.678173] program stress-ng-dev is using a deprecated SCSI ioctl, 
please convert it to SG_IO
    [  

[Kernel-packages] [Bug 1797563] Re: Xenial update: 4.4.156 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Xenial update: 4.4.156 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.4.156 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * staging: android: ion: fix ION_IOC_{MAP,SHARE} use-after-free
  * net: bcmgenet: use MAC link status for fixed phy
  * qlge: Fix netdev features configuration.
  * tcp: do not restart timewait timer on rst reception
  * vti6: remove !skb->ignore_df check from vti6_xmit()
  * cifs: check if SMB2 PDU size has been padded and suppress the warning
  * hfsplus: don't return 0 when fill_super() failed
  * hfs: prevent crash on exit from failed search
  * fork: don't copy inconsistent signal handler state to child
  * reiserfs: change j_timestamp type to time64_t
  * hfsplus: fix NULL dereference in hfsplus_lookup()
  * fat: validate ->i_start before using
  * scripts: modpost: check memory allocation results
  * mm/fadvise.c: fix signed overflow UBSAN complaint
  * fs/dcache.c: fix kmemcheck splat at take_dentry_name_snapshot()
  * ipvs: fix race between ip_vs_conn_new() and ip_vs_del_dest()
  * mfd: sm501: Set coherent_dma_mask when creating subdevices
  * platform/x86: asus-nb-wmi: Add keymap entry for lid flip action on UX360
  * irqchip/bcm7038-l1: Hide cpu offline callback when building for !SMP
  * net/9p: fix error path of p9_virtio_probe
  * powerpc: Fix size calculation using resource_size()
  * s390/dasd: fix hanging offline processing due to canceled worker
  * scsi: aic94xx: fix an error code in aic94xx_init()
  * PCI: mvebu: Fix I/O space end address calculation
  * dm kcopyd: avoid softlockup in run_complete_job
  * staging: comedi: ni_mio_common: fix subdevice flags for PFI subdevice
  * selftests/powerpc: Kill child processes on SIGINT
  * smb3: fix reset of bytes read and written stats
  * SMB3: Number of requests sent should be displayed for SMB3 not just CIFS
  * powerpc/pseries: Avoid using the size greater than RTAS_ERROR_LOG_MAX.
  * btrfs: replace: Reset on-disk dev stats value after replace
  * btrfs: relocation: Only remove reloc rb_trees if reloc control has been
initialized
  * btrfs: Don't remove block group that still has pinned down bytes
  * debugobjects: Make stack check warning more informative
  * x86/pae: use 64 bit atomic xchg function in native_ptep_get_and_clear
  * kbuild: make missing $DEPMOD a Warning instead of an Error
  * Revert "ARM: imx_v6_v7_defconfig: Select ULPI support"
  * enic: do not call enic_change_mtu in enic_probe
  * Fixes: Commit cdbf92675fad ("mm: numa: avoid waiting on freed migrated 
pages")
  * genirq: Delay incrementing interrupt count if it's disabled/pending
  * irqchip/gic-v3-its: Recompute the number of pages on page size change
  * irqchip/gicv3-its: Fix memory leak in its_free_tables()
  * irqchip/gicv3-its: Avoid cache flush beyond ITS_BASERn memory size
  * irqchip/gic-v3: Add missing barrier to 32bit version of gic_read_iar()
  * irqchip/gic: Make interrupt ID 1020 invalid
  * ovl: rename is_merge to is_lowest
  * ovl: override creds with the ones from the superblock mounter
  * ovl: proper cleanup of workdir
  * sch_htb: fix crash on init failure
  * sch_multiq: fix double free on init failure
  * sch_hhf: fix null pointer dereference on init failure
  * sch_netem: avoid null pointer deref on init failure
  * sch_tbf: fix two null pointer dereferences on init failure
  * mei: me: allow runtime pm for platform with D0i3
  * ASoC: wm8994: Fix missing break in switch
  * btrfs: use correct compare function of dirty_metadata_bytes
  * Linux 4.4.156

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797563/+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 1801250] Re: [AEP] mprotect clobbers _PAGE_DEVMAP

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP] mprotect clobbers _PAGE_DEVMAP

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  [PATCH] mm: Preserve _PAGE_DEVMAP across mprotect() calls

  Commits:
  4628a64591e6

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801250/+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 1801253] Re: [AEP]copy_to_iter_mcsafe() send incorrect param to check_copy_size()

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]copy_to_iter_mcsafe() send incorrect param to check_copy_size()

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  copy_to_iter_mcsafe() is passing in the is_source parameter as "false" to 
check_copy_size(). This is different than what copy_to_iter() does. Also, the 
addr parameter passed to check_copy_size() is the source so therefore we should 
be passing in "true" instead.

  Commits:
  dfb06cba8c73

  Target Kernel: 4.19
  Target Release:  19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801253/+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 1801256] Re: [AEP]nd_region region12: allocation underrun: 0x0 of 0x1980000000 bytes

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]nd_region region12: allocation underrun: 0x0 of 0x198000
  bytes

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  This was seen by a customer when trying to create a namespace:

  [1124286.189585] nd_region region12: allocation underrun: 0x0 of 0x198000 
bytes
  [1124286.189604] ---[ cut here ]---
  [1124286.189611] WARNING: CPU: 59 PID: 145367 at 
drivers/nvdimm/namespace_devs.c:913 size_store+0x85e/0x870
  [1124286.189612] Modules linked in: hfsplus hfs isofs binfmt_misc vtsspp(OE) 
sep4_1(OE) sepint4_1(OE) socperf2_0(OE) pax(OE) ip6t_rpfilter ip6t_REJECT 
nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge 
stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw 
iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc vfat 
fat dax_pmem nd_pmem device_dax nd_btt intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf ipmi_ssif 
iTCO_wdt iTCO_vendor_support ioatdma mei_me joydev i2c_i801 lpc_ich shpchp
  [1124286.189645] mei wmi dca ipmi_msghandler nfit acpi_power_meter acpi_pad 
xfs libcrc32c ast i2c_algo_bit drm_kms_helper ttm crc32c_intel nvme i40e drm 
nvme_core ptp pps_core [last unloaded: vtsspp]
  [1124286.189656] CPU: 59 PID: 145367 Comm: ndctl Tainted: G OE 
4.14.18-300.fc27.x86_64 #1
  [1124286.189657] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS 
SE5C620.86B.01.00.0694.120620170818 12/06/2017
  [1124286.189658] task: 98a64a088000 task.stack: a9840e52
  [1124286.189660] RIP: 0010:size_store+0x85e/0x870
  [1124286.189661] RSP: 0018:a9840e523d38 EFLAGS: 00010282
  [1124286.189662] RAX: 0042 RBX: 9991b119a008 RCX: 

  [1124286.189663] RDX:  RSI: 98a67efd6a38 RDI: 
98a67efd6a38
  [1124286.189663] RBP: 9991b15a3fc0 R08: 0760 R09: 
0004
  [1124286.189664] R10: f171b9971c40 R11: 0001 R12: 

  [1124286.189665] R13: 9991b515f000 R14: 9991b515f3d0 R15: 
a9840e523d9e
  [1124286.189666] FS: 7f402255c780() GS:98a67efc() 
knlGS:
  [1124286.189667] CS: 0010 DS:  ES:  CR0: 80050033
  [1124286.189667] CR2: 563419868608 CR3: 002ef88ac001 CR4: 
007606e0
  [1124286.189668] DR0:  DR1:  DR2: 

  [1124286.189669] DR3:  DR6: fffe0ff0 DR7: 
0400
  [1124286.189669] PKRU: 5554
  [1124286.189670] Call Trace:
  [1124286.189677] ? __kmalloc+0x199/0x210
  [1124286.189680] kernfs_fop_write+0x10b/0x190
  [1124286.189683] __vfs_write+0x36/0x180
  [1124286.189687] ? selinux_file_permission+0x116/0x130
  [1124286.189691] ? security_file_permission+0x3c/0xb0
  [1124286.189692] vfs_write+0xad/0x1a0
  [1124286.189694] SyS_write+0x52/0xc0
  [1124286.189698] do_syscall_64+0x75/0x180
  [1124286.189701] entry_SYSCALL_64_after_hwframe+0x21/0x86
  [1124286.189703] RIP: 0033:0x7f40218517a4
  [1124286.189703] RSP: 002b:7ffcc1c0e948 EFLAGS: 0246 ORIG_RAX: 
0001
  [1124286.189704] RAX: ffda RBX: 000e RCX: 
7f40218517a4
  [1124286.189705] RDX: 000e RSI: 7ffcc1c0e990 RDI: 
0003
  [1124286.189706] RBP: 7ffcc1c0e990 R08: 000a R09: 

  [1124286.189706] R10:  R11: 0246 R12: 
0003
  [1124286.189707] R13:  R14: 7f402255c6b0 R15: 
0002
  [1124286.189708] Code: 48 85 ed 75 04 49 8b 6d 10 4c 89 ef e8 2c a7 fc ff 4c 
8b 44 24 38 4c 89 e1 48 89 ea 48 89 c6 48 c7 c7 a8 7b 0f 95 e8 5d 74 b5 ff <0f> 
ff e9 bb fd ff ff e8 f6 9c af ff 66 0f 1f 44 00 00 0f 1f 44 
  [1124286.189729] --[ end trace 39a78a4960fc8601 ]--

  Commits:
  12e3129e29b4 1e687220ef2d

  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801256/+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 1798330] Re: Support Edge Gateway's WIFI LED

[Brad Figg]

** Tags added: cscc

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

Title:
  Support Edge Gateway's WIFI LED

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

Bug description:
  == Impact ==
  The WIFI LED of Marvell 88W8897 is not enabled by default (there's no code 
for controlling LED in mwifiex). It is requested to be ON and OFF when the 
radio is on and off accordingly.

  == Fix ==
  The LEDs are connected to GPIO pins on the Marvell WiFi/Bluetooth combo 
module, thus they can only be controlled via firmware.

  == Test Case ==
  # ifconfig wlan0 [on|off]
  and see if the LEDs work properly.

  == Risk of Regression ==
  PCI sub IDs of the host bridge are used to determine if we're really running 
on an Edge Gateway, and we already have these patches in Xenial kernels quite a 
while. Risk should be reasonably low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798330/+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 1797654] Re: hns3: autoneg settings get lost on down/up

[Brad Figg]

** Tags added: cscc

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

Title:
  hns3: autoneg settings get lost on down/up

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

Bug description:
  [Impact]
  If a user manually disables autonegotiation, that setting will be lost if the 
link is toggled.

  [Test Case]
  sudo ethtool -s enp125s0f2 speed 100 duplex half autoneg off
  After this, "ethtool enp125s0f2" will show:
Advertised auto-negotiation: No
  If you then run:
  sudo ifconfig enp125s0f2 down; sudo ifconfig enp125s0f2 up, then ethtool will 
show:
Advertised auto-negotiation: Yes

  [Fix]
  b01b7cf19bf4a net: hns3: Fix for information of phydev lost problem when 
down/up

  [Regression Risk]
  Restricted to a single SoC on which the fix was explicitly tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797654/+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 1801254] Re: [AEP]EDAC may report the wrong DIMM when patrol scrubber finds an error

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]EDAC may report the wrong DIMM when patrol scrubber finds an
  error

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  Facebook reported that on Broadwell systems EDAC sometimes reports the wrong 
DIMM for a memory error found by the patrol scrubber.

  The issue is rooted in h/w that only provides a 4KB page aligned
  address for the error in this case. This means that the EDAC driver
  will point at the DIMM matching offset 0x0 in the 4KB page, but
  because of interleaving across channels and ranks the actual DIMM
  involved may be different if the error is on some other cache line
  within the page.

  Fix: We can't actually get EDAC to point to the right DIMM because we
  don't know the offset within the page. But we should fix EDAC to say
  "I don't know" instead of pointing to the wrong DIMM.

  We can check the MCi_MISC register to know whether the address was
  cache-line aligned or page aligned. Bits 5:0 give the least
  significant bit that is valid. So a value of 6 is for cache line
  aligned (8 on Optane DC equipped systems that bundle 4 processor cache
  lines into a single Optane DC cache line). It will be 12 for patrol
  scrubber reported errors.

  Once we know we have a problem we should see how much information we
  can provide just from the "mce" structure passed the the EDAC driver.

  1) We can get the socket from looking at m->extcup (the CMCI from the
  patrol scrubber will have been delivered to a logical CPU on the same
  socket)

  2) The memory controller number. I think the m->bank will tell us this
  Need to check in the EDS for IvyBridge, Haswell and Broadwell.

  3) The channel number. Low bits of MCi_STATUS.MCACOD should provide
  this.

  Facebook said that for many of their systems this should be enough for
  them (as a lot of systems only have one DIMM populated per channel).

  Note that Skylake is allegedly unaffected as the patrol scrubber
  should provide a cacheline aligned address. We should test and confirm

  Commits:
  8489b17ce29d9a35a36c08bbea93cdce4c98a6ad
  Target Kernel: 4.20
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801254/+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 1797713] Re: 18.10 update: keyboard backlight stopped working

[Brad Figg]

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

** Tags added: cscc

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

Title:
  18.10 update: keyboard backlight stopped working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've updated to the Ubuntu 18.10 beta release. Since then my keyboard
  backlight stopped working. The function keys still display the
  keyboard backlight brightness control icon on screen, but it doesn't
  change.

  I'm using kernel 4.18.0-10-generic.

  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-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mweimann  15267 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Oct 13 20:18:22 2018
  InstallationDate: Installed on 2017-12-20 (296 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5a09 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX331UN
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=e117a09c-da54-44f2-b41a-8cd26a874ac4 ro quiet splash 
nouveau.modeset=0 nouveau.runpm=0 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX331UN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX331UN
  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.:bvrUX331UN.301:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX331UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX331UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX331UN
  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/1797713/+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 1801248] Re: [AEP]Add micro-optimizations to dax page pinning

[Brad Figg]

** Tags added: cscc

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

Title:
  [AEP]Add micro-optimizations to dax page pinning

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description
  We think we can save a few cpu cycles when pinning user pages mmap'ed from 
dax by avoiding the memtype_lock when looking up the memory type, and cache the 
dev_pagemap structure so we don't need to search the radix tree for it for 
every page.

  Commits:
  df06b37ffe5a442503b7095b77b0a970df515459 
  Target Kernel: 4.19
  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801248/+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 1798061] Re: open14 in ubuntu_ltp_syscalls failed with T (Power8)

[Brad Figg]

** Tags added: cscc

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

Title:
  open14 in ubuntu_ltp_syscalls failed with T (Power8)

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

Bug description:
  This issue can only be reproduced on Power8 node:

  <<>>
  tag=open14 stime=1539683773
  cmdline="open14"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  open14  1  TBROK  :  open14.c:58: open() failed: errno=EINVAL(22): 
Invalid argument
  open14  2  TBROK  :  open14.c:58: Remaining cases broken
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-160-generic 3.13.0-160.210
  ProcVersionSignature: User Name 3.13.0-160.210-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-160-generic ppc64le
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CurrentDmesg:
   [   75.881756] tg3 0003:05:00.0 enP3p5s0f0: Link is up at 1000 Mbps, full 
duplex
   [   75.881762] tg3 0003:05:00.0 enP3p5s0f0: Flow control is off for TX and 
off for RX
   [   75.881765] tg3 0003:05:00.0 enP3p5s0f0: EEE is disabled
   [   75.881788] IPv6: ADDRCONF(NETDEV_CHANGE): enP3p5s0f0: link becomes ready
   [  656.832585] LTP: starting open14
  Date: Tue Oct 16 09:56:22 2018
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.08 0.07 0.08 1/1034 3981
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3027 00:11:28789 0 EOF
   2: POSIX  ADVISORY  WRITE 3146 00:11:90135 0 EOF
   3: POSIX  ADVISORY  WRITE 3176 00:11:95241 0 EOF
   4: FLOCK  ADVISORY  WRITE 3093 00:11:89096 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.13.0-160-generic (buildd@bos02-ppc64el-007) (gcc 
version 4.8.4 (User Name 4.8.4-2ubuntu1~14.04.4) ) #210-User Name SMP Mon Sep 
24 18:06:36 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-160-generic N/A
   linux-backports-modules-3.13.0-160-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798061/+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 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags

[Brad Figg]

** Tags added: cscc

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

Title:
  [Ubuntu] qdio: reset old sbal_state flags

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==

  Description: qdio: reset old sbal_state flags

  Symptom:
     af_iucv socket using HiperSockets may stall.
  Problem:
     When allocating a new AOB fails, handle_outbound() is
  still capable of transmitting the selected buffer
  (just without async completion).
  But if a previous transfer on this queue slot used
  async completion, its sbal_state flags field is still set
  to QDIO_OUTBUF_STATE_FLAG_PENDING.
  So when the upper layer driver sees this stale flag, it
  expects an async completion that never happens.
  Solution:
     Unconditionally clear the buffer's flags field.

  == Fix ==

  64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
  sbal_state flags")

  == Regression Potential ==

  Low, because:
  - s390x only
  - further limited to qeth driver (OSA Express networking)
  - changes are limited to two files and 6 lines
     - arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
     - drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
  - error was identified at IBM/customer, fix was created there and tested 
upfront
  - (changes are upstream in 4.20 (according to bug description,
 but in 4.19 according to 'git tag'),
 hence will make it automatically into 'disco')

  == Test Case ==

  Test case / reproduction:
  Error inject and then simulate out-of-memory situation.

  __

  Description:  qdio: reset old sbal_state flags

  Symptom:  af_iucv socket using HiperSockets may stall.

  Problem:  When allocating a new AOB fails, handle_outbound() is
    still capable of transmitting the selected buffer
    (just without async completion).
    But if a previous transfer on this queue slot used
    async completion, its sbal_state flags field is still set
    to QDIO_OUTBUF_STATE_FLAG_PENDING.
    So when the upper layer driver sees this stale flag, it
    expects an async completion that never happens.

  Solution: Unconditionally clear the buffer's flags field.

  Reproduction: Error inject, simulating out-of-memory.

  kernel 4.20
  Upstream-ID:  64e03ff72623b8c2ea89ca3cb660094e019ed4ae

  Canonical , please provide this fix for all Releases in Service
  Ubuntu 18.10, 18.04 and 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1801686/+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 1801986] Re: Cosmic update: 4.18.14 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Cosmic update: 4.18.14 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.18.14 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * perf/core: Add sanity check to deal with pinned event failure
  * mm: migration: fix migration of huge PMD shared pages
  * mm, thp: fix mlocking THP page with migration enabled
  * mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly
  * KVM: VMX: check for existence of secondary exec controls before accessing
  * blk-mq: I/O and timer unplugs are inverted in blktrace
  * pstore/ram: Fix failure-path memory leak in ramoops_init
  * clocksource/drivers/timer-atmel-pit: Properly handle error cases
  * fbdev/omapfb: fix omapfb_memory_read infoleak
  * mmc: core: Fix debounce time to use microseconds
  * mmc: slot-gpio: Fix debounce time to use miliseconds again
  * mac80211: allocate TXQs for active monitor interfaces
  * drm/amdgpu: Fix vce work queue was not cancelled when suspend
  * drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
  * drm: fix use-after-free read in drm_mode_create_lease_ioctl()
  * x86/vdso: Fix asm constraints on vDSO syscall fallbacks
  * selftests/x86: Add clock_gettime() tests to test_vdso
  * x86/vdso: Only enable vDSO retpolines when enabled and supported
  * x86/vdso: Fix vDSO syscall fallback asm constraint regression
  * Revert "UBUNTU: SAUCE: PCI: Reprogram bridge prefetch registers on resume"
  * PCI: Reprogram bridge prefetch registers on resume
  * mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys
  * PM / core: Clear the direct_complete flag on errors
  * dm mpath: fix attached_handler_name leak and dangling hw_handler_name 
pointer
  * dm cache metadata: ignore hints array being too small during resize
  * dm cache: fix resize crash if user doesn't reload cache table
  * xhci: Add missing CAS workaround for Intel Sunrise Point xHCI
  * usb: xhci-mtk: resume USB3 roothub first
  * USB: serial: simple: add Motorola Tetra MTP6550 id
  * USB: serial: option: improve Quectel EP06 detection
  * USB: serial: option: add two-endpoints device-id flag
  * usb: cdc_acm: Do not leak URB buffers
  * tty: Drop tty->count on tty_reopen() failure
  * of: unittest: Disable interrupt node tests for old world MAC systems
  * powerpc: Avoid code patching freed init sections
  * powerpc/lib: fix book3s/32 boot failure due to code patching
  * ARC: clone syscall to setp r25 as thread pointer
  * f2fs: fix invalid memory access
  * tipc: call start and done ops directly in __tipc_nl_compat_dumpit()
  * ucma: fix a use-after-free in ucma_resolve_ip()
  * ubifs: Check for name being NULL while mounting
  * rds: rds_ib_recv_alloc_cache() should call alloc_percpu_gfp() instead
  * ath10k: fix scan crash due to incorrect length calculation
  * Linux 4.18.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801986/+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 1801893] Re: Xenial update: 4.4.161 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Xenial update: 4.4.161 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.4.161 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * mm/vmstat.c: skip NR_TLB_REMOTE_FLUSH* properly
  * fbdev/omapfb: fix omapfb_memory_read infoleak
  * x86/vdso: Fix asm constraints on vDSO syscall fallbacks
  * x86/vdso: Fix vDSO syscall fallback asm constraint regression
  * PCI: Reprogram bridge prefetch registers on resume
  * mac80211: fix setting IEEE80211_KEY_FLAG_RX_MGMT for AP mode keys
  * PM / core: Clear the direct_complete flag on errors
  * dm cache: fix resize crash if user doesn't reload cache table
  * xhci: Add missing CAS workaround for Intel Sunrise Point xHCI
  * USB: serial: simple: add Motorola Tetra MTP6550 id
  * of: unittest: Disable interrupt node tests for old world MAC systems
  * ext4: always verify the magic number in xattr blocks
  * cgroup: Fix deadlock in cpu hotplug path
  * ath10k: fix use-after-free in ath10k_wmi_cmd_send_nowait
  * powerpc/fadump: Return error when fadump registration fails
  * ARC: clone syscall to setp r25 as thread pointer
  * ucma: fix a use-after-free in ucma_resolve_ip()
  * ubifs: Check for name being NULL while mounting
  * tcp: increment sk_drops for dropped rx packets
  * tcp: use an RB tree for ooo receive queue
  * tcp: fix a stale ooo_last_skb after a replace
  * tcp: free batches of packets in tcp_prune_ofo_queue()
  * tcp: call tcp_drop() from tcp_data_queue_ofo()
  * tcp: add tcp_ooo_try_coalesce() helper
  * ath10k: fix scan crash due to incorrect length calculation
  * ebtables: arpreply: Add the standard target sanity check
  * Linux 4.4.161

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801893/+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 1802082] Re: Cosmic update: 4.18.15 upstream stable release

[Brad Figg]

** Tags added: cscc

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

Title:
  Cosmic update: 4.18.15 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.18.15 upstream stable release
     from git://git.kernel.org/

  The following patches will be applied:
  * bnxt_en: Fix TX timeout during netpoll.
  * bnxt_en: free hwrm resources, if driver probe fails.
  * bonding: avoid possible dead-lock
  * ip6_tunnel: be careful when accessing the inner header
  * ip_tunnel: be careful when accessing the inner header
  * ipv4: fix use-after-free in ip_cmsg_recv_dstaddr()
  * ipv6: take rcu lock in rawv6_send_hdrinc()
  * net: dsa: bcm_sf2: Call setup during switch resume
  * net: hns: fix for unmapping problem when SMMU is on
  * net: ipv4: update fnhe_pmtu when first hop's MTU changes
  * net/ipv6: Display all addresses in output of /proc/net/if_inet6
  * netlabel: check for IPV4MASK in addrinfo_get
  * net: mvpp2: Extract the correct ethtype from the skb for tx csum offload
  * net: mvpp2: fix a txq_done race condition
  * net: sched: Add policy validation for tc attributes
  * net: sched: cls_u32: fix hnode refcounting
  * net: systemport: Fix wake-up interrupt race during resume
  * net/usb: cancel pending work when unbinding smsc75xx
  * qlcnic: fix Tx descriptor corruption on 82xx devices
  * qmi_wwan: Added support for Gemalto's Cinterion ALASxx WWAN interface
  * rtnl: limit IFLA_NUM_TX_QUEUES and IFLA_NUM_RX_QUEUES to 4096
  * sctp: update dst pmtu with the correct daddr
  * team: Forbid enslaving team device to itself
  * tipc: fix flow control accounting for implicit connect
  * udp: Unbreak modules that rely on external __skb_recv_udp() availability
  * net: qualcomm: rmnet: Skip processing loopback packets
  * net: qualcomm: rmnet: Fix incorrect allocation flag in transmit
  * net: qualcomm: rmnet: Fix incorrect allocation flag in receive path
  * tun: remove unused parameters
  * tun: initialize napi_mutex unconditionally
  * tun: napi flags belong to tfile
  * net: stmmac: Fixup the tail addr setting in xmit path
  * net/packet: fix packet drop as of virtio gso
  * net: dsa: bcm_sf2: Fix unbind ordering
  * net/mlx5e: Set vlan masks for all offloaded TC rules
  * net: aquantia: memory corruption on jumbo frames
  * net/mlx5: E-Switch, Fix out of bound access when setting vport rate
  * bonding: pass link-local packets to bonding master also.
  * bonding: fix warning message
  * net: stmmac: Rework coalesce timer and fix multi-queue races
  * nfp: avoid soft lockups under control message storm
  * bnxt_en: don't try to offload VLAN 'modify' action
  * net-ethtool: ETHTOOL_GUFO did not and should not require CAP_NET_ADMIN
  * net: phy: phylink: fix SFP interface autodetection
  * sfp: fix oops with ethtool -m
  * tcp/dccp: fix lockdep issue when SYN is backlogged
  * inet: make sure to grab rcu_read_lock before using ireq->ireq_opt
  * net: dsa: b53: Keep CPU port as tagged in all VLANs
  * rtnetlink: Fail dump if target netnsid is invalid
  * bnxt_en: Fix VNIC reservations on the PF.
  * net: ipv4: don't let PMTU updates increase route MTU
  * net/mlx5: Check for SQ and not RQ state when modifying hairpin SQ
  * bnxt_en: Fix enables field in HWRM_QUEUE_COS2BW_CFG request
  * bnxt_en: get the reduced max_irqs by the ones used by RDMA
  * net/ipv6: Remove extra call to ip6_convert_metrics for multipath case
  * net/ipv6: stop leaking percpu memory in fib6 info
  * net: mscc: fix the frame extraction into the skb
  * qed: Fix shmem structure inconsistency between driver and the mfw.
  * r8169: fix network stalls due to missing bit TXCFG_AUTO_FIFO
  * r8169: set RX_MULTI_EN bit in RxConfig for 8168F-family chips
  * vxlan: fill ttl inherit info
  * ASoC: dapm: Fix NULL pointer deference on CODEC to CODEC DAIs
  * ASoC: max98373: Added speaker FS gain cotnrol register to volatile.
  * ASoC: rt5514: Fix the issue of the delay volume applied again
  * selftests: android: move config up a level
  * selftests: kselftest: Remove outdated comment
  * ASoC: max98373: Added 10ms sleep after amp software reset
  * ASoC: wm8804: Add ACPI support
  * ASoC: sigmadsp: safeload should not have lower byte limit
  * ASoC: q6routing: initialize data correctly
  * selftests: add headers_install to lib.mk
  * selftests/efivarfs: add required kernel 

[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

[Brad Figg]

** Tags added: cscc

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+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 1801878] Re: NULL pointer dereference at 0000000000000020 when access dst_orig->ops->family in function xfrm_lookup_with_ifid()

[Brad Figg]

** Tags added: cscc

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

Title:
  NULL pointer dereference at 0020 when access
  dst_orig->ops->family in function  xfrm_lookup_with_ifid()

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

Bug description:
  [Impact]

  NULL pointer access happens when trying to access dst_orig->ops.

  The function xfrm_lookup() calls xfrm_lookup_with_ifid() and there is 
  a line inside trying to access dst_orig->ops and it's exactly where the 
  panicing happens: 

  u16 family = dst_orig->ops->family;

  As you can see that the symbol offset of ops is about 32(0x20) which 
  definitely is the error message shows in the kern.log: 

  [267265.140511] BUG: unable to handle kernel NULL pointer dereference 
  at 0020 

  struct dst_entry { 
  struct callback_head callback_head; /* 0 16 */ 
  struct dst_entry * child; /* 16 8 */ 
  struct net_device * dev; /* 24 8 */ 
  struct dst_ops * ops; <-- /* 32 8 */ 

  The oops:
  BUG: unable to handle kernel NULL pointer dereference at 0020 
  IP: xfrm_lookup+0x31/0x870 
  PGD 0 P4D 0 
  Oops:  [#1] SMP PTI 
  CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.15.0-36-generic 
#39~16.04.1-Ubuntu 
  Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 
  RIP: 0010:xfrm_lookup+0x31/0x870 
  RSP: 0018:98b542343a48 EFLAGS: 00010246 
  RAX:  RBX: 98b542343ac8 RCX:  
  RDX: 98b542343ac8 RSI:  RDI: b39e4380 
  RBP: 98b542343ab8 R08: 0002 R09:  
  R10: 0020 R11: 7fb56465 R12:  
  R13: b39e4380 R14: 0002 R15: b39e4380 
  FS: () GS:98b54234() knlGS: 
  CS: 0010 DS:  ES:  CR0: 80050033 
  CR2: 0020 CR3: 0004ed40a001 CR4: 001606e0 
  DR0:  DR1:  DR2:  
  DR3:  DR6: fffe0ff0 DR7: 0400 
  Call Trace: 
   
  ? __xfrm_policy_check+0x41d/0x630 
  __xfrm_route_forward+0xa3/0x110 
  ip_forward+0x38c/0x470 
  ? ip_route_input_noref+0x28/0x40 
  ip_rcv_finish+0x124/0x410 
  ip_rcv+0x28e/0x3b0 
  ? inet_del_offload+0x40/0x40 
  __netif_receive_skb_core+0x879/0xba0 
  ? __skb_checksum+0x188/0x2c0 
  __netif_receive_skb+0x18/0x60 
  ? __netif_receive_skb+0x18/0x60 
  netif_receive_skb_internal+0x37/0xe0 
  ? tcp4_gro_complete+0x86/0x90 
  napi_gro_complete+0x73/0x90 
  dev_gro_receive+0x2ee/0x5c0 
  napi_gro_frags+0xa3/0x230 
  ena_clean_rx_irq+0x486/0x7c0 [ena] 
  ena_io_poll+0x41d/0x770 [ena] 
  net_rx_action+0x265/0x3b0 
  __do_softirq+0xf5/0x28f 
  irq_exit+0xb8/0xc0 
  xen_evtchn_do_upcall+0x30/0x40 
  xen_hvm_callback_vector+0x84/0x90 

  [Fix]
  The patch tries to avoid the NULL pointer access before the line
  mentioned "dst_orig->ops->family" in function __xfrm_route_forward.
  And the function calling sequence is: 

  __xfrm_route_forward -> xfrm_lookup -> xfrm_lookup_with_ifid

  It definitely avoids the NULL pointer access in the 
  xfrm_lookup_with_ifid.

  commit c5e39ef174ad34cd4d26af3a83bdbccddd2ad9d6
  Author: Steffen Klassert 
  Date:   Tue Sep 11 10:31:15 2018 +0200

  xfrm: Fix NULL pointer dereference when skb_dst_force clears the 
dst_entry.
  
  Since commit 222d7dbd258d ("net: prevent dst uses after free")
  skb_dst_force() might clear the dst_entry attached to the skb.
  The xfrm code don't expect this to happen, so we crash with
  a NULL pointer dereference in this case. Fix it by checking
  skb_dst(skb) for NULL after skb_dst_force() and drop the packet
  in cast the dst_entry was cleared.
  
  [Test]
  The fix has been tested in the production system with the IPSec enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801878/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

[Brad Figg]

** Tags added: cscc

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1805835] Re: Infinite aer_status and aer_agent output in tty

[Brad Figg]

** Tags added: cscc

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

Title:
  Infinite aer_status and aer_agent output in tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A fresh install of Ubuntu Server 18.04.1. It keeps printing the same
  messages to the terminal:

  [ 1475.344317] pci :00:00.0: aer_status: 0x0080, aer_mask: 0x
  [ 1475.345586] pci :00:00.0: aer_layer=Data Link Layer, 
aer_agent=Receiver ID

  The same two lines, over and over (except number in brackets), every
  10 minutes or so. After logging in it still keeps printing them. The
  interval is not constant, sometimes longer, sometimes shorter.

  Performed apt-get update and dist-upgrade, rebooted. Now 0 packages
  pending update, but the above output is not affected.

  Googled to find that AER is supposed to report PCIe errors. However
  the above output does not look like an error. Seems like some log
  output?

  Naturally this randomly appearing output is extremely annoying and
  interferes with the normal use of the console. My guess is that a
  normally functioning install should have nothing of this sort, hence
  this bug-report.

  Any fix or workaround that will silence this output will be
  appreciated greatly.

  Let me know if any additional information or tests are needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-39-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Thu Nov 29 12:07:18 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: ASUSTeK COMPUTER INC. WS-C621E-SAGE Series
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=linux
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcFB:
   0 astdrmfb
   1 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=e2d7aa3a-f3be-11e8-9d19-0c9d925bd3e9 ro maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: WS-C621E-SAGE Series
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0801:bd04/30/2018:svnASUSTeKCOMPUTERINC.:pnWS-C621E-SAGESeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnWS-C621E-SAGESeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Server
  dmi.product.name: WS-C621E-SAGE Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805835/+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 1806396] Re: lis3lv02d: unknown sensor type 0x0

[Brad Figg]

** Tags added: cscc

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

Title:
  lis3lv02d: unknown sensor type 0x0

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

Bug description:
  Hello,

  dmesg:
  [   15.684425] lis3lv02d: unknown sensor type 0x0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2647 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2647 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 10:22:33 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806396/+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 1805631] Re: Freeze when usb-data-collision with usb-mouse

[Brad Figg]

** Tags added: cscc

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805631/+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 1806412] Re: EXT4-fs error (device sda7): ext4_iget:4831: inode #8663569: comm REINDEX: bad extra_isize 8306 (inode size 256)

[Brad Figg]

** Tags added: cscc

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

Title:
  EXT4-fs error (device sda7): ext4_iget:4831: inode #8663569: comm
  REINDEX: bad extra_isize 8306 (inode size 256)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  [   96.230966] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663569: 
comm REINDEX: bad extra_isize 8306 (inode size 256)
  [   96.259863] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663570: 
comm REINDEX: bad extra_isize 3912 (inode size 256)
  [   96.328165] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663571: 
comm REINDEX: bad extra_isize 2 (inode size 256)
  [   96.372998] EXT4-fs error (device sda7): ext4_iget:4851: inode #8663572: 
comm REINDEX: checksum invalid
  [   96.451608] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663573: 
comm REINDEX: bad extra_isize 3288 (inode size 256)
  [   96.549207] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663574: 
comm REINDEX: bad extra_isize 38448 (inode size 256)
  [   96.584675] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663575: 
comm REINDEX: bad extra_isize 67 (inode size 256)
  [   96.628344] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663576: 
comm REINDEX: bad extra_isize 34544 (inode size 256)
  [   96.754517] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663577: 
comm REINDEX: bad extra_isize 16592 (inode size 256)
  [   96.916746] EXT4-fs error (device sda7): ext4_iget:4831: inode #8663578: 
comm REINDEX: bad extra_isize 29555 (inode size 256)
  [  101.261135] EXT4-fs error: 55 callbacks suppressed

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-7-generic 4.19.0-7.8
  ProcVersionSignature: Ubuntu 4.19.0-7.8-generic 4.19.5
  Uname: Linux 4.19.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2623 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 11:32:18 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-7-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-7-generic N/A
   linux-backports-modules-4.19.0-7-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806412/+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 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B

[Brad Figg]

** Tags added: cscc

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have this error and arbitrary freezes on the system

  My System:

  Hardware:
  Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 
0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate 
ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: 
Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 
Gigabit + Intel Device a370

  Software:
  OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, 
Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, 
Screen Resolution: 1920x1980

  dmesg output:

  Dec  2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, 
min 894, max 899, scanline start 845, end 903
  Dec  2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup 
failure, AE_NOT_FOUND (20170831/psargs-364)
  Dec  2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized 
for Method [BRT6]
  Dec  2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method 
[BRT6]:  (2 arguments defined for method invocation)
  Dec  2 16:08:50 G5 kernel: [ 2534.448073]   Arg0:   a83faa08 
   Integer 0001
  Dec  2 16:08:50 G5 kernel: [ 2534.448076]   Arg1:   35246c42 
   Integer 
  Dec  2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution 
failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution 
failed \EV5, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution 
failed \SMEE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution 
failed \SMIE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution 
failed \NEVT, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution 
failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, 
min 894, max 899, scanline start 864, end 14
  Dec  2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b 
changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  instantcrush   1622 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G5 5587
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0M2MWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5587
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+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 1806177] Re: Display resolution with later kernels

[Brad Figg]

** Tags added: cscc

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

Title:
  Display resolution with later kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware - thinkpad T430, 3rd gen integrated graphics, external LG
  ultrawide monitor (2560x1080). OS linux mint. Any kernel later than
  4.5.7. will not correctly identify the monitor resolution only giving
  1920x1080 as the max. No problems with the earlier kernels.

  Further information:
  https://forums.linuxmint.com/viewtopic.php?f=46=280143

  While not hard fact, it would appear that other older thinkpads, e.g.
  X220 and 4k screens have the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806177/+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 1806604] Re: linux: -proposed tracker

[Brad Figg]

** Tags added: cscc

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

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-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 04. December 2018 10:09 UTC
  reason:
prepare-package: Version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806604/+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 1809872] Re: btrfs send / receive command with -f argument position in btrfs_kernel_fixes is causing failures on B

[Brad Figg]

** Tags added: cscc

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

Title:
  btrfs send / receive command with -f argument position in
  btrfs_kernel_fixes is causing failures on B

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This issue is different from bug 1809869.

  Test failed with:
  ERROR: unable to resolve -f
  And:
  btrfs receive: too many arguments

  This patch does exist in Bionic kernel tree.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  ERROR: unable to resolve -f
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  ERROR: unable to resolve -f
  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   e6351943-c767-4339-b662-609e80dae55b
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE  read the stream from FILE instead of stdin
  -e   terminate after receiving an  marker in the 
stream.
   Without this option the receiver side terminates only in 
case
   of an error on end of file.
  -C|--chroot  confine the process to  using chroot
  -E|--max-errors NERR
   terminate as soon as NERR errors occur while
   stream processing commands from the stream.
   Default value is 1. A value of 0 means no limit.
  -m ROOTMOUNT the root mount point of the destination filesystem.
   If /proc is not accessible, use this to tell us where
   this file system is mounted.
  --dump   dump stream metadata, one line per operation,
   does not require the MOUNT parameter

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE

[Kernel-packages] [Bug 1805793] Re: [19.04 FEAT] qeth: Full-blown TCP Segmentation Offload

[Brad Figg]

** Tags added: cscc

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

Title:
  [19.04 FEAT] qeth: Full-blown TCP Segmentation Offload

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  As of now, qeth only supports TCP Segmentation Offload (TSO) for IPv4 in 
Layer3 devices. 
  This feature extends the existing support to IPv6, and adds support for TSO 
in both IP variants for Layer2.

  Improved performance via improved TCP Segmentation offload also
  extended to IPv6 and for layer 2 devices

  kernel 4.20:
  Git-Commit: will follow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805793/+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 1806395] Re: i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535)

[Brad Figg]

** Tags added: cscc

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

Title:
  i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report
  (67/65535)

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

Bug description:
  Hello,

  dmesg:
  [   15.337762] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report 
(67/65535)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2647 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2647 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  3 10:19:29 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806395/+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 1809848] Re: package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to install/upgrade: installed linux-image-4.15.0-42-generic package pre-removal script subprocess returned

[Brad Figg]

** Tags added: cscc

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A bug reported on latest Ubuntu download.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp intel_cstate intel_rapl_perf 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core mei_me mei ie31200_edac lpc_ich mac_hid shpchp 
radeon r8169 i2c_i801 pata_acpi
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1207 F pulseaudio
booboo 1686 F pulseaudio
   /dev/snd/controlC1:  gdm1207 F pulseaudio
booboo 1686 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Dec 26 18:46:53 2018
  DuplicateSignature:
   package:linux-image-4.15.0-42-generic:4.15.0-42.45
   Removing linux-image-4.15.0-42-generic (4.15.0-42.45) ...
   E: Aborting removal of the running kernel
   dpkg: error processing package linux-image-4.15.0-42-generic (--remove):
installed linux-image-4.15.0-42-generic package pre-removal script 
subprocess returned error exit status 1
  ErrorMessage: installed linux-image-4.15.0-42-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=7c572848-7310-43e5-960f-3b8791821190
  InstallationDate: Installed on 2014-08-09 (1600 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-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.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to 
install/upgrade: installed linux-image-4.15.0-42-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-09-08 (109 days ago)
  dmi.bios.date: 07/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd07/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809848/+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 1805248] Re: Regression: hinic performance degrades over time

[Brad Figg]

** Tags added: cscc

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

Title:
  Regression: hinic performance degrades over time

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Bug 1800664 introduced checksum offload and TSO support for HiNIC adapters. 
While that did improve performance in short iperf runs, longer runs were later 
found to show a significant regression in performance:
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800664/comments/3

  [Test Case]
  iperf -c 192.168.99.1 -P5

  [Fix]
  Revert the offending patch.

  [Regression Risk]
  This is reverting a patch, returning the driver to 18.10 GA behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805248/+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 1809870] Re: 2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes failed on B

[Brad Figg]

** Tags added: cscc

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

Title:
  2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes
  failed on B

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Test failed on Bionic, and this patch does exist in Bionic kernel
  tree.

  
  Invoking test 2365dd3ca02bbb6d3412404482e1d85752549953

  fix 2365dd3ca02bbb6d3412404482e1d85752549953

  btrfs: undo sysfs when open_ctree() fails

  reproducer:
  mkfs.btrfs -f /dev/sdb &&mount /dev/sdb /btrfs &&btrfs dev add -f 
/dev/sdc /btrfs &&umount /btrfs &&wipefs -a /dev/sdc &&mount -o 
degraded /dev/sdb /btrfs
  //above mount fails so try with RO
  mount -o degraded,ro /dev/sdb /btrfs

  --
  sysfs: cannot create duplicate filename 
'/fs/btrfs/3f48c79e-5ed0-4e87-b189-86e749e503f4'
  ::

  Performing full device TRIM /dev/loop1 (512.00MiB) ...
  mount -o degraded /dev/loop0 
/tmp/mnt-2365dd3ca02bbb6d3412404482e1d85752549953 was expected to fail

  FAIL: 2365dd3ca02bbb6d3412404482e1d85752549953 (ret=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 18:17 seq
   crw-rw 1 root audio 116, 33 Dec 20 18:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Thu Dec 27 07:34:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809870/+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 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change

[Brad Figg]

** Tags added: cscc

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

Title:
  hwclock test failed on Power9 due to 0.x sec differences / time out
  waiting for time change

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The hwclock test will fail on the Power9 system "baltar" due to a
  <0.02 second difference.

  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in 
run_once
  raise error.TestFail("Failed to set hwclock back to Warthog's birthday. 
Output of hwclock is '%s'" % date)
  TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock 
is '2004-10-20 04:09:59.582146+'

  Didn't see this on Power8 boxes

  Sometimes it will fail because "time out waiting for time change" on the same 
node:
  $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
  hwclock: Timed out waiting for time change.

  Workaround for these is to add "sleep 1".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 03:45 seq
   crw-rw 1 root audio 116, 33 Nov  8 03:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Thu Nov  8 06:03:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3544 00:17:582 0 EOF
   2: POSIX  ADVISORY  WRITE 1798 00:17:338 0 EOF
   3: POSIX  ADVISORY  WRITE 3603 00:17:576 0 EOF
   4: FLOCK  ADVISORY  WRITE 3535 00:17:564 0 EOF
   5: FLOCK  ADVISORY  WRITE 4081 00:17:481 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-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)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 1)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

  -- Firmware information on Baltar --
  pnor: P9DSU20190404_IBM_prod_sign.pnor
  bmc: SMT_P9_206.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+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 1806649] Re: Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter

[Brad Figg]

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

** Tags added: cscc

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

Title:
  Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter

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

Bug description:
  Hello,

  Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2784 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 07:41:10 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806649/+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 1805344] Re: SRU: Fix kernel xhci hang when resume from S3

[Brad Figg]

** Tags added: cscc

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

Title:
  SRU: Fix kernel xhci hang when resume from S3

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

Bug description:
  [Impact]
  On some thinkpad laptops, Realtek USB3.0 Card Reader [0bda:0328] reports 
wrong port status on
  Cannon lake PCH USB3.1 xHCI [8086:a36d] after resume from S3, then kernel 
hang.

  [Fix]
  Restrict the USB2 resume status check in USB2 roothub to fix hang issue.

  [Test Case]
  Suspend/resume 30 times OK.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  These 2 patches are already Cc: sta...@vger.kernel.org, cosmic and
  future kernel will get these 2 patches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805344/+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 1806534] Re: Fix USB2 device wrongly detected as USB1

[Brad Figg]

** Tags added: cscc

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

Title:
  Fix USB2 device wrongly detected as USB1

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

Bug description:
  [Impact]
  USB 2 device may come up as USB 1 if a connection to a USB 1 device is 
followed by another connection to a USB 2 device, the link will come up as USB 
1 for the USB 2 device.

  [Test Case]
  Insert 2 USB devices and they shall appear on lsusb with correct address

  [Fix]
  11644a76 xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 
Soc

  [Regression Risk]
  It only affect device PCI_VENDOR_ID_CAVIUM:0x9026 and 
PCI_VENDOR_ID_BROADCOM:0x9026.
  Low regression to other device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806534/+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 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

[Brad Figg]

** Tags added: cscc

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

Title:
  Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless
  Network Adapter

Status in HWE Next:
  Fix Released
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
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  It drains power more than 0.5 Watt after power off(S5) the machine with 
QCA9377 wifi card. The power consumption should be lower than 0.5 Watt, or it 
won't pass E-star 7.

  [Fix]
  Qualcomm provides this fix, and the power consumption becomes 0.23 Watt at 
S5. This fix doesn't submit to upstream yet, Qualcomm is still working on it.

  [Test]
  Verified on Dell machines, it works.

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805607/+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 1806232] Re: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing

[Brad Figg]

** Tags added: cscc

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

Title:
  Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing

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

Bug description:
  There is screen tearing on the left side of the screen, and it's
  especially apparent when there's motion on the entire screen. This is
  happening on Ubuntu 18.10 on an Asus T102HA with an Atom x5 Cherry
  Trail.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 00:59:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1400]
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK COMPUTER INC. T102HA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=6d4342e4-1f2b-42ea-850e-63e34c955cd3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T102HA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T102HA
  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.:bvrT102HA.204:bd07/18/2016:svnASUSTeKCOMPUTERINC.:pnT102HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT102HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T102HA
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806232/+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 1809847] Re: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

[Brad Figg]

** Tags added: cscc

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

Title:
  Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel 
4.15.0.43.64.
  There is no interrupt while plug/unplug Ethernet cable after S3, so it looks 
like a regression after 4.15.0-33.36.

  [Fix]
  Check changelog and found there are 2 commits introduced from 4.15.0-35.38 
might be suspicious
    * r8169 no internet after suspending (LP: #1779817)
  - r8169: don't use MSI-X on RTL8168g
  - r8169: don't use MSI-X on RTL8106e
  And check the upstream log and found the 2 MSI-X commits had been all 
reverted, since below commit claims it fixes the MSI-X interrupt issue which is 
already in Bionic kernel.
     083874549fdf PCI: Reprogram bridge prefetch registers on resume
  So, I reverted the 2 MSI-X commits and found the Ethernet works again after 
S3.

  [Regression Potential]
  Low, the 2 disable MSI-X commits are workarounds, and now we have proper way 
to fix the issue, so it should be fine to revert them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1809847/+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 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.

[Brad Figg]

** Tags added: cscc

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

Title:
  FN+F3/F4 does not modify keyboard backlight brightness.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  acpi_listen does not output anything to terminal when pressing key
  combination.

  Keyboard backlight has worked on older versions (I believe 18.04 or
  earlier.)

  I can manually toggle with:

  echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness

  for varying degrees of brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  disco
  Uname: Linux 4.19.6-041906-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  duck   3632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (22 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  Tags:  disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  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.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  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/1806343/+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 1806569] Re: linux: 4.4.0-141.167 -proposed tracker

[Brad Figg]

** Tags added: cscc

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

Title:
  linux: 4.4.0-141.167 -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-dnu 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 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Released
  phase-changed: Friday, 21. December 2018 04:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Stalled -- snap-release-to-stable is neither "Fix 
Released"
  nor "Invalid" (Confirmed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806569/+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 1809888] Re: zed air sound problem.

[Brad Figg]

** Tags added: cscc

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

Title:
  zed air sound problem.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  No sound on device

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 27 14:26:46 2018
  InstallationDate: Installed on 2018-12-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809888/+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 1802812] Re: Ubuntu 18.04 (4.15.0-38-generic) 'suspend' seizing up and requiring a forced shutdown

[Brad Figg]

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

** Tags added: cscc

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

Title:
  Ubuntu 18.04 (4.15.0-38-generic) 'suspend' seizing up and requiring a
  forced shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today after a fresh install of the latest 18.04 LTS on my dell
  precision m4800; my laptop fails when i try to suspend. Either i
  choose to suspend via fn+f1, or closing the lid, or using the comman
  line; first i have a black screen and then the system seizes up. (not
  on sleep state) esc, power button, ctrl+alt+f1,f2 etc. nothing works.
  I have to force power off by holding the power button.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  suleyman   1201 F pulseaudio
   /dev/snd/controlC0:  suleyman   1201 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 12 05:09:25 2018
  HibernationDevice: RESUME=UUID=d4445414-6a4b-43fe-8d99-ec6cf57b951a
  InstallationDate: Installed on 2018-11-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Precision M4800
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=bd1aa1f5-5a41-4d1c-a57b-83ef5e861879 ro acpi_osi=Linux 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0V5GVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd02/01/2018:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  suleyman   1201 F pulseaudio
   /dev/snd/controlC0:  suleyman   1201 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=d4445414-6a4b-43fe-8d99-ec6cf57b951a
  InstallationDate: Installed on 2018-11-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Precision M4800
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=bd1aa1f5-5a41-4d1c-a57b-83ef5e861879 ro acpi_osi=Linux 
mem_sleep_default=deep
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0V5GVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd02/01/2018:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802812/+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 1806093] Re: linux-oracle: 4.15.0-1006.6 -proposed tracker

[Brad Figg]

** Tags added: cscc

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

Title:
  linux-oracle: 4.15.0-1006.6 -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-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed 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-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1006.6 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: 1803592

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806093/+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