[Kernel-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

[Maxim Smih]

I do not know how to divide the core into parts

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3.

  There is no such problem with the 4.15 kernel. It happens that after
  90 seconds it turns off. And with a new core, he writes that he will
  turn off after 90 seconds, but he will not turn off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.

   enp7s4 нет беспроводных расширений.

   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:

  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

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

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

[Kernel-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

[Kai-Heng Feng]

It use different method to reboot.

But if it's a regression (once worked on 4.15), can you please perform a
kernel bisection?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3.

  There is no such problem with the 4.15 kernel. It happens that after
  90 seconds it turns off. And with a new core, he writes that he will
  turn off after 90 seconds, but he will not turn off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.

   enp7s4 нет беспроводных расширений.

   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:

  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

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

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

[Kernel-packages] [Bug 1847599] Re: After upgrading to Ubuntu 19.10 the boot hangs on HP EliteDesk 800 G2 SFF

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/

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

Title:
  After upgrading to Ubuntu 19.10 the boot hangs on HP EliteDesk 800 G2
  SFF

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 19.10 the boot hangs, I had to start the
  system with the previous kernel linux-modules-extra-5.0.0-31-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-13-generic 5.3.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caiofior   1818 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Oct 10 14:15:57 2019
  HibernationDevice: RESUME=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro quiet splash 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.183
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caiofior   1981 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 19.10
  HibernationDevice: RESUME=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  generic/471 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   generic/471- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad)
   --- tests/generic/471.out  2019-10-16 10:51:13.156701083 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad
  2019-10-16 12:16:10.594841128 +
   @@ -2,12 +2,10 @@
pwrite: Resource temporarily unavailable
wrote 8388608/8388608 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
   -RWF_NOWAIT time is within limits.
   +pwrite: Resource temporarily unavailable 
   +(standard_in) 1: syntax error
   +RWF_NOWAIT took  seconds
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad'
  to see the entire diff) 

  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out
2019-10-16 10:51:13.156701083 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad
 2019-10-16 12:16:10.594841128 +
  @@ -2,12 +2,10 @@
   pwrite: Resource temporarily unavailable
   wrote 8388608/8388608 bytes at offset 0
   XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
  -RWF_NOWAIT time is within limits.
  +pwrite: Resource temporarily unavailable
  +(standard_in) 1: syntax error
  +RWF_NOWAIT took  seconds
   :  aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa  
   *
  -0020:  bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  
  -*
  -0030:  aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa  
  -*
   read 8388608/8388608 bytes at offset 0
   XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)

  Syslog:
  Oct 16 12:16:09 kili ubuntu: run xfstest generic/471
  Oct 16 12:16:09 kili kernel: [ 5708.949736] run fstests generic/471 at 
2019-10-16 12:16:09
  Oct 16 12:16:10 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 12:16:10 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 12:16:10 kili kernel: [ 5710.290570] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 12:16:10 kili kernel: [ 5710.290573] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 12:16:10 kili kernel: [ 5710.294454] BTRFS info (device sdb1): 
enabling ssd optimizations

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
   crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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 Oct 17 04:55:08 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S2600WTT
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
  dmi.board.asset.tag: Base Board Asset Tag
  

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  generic/526 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   generic/526- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad)
   --- tests/generic/526.out  2019-10-16 10:51:13.160701040 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad
  2019-10-16 12:22:09.159460024 +
   @@ -1,5 +1,11 @@
QA output created by 526
   -File fname1 data after power failure: bar
   -File fname2 data after power failure: foo
   -File fname3 data after power failure: foo
   -File fname4 data after power failure: hello
   +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
   +cat: 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such 
file or directory
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad'
  to see the entire diff)

  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out
2019-10-16 10:51:13.160701040 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad
 2019-10-16 12:22:09.159460024 +
  @@ -1,5 +1,11 @@
   QA output created by 526
  -File fname1 data after power failure: bar
  -File fname2 data after power failure: foo
  -File fname3 data after power failure: foo
  -File fname4 data after power failure: hello
  +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: 
No such file or directory
  +File fname1 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: 
No such file or directory
  +File fname2 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: 
No such file or directory
  +File fname3 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname4: 
No such file or directory
  +File fname4 data after power failure: 
  +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted.


  Syslog:
  Oct 16 12:22:07 kili ubuntu: run xfstest generic/526
  Oct 16 12:22:07 kili kernel: [ 6067.439549] run fstests generic/526 at 
2019-10-16 12:22:07
  Oct 16 12:22:07 kili kernel: [ 6067.619112] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 12:22:07 kili kernel: [ 6067.619114] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 12:22:07 kili kernel: [ 6067.623160] BTRFS info (device sdb1): 
enabling ssd optimizations
  Oct 16 12:22:07 kili kernel: [ 6067.740396] BTRFS: device fsid 
25391e30-6097-48bd-8db6-b92d0184c072 devid 1 transid 5 /dev/sdb2
  Oct 16 12:22:08 kili kernel: [ 6067.845454] BTRFS info (device dm-0): disk 
space caching is enabled
  Oct 16 12:22:08 kili kernel: [ 6067.845456] BTRFS info (device dm-0): has 
skinny extents
  Oct 16 12:22:08 kili kernel: [ 6067.845458] BTRFS info (device dm-0): 
flagging fs with big metadata feature
  Oct 16 12:22:08 kili kernel: [ 6067.851055] BTRFS info (device dm-0): 
enabling ssd optimizations
  Oct 16 12:22:08 kili kernel: [ 6067.851555] BTRFS info (device dm-0): 
checking UUID tree
  Oct 16 12:22:08 kili kernel: [ 6068.206539] BTRFS info (device dm-0): device 
fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved 
old:/dev/mapper/flakey-test new:/dev/dm-0
  Oct 16 12:22:08 kili kernel: [ 6068.207207] BTRFS info (device dm-0): device 
fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved old:/dev/dm-0 
new:/dev/mapper/flakey-test
  Oct 16 12:22:08 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 12:22:08 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 12:22:08 kili 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  generic/527 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   generic/527- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad)
   --- tests/generic/527.out  2019-10-16 10:51:13.160701040 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
  2019-10-16 12:22:10.315449210 +
   @@ -1,4 +1,9 @@
QA output created by 527
   -File fname1 data after power failure: bar
   -File fname2 data after power failure: foo
   -File fname3 data after power failure: foo
   +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
   +cat: 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such 
file or directory
   +File fname1 data after power failure: 
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad'
  to see the entire diff) 

  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
2019-10-16 10:51:13.160701040 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
 2019-10-16 12:22:10.315449210 +
  @@ -1,4 +1,9 @@
   QA output created by 527
  -File fname1 data after power failure: bar
  -File fname2 data after power failure: foo
  -File fname3 data after power failure: foo
  +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: 
No such file or directory
  +File fname1 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: 
No such file or directory
  +File fname2 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: 
No such file or directory
  +File fname3 data after power failure: 
  +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted.

  Syslog:
  Oct 16 12:22:09 kili ubuntu: run xfstest generic/527
  Oct 16 12:22:09 kili kernel: [ 6068.948341] run fstests generic/527 at 
2019-10-16 12:22:09
  Oct 16 12:22:09 kili kernel: [ 6069.125238] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 12:22:09 kili kernel: [ 6069.125240] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 12:22:09 kili kernel: [ 6069.132427] BTRFS info (device sdb1): 
enabling ssd optimizations
  Oct 16 12:22:09 kili kernel: [ 6069.246264] BTRFS: device fsid 
6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 transid 5 /dev/sdb2
  Oct 16 12:22:09 kili multipathd[1484]: dm-0: remove map (uevent)
  Oct 16 12:22:09 kili kernel: [ 6069.353749] BTRFS info (device dm-0): disk 
space caching is enabled
  Oct 16 12:22:09 kili kernel: [ 6069.353751] BTRFS info (device dm-0): has 
skinny extents
  Oct 16 12:22:09 kili kernel: [ 6069.353752] BTRFS info (device dm-0): 
flagging fs with big metadata feature
  Oct 16 12:22:09 kili kernel: [ 6069.358172] BTRFS info (device dm-0): 
enabling ssd optimizations
  Oct 16 12:22:09 kili kernel: [ 6069.359885] BTRFS info (device dm-0): 
checking UUID tree
  Oct 16 12:22:09 kili kernel: [ 6069.677202] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved 
old:/dev/mapper/flakey-test new:/dev/dm-0
  Oct 16 12:22:09 kili kernel: [ 6069.677914] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/dm-0 
new:/dev/mapper/flakey-test
  Oct 16 12:22:09 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 12:22:09 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 12:22:10 kili kernel: [ 6069.781083] BTRFS info (device dm-0): disk 
space caching is enabled
  Oct 16 12:22:10 kili kernel: [ 6069.781085] BTRFS info 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  generic/527 from ubuntu_xfstests_btrfs failed on D

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue found on node amd64 node "kili"

   generic/527- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad)
   --- tests/generic/527.out  2019-10-16 10:51:13.160701040 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
  2019-10-16 12:22:10.315449210 +
   @@ -1,4 +1,9 @@
QA output created by 527
   -File fname1 data after power failure: bar
   -File fname2 data after power failure: foo
   -File fname3 data after power failure: foo
   +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
   +cat: 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such 
file or directory
   +File fname1 data after power failure: 
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad'
  to see the entire diff) 

  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
2019-10-16 10:51:13.160701040 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
 2019-10-16 12:22:10.315449210 +
  @@ -1,4 +1,9 @@
   QA output created by 527
  -File fname1 data after power failure: bar
  -File fname2 data after power failure: foo
  -File fname3 data after power failure: foo
  +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: 
No such file or directory
  +File fname1 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: 
No such file or directory
  +File fname2 data after power failure: 
  +cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: 
No such file or directory
  +File fname3 data after power failure: 
  +umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted.

  Syslog:
  Oct 16 12:22:09 kili ubuntu: run xfstest generic/527
  Oct 16 12:22:09 kili kernel: [ 6068.948341] run fstests generic/527 at 
2019-10-16 12:22:09
  Oct 16 12:22:09 kili kernel: [ 6069.125238] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 12:22:09 kili kernel: [ 6069.125240] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 12:22:09 kili kernel: [ 6069.132427] BTRFS info (device sdb1): 
enabling ssd optimizations
  Oct 16 12:22:09 kili kernel: [ 6069.246264] BTRFS: device fsid 
6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 transid 5 /dev/sdb2
  Oct 16 12:22:09 kili multipathd[1484]: dm-0: remove map (uevent)
  Oct 16 12:22:09 kili kernel: [ 6069.353749] BTRFS info (device dm-0): disk 
space caching is enabled
  Oct 16 12:22:09 kili kernel: [ 6069.353751] BTRFS info (device dm-0): has 
skinny extents
  Oct 16 12:22:09 kili kernel: [ 6069.353752] BTRFS info (device dm-0): 
flagging fs with big metadata feature
  Oct 16 12:22:09 kili kernel: [ 6069.358172] BTRFS info (device dm-0): 
enabling ssd optimizations
  Oct 16 12:22:09 kili kernel: [ 6069.359885] BTRFS info (device dm-0): 
checking UUID tree
  Oct 16 12:22:09 kili kernel: [ 6069.677202] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved 
old:/dev/mapper/flakey-test new:/dev/dm-0
  Oct 16 12:22:09 kili kernel: [ 6069.677914] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/dm-0 
new:/dev/mapper/flakey-test
  Oct 16 12:22:09 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 12:22:09 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 12:22:10 kili kernel: [ 6069.781083] BTRFS info (device dm-0): disk 
space caching is enabled
  Oct 16 12:22:10 kili kernel: [ 6069.781085] BTRFS info (device dm-0): has 
skinny extents
  Oct 16 12:22:10 kili kernel: [ 6069.785329] BTRFS info (device dm-0): 
enabling ssd optimizations
  Oct 16 12:22:10 kili 

[Kernel-packages] [Bug 1847151] Re: Touchpad not detected

[Paul S. Strauss]

Seems to be fixed in 5.0.0-32

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 5.0.0-31.33-generic 5.0.21 (from 5.0.0-29),
  my laptop's touchpad is no longer detected as a device. This is a new
  problem.

  Contents of /proc/bus/input/devices attached.

  Following directions from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss3353 F pulseaudio
   /dev/snd/controlC0:  pss3353 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct  7 14:14:13 2019
  InstallationDate: Installed on 2019-04-24 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=76a404c8-db6d-4ab3-8614-86dbef6fdda8 ro "acpi_osi=!acpi_osi=Windows 
2009" quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-29 (161 days ago)
  dmi.bios.date: 10/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17B7IMS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17B7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17B7IMS.10F:bd10/03/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS73 Stealth 8RF
  dmi.product.sku: 17B7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-04-25T10:50:34.601584

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

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

[Kernel-packages] [Bug 1848428] [NEW] generic/526 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 generic/526- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad)
 --- tests/generic/526.out  2019-10-16 10:51:13.160701040 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad
  2019-10-16 12:22:09.159460024 +
 @@ -1,5 +1,11 @@
  QA output created by 526
 -File fname1 data after power failure: bar
 -File fname2 data after power failure: foo
 -File fname3 data after power failure: foo
 -File fname4 data after power failure: hello
 +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
 +cat: 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such 
file or directory
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad'
  to see the entire diff)


$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/526.out
  2019-10-16 10:51:13.160701040 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/526.out.bad
   2019-10-16 12:22:09.159460024 +
@@ -1,5 +1,11 @@
 QA output created by 526
-File fname1 data after power failure: bar
-File fname2 data after power failure: foo
-File fname3 data after power failure: foo
-File fname4 data after power failure: hello
+mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system 
call failed: File exists.
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No 
such file or directory
+File fname1 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No 
such file or directory
+File fname2 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No 
such file or directory
+File fname3 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname4: No 
such file or directory
+File fname4 data after power failure: 
+umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted.


Syslog:
Oct 16 12:22:07 kili ubuntu: run xfstest generic/526
Oct 16 12:22:07 kili kernel: [ 6067.439549] run fstests generic/526 at 
2019-10-16 12:22:07
Oct 16 12:22:07 kili kernel: [ 6067.619112] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 12:22:07 kili kernel: [ 6067.619114] BTRFS info (device sdb1): has 
skinny extents
Oct 16 12:22:07 kili kernel: [ 6067.623160] BTRFS info (device sdb1): enabling 
ssd optimizations
Oct 16 12:22:07 kili kernel: [ 6067.740396] BTRFS: device fsid 
25391e30-6097-48bd-8db6-b92d0184c072 devid 1 transid 5 /dev/sdb2
Oct 16 12:22:08 kili kernel: [ 6067.845454] BTRFS info (device dm-0): disk 
space caching is enabled
Oct 16 12:22:08 kili kernel: [ 6067.845456] BTRFS info (device dm-0): has 
skinny extents
Oct 16 12:22:08 kili kernel: [ 6067.845458] BTRFS info (device dm-0): flagging 
fs with big metadata feature
Oct 16 12:22:08 kili kernel: [ 6067.851055] BTRFS info (device dm-0): enabling 
ssd optimizations
Oct 16 12:22:08 kili kernel: [ 6067.851555] BTRFS info (device dm-0): checking 
UUID tree
Oct 16 12:22:08 kili kernel: [ 6068.206539] BTRFS info (device dm-0): device 
fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved 
old:/dev/mapper/flakey-test new:/dev/dm-0
Oct 16 12:22:08 kili kernel: [ 6068.207207] BTRFS info (device dm-0): device 
fsid 25391e30-6097-48bd-8db6-b92d0184c072 devid 1 moved old:/dev/dm-0 
new:/dev/mapper/flakey-test
Oct 16 12:22:08 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 12:22:08 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 12:22:08 kili kernel: [ 6068.292235] BTRFS info (device dm-0): disk 
space caching is enabled
Oct 16 12:22:08 kili kernel: [ 6068.292237] BTRFS info (device dm-0): has 
skinny extents
Oct 16 12:22:08 kili kernel: [ 6068.295626] BTRFS info (device dm-0): enabling 
ssd optimizations
Oct 16 12:22:08 kili kernel: [ 6068.297102] BTRFS: error (device dm-0) in 
btrfs_replay_log:2304: errno=-17 Object already exists (Failed to recover log 
tree)
Oct 16 12:22:08 kili kernel: [ 6068.337404] BTRFS error (device dm-0): 
open_ctree failed
Oct 16 12:22:09 kili multipathd[1484]: flakey-test: adding map
Oct 16 12:22:09 kili multipathd[1484]: 

[Kernel-packages] [Bug 1848360] Re: [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full brightness after wake up

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Invalid

** Summary changed:

- [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full brightness 
after wake up
+ [AMD Raven Ridge] Screen always returns to full brightness after wake up

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: xserver-xorg-video-amdgpu (Ubuntu)

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

Title:
  [AMD Raven Ridge] Screen always returns to full brightness after wake
  up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Every time when I open up my lid of my laptop, and wake up my system
  from sleeping,the screen will return to full brightness.Either I press
  the brightness - or + button,the brightness will back to normal
  immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 00:05:56 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:380c]
  InstallationDate: Installed on 2019-09-28 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN30WW:bd07/04/2018:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.sku: LENOVO_MT_81BR_BU_idea_FM_ideapad 720S-13ARR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1848429] [NEW] generic/527 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 generic/527- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad)
 --- tests/generic/527.out  2019-10-16 10:51:13.160701040 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
  2019-10-16 12:22:10.315449210 +
 @@ -1,4 +1,9 @@
  QA output created by 527
 -File fname1 data after power failure: bar
 -File fname2 data after power failure: foo
 -File fname3 data after power failure: foo
 +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
 +cat: 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such 
file or directory
 +File fname1 data after power failure: 
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad'
  to see the entire diff) 

$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
  2019-10-16 10:51:13.160701040 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
   2019-10-16 12:22:10.315449210 +
@@ -1,4 +1,9 @@
 QA output created by 527
-File fname1 data after power failure: bar
-File fname2 data after power failure: foo
-File fname3 data after power failure: foo
+mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system 
call failed: File exists.
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No 
such file or directory
+File fname1 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No 
such file or directory
+File fname2 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No 
such file or directory
+File fname3 data after power failure: 
+umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted.

Syslog:
Oct 16 12:22:09 kili ubuntu: run xfstest generic/527
Oct 16 12:22:09 kili kernel: [ 6068.948341] run fstests generic/527 at 
2019-10-16 12:22:09
Oct 16 12:22:09 kili kernel: [ 6069.125238] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 12:22:09 kili kernel: [ 6069.125240] BTRFS info (device sdb1): has 
skinny extents
Oct 16 12:22:09 kili kernel: [ 6069.132427] BTRFS info (device sdb1): enabling 
ssd optimizations
Oct 16 12:22:09 kili kernel: [ 6069.246264] BTRFS: device fsid 
6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 transid 5 /dev/sdb2
Oct 16 12:22:09 kili multipathd[1484]: dm-0: remove map (uevent)
Oct 16 12:22:09 kili kernel: [ 6069.353749] BTRFS info (device dm-0): disk 
space caching is enabled
Oct 16 12:22:09 kili kernel: [ 6069.353751] BTRFS info (device dm-0): has 
skinny extents
Oct 16 12:22:09 kili kernel: [ 6069.353752] BTRFS info (device dm-0): flagging 
fs with big metadata feature
Oct 16 12:22:09 kili kernel: [ 6069.358172] BTRFS info (device dm-0): enabling 
ssd optimizations
Oct 16 12:22:09 kili kernel: [ 6069.359885] BTRFS info (device dm-0): checking 
UUID tree
Oct 16 12:22:09 kili kernel: [ 6069.677202] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved 
old:/dev/mapper/flakey-test new:/dev/dm-0
Oct 16 12:22:09 kili kernel: [ 6069.677914] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/dm-0 
new:/dev/mapper/flakey-test
Oct 16 12:22:09 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 12:22:09 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 12:22:10 kili kernel: [ 6069.781083] BTRFS info (device dm-0): disk 
space caching is enabled
Oct 16 12:22:10 kili kernel: [ 6069.781085] BTRFS info (device dm-0): has 
skinny extents
Oct 16 12:22:10 kili kernel: [ 6069.785329] BTRFS info (device dm-0): enabling 
ssd optimizations
Oct 16 12:22:10 kili kernel: [ 6069.786880] BTRFS: error (device dm-0) in 
btrfs_replay_log:2304: errno=-17 Object already exists (Failed to recover log 
tree)
Oct 16 12:22:10 kili kernel: [ 6069.837515] BTRFS error (device dm-0): 
open_ctree failed
Oct 16 12:22:10 kili multipathd[1484]: flakey-test: adding map
Oct 16 12:22:10 kili multipathd[1484]: flakey-test: devmap dm-0 added
Oct 16 12:22:10 kili multipathd[1484]: dm-0: remove map (uevent)
Oct 16 12:22:10 kili multipathd[1484]: dm-0: 

[Kernel-packages] [Bug 1848430] [NEW] generic/527 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 generic/527- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad)
 --- tests/generic/527.out  2019-10-16 10:51:13.160701040 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
  2019-10-16 12:22:10.315449210 +
 @@ -1,4 +1,9 @@
  QA output created by 527
 -File fname1 data after power failure: bar
 -File fname2 data after power failure: foo
 -File fname3 data after power failure: foo
 +mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) 
system call failed: File exists.
 +cat: 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No such 
file or directory
 +File fname1 data after power failure: 
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad'
  to see the entire diff) 

$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/527.out
  2019-10-16 10:51:13.160701040 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/527.out.bad
   2019-10-16 12:22:10.315449210 +
@@ -1,4 +1,9 @@
 QA output created by 527
-File fname1 data after power failure: bar
-File fname2 data after power failure: foo
-File fname3 data after power failure: foo
+mount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: mount(2) system 
call failed: File exists.
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname1: No 
such file or directory
+File fname1 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname2: No 
such file or directory
+File fname2 data after power failure: 
+cat: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testdir/fname3: No 
such file or directory
+File fname3 data after power failure: 
+umount: /home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch: not mounted.

Syslog:
Oct 16 12:22:09 kili ubuntu: run xfstest generic/527
Oct 16 12:22:09 kili kernel: [ 6068.948341] run fstests generic/527 at 
2019-10-16 12:22:09
Oct 16 12:22:09 kili kernel: [ 6069.125238] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 12:22:09 kili kernel: [ 6069.125240] BTRFS info (device sdb1): has 
skinny extents
Oct 16 12:22:09 kili kernel: [ 6069.132427] BTRFS info (device sdb1): enabling 
ssd optimizations
Oct 16 12:22:09 kili kernel: [ 6069.246264] BTRFS: device fsid 
6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 transid 5 /dev/sdb2
Oct 16 12:22:09 kili multipathd[1484]: dm-0: remove map (uevent)
Oct 16 12:22:09 kili kernel: [ 6069.353749] BTRFS info (device dm-0): disk 
space caching is enabled
Oct 16 12:22:09 kili kernel: [ 6069.353751] BTRFS info (device dm-0): has 
skinny extents
Oct 16 12:22:09 kili kernel: [ 6069.353752] BTRFS info (device dm-0): flagging 
fs with big metadata feature
Oct 16 12:22:09 kili kernel: [ 6069.358172] BTRFS info (device dm-0): enabling 
ssd optimizations
Oct 16 12:22:09 kili kernel: [ 6069.359885] BTRFS info (device dm-0): checking 
UUID tree
Oct 16 12:22:09 kili kernel: [ 6069.677202] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved 
old:/dev/mapper/flakey-test new:/dev/dm-0
Oct 16 12:22:09 kili kernel: [ 6069.677914] BTRFS info (device dm-0): device 
fsid 6572496b-1348-4fc7-a1a8-a4fdb1194b9b devid 1 moved old:/dev/dm-0 
new:/dev/mapper/flakey-test
Oct 16 12:22:09 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 12:22:09 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 12:22:10 kili kernel: [ 6069.781083] BTRFS info (device dm-0): disk 
space caching is enabled
Oct 16 12:22:10 kili kernel: [ 6069.781085] BTRFS info (device dm-0): has 
skinny extents
Oct 16 12:22:10 kili kernel: [ 6069.785329] BTRFS info (device dm-0): enabling 
ssd optimizations
Oct 16 12:22:10 kili kernel: [ 6069.786880] BTRFS: error (device dm-0) in 
btrfs_replay_log:2304: errno=-17 Object already exists (Failed to recover log 
tree)
Oct 16 12:22:10 kili kernel: [ 6069.837515] BTRFS error (device dm-0): 
open_ctree failed
Oct 16 12:22:10 kili multipathd[1484]: flakey-test: adding map
Oct 16 12:22:10 kili multipathd[1484]: flakey-test: devmap dm-0 added
Oct 16 12:22:10 kili multipathd[1484]: dm-0: remove map (uevent)
Oct 16 12:22:10 kili multipathd[1484]: dm-0: 

[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

[Kai-Heng Feng]

The pci_save_state () will make the Nvidia PCI devices stay at D0 under
S3. We need to put it to D3 to save power.

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

Title:
  System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  After upgrading the Ubuntu kernel to version 5.0.0-21, the System76
  Oryx Pro (oryp5) fails to resume from suspend when using discrete
  NVIDIA graphics

  The issue can be created on this hardware by following these steps:
  - Install Ubuntu 18.04.2
  - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed
  - Upgrade:
sudo apt-get updatesudo apt-get dist-upgrade
  - Install 5.0 HWE kernel:
sudo apt-get install linux-generic-hwe-18.04-edge
  - Install NVIDIA driver:
sudo apt-get install nvidia-driver-430
  - Reboot:
sudo reboot
  - Attempt suspend/resume cycle

  This occurred after upgrading the kernel from version 5.0.0-20.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system76   1721 F pulseaudio
   /dev/snd/controlC0:  system76   1721 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  MachineType: System76 Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-hwe-edge
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro
  ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp5
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: oryp5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp5
  dmi.sys.vendor: System76

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

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

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

[Kai-Heng Feng]

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

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

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Fix Released

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

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

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

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

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

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

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

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

[Kernel-packages] [Bug 1846306] Re: generic/394 from ubuntu_xfstests_ext4 / xfs failed on D

[Po-Hsu Lin]

The same failure could be found with btrfs filesystem on Disco as well:

 generic/394- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad)
 --- tests/generic/394.out  2019-10-16 10:51:13.148701170 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad
  2019-10-16 12:04:24.705838723 +
 @@ -1,2 +1 @@
  QA output created by 394
 -File size limit exceeded
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/394.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad'
  to see the entire diff)


** Summary changed:

- generic/394 from ubuntu_xfstests_ext4 / xfs failed on D
+ generic/394 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

** Tags added: ubuntu-xfstests-btrfs

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

Title:
  generic/394 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

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

Bug description:
  Issue found on node amd64 node "gonzo"

   generic/394- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad)
   --- tests/generic/394.out  2019-10-01 07:38:07.080386390 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad
   2019-10-01 13:01:11.666597773 +
   @@ -1,2 +1 @@
QA output created by 394
   -File size limit exceeded
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/394.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad'
  to see the entire diff) 

  $ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/394.out.bad
  QA output created by 394

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  1 11:07 seq
   crw-rw 1 root audio 116, 33 Oct  1 11:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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:
   [68184.314209] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Oct  2 07:35:47 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R415
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.4
  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/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/1846306/+subscriptions

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

[Kernel-packages] [Bug 1846295] Re: generic/484 from ubuntu_xfstests_ext4 / xfs failed on D

[Po-Hsu Lin]

The same failure could be found with btrfs filesystem as well.


 generic/484- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad)
 --- tests/generic/484.out  2019-10-16 10:51:13.156701083 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad
  2019-10-16 12:21:10.804006496 +
 @@ -1,2 +1,3 @@
  QA output created by 484
 +record lock is not preserved across execve(2)
  Silence is golden
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/484.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad'
  to see the entire diff) 


** Summary changed:

- generic/484 from ubuntu_xfstests_ext4 / xfs failed on D
+ generic/484 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

** Tags added: ubuntu-xfstests-btrfs

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

Title:
  generic/484 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

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

Bug description:
  Issue found on node amd64 node "gonzo"

   generic/484- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad)
   --- tests/generic/484.out  2019-10-01 07:38:07.088386381 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad
   2019-10-01 13:50:54.838245083 +
   @@ -1,2 +1,3 @@
QA output created by 484
   +record lock is not preserved across execve(2)
Silence is golden
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/484.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad'
  to see the entire diff) 

  $ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/484.out.bad
  QA output created by 484
  record lock is not preserved across execve(2)
  Silence is golden

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  1 11:07 seq
   crw-rw 1 root audio 116, 33 Oct  1 11:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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:
   [68184.314209] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Oct  2 06:28:30 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R415
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.4
  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/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/1846295/+subscriptions

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  btrfs/193 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/193  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad)
   --- tests/btrfs/193.out2019-10-16 10:51:13.104701643 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad
2019-10-16 11:16:44.831139679 +
   @@ -4,5 +4,4 @@
wrote 4096/4096 bytes at offset 268435456
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
fallocate: Disk quota exceeded
   -wrote 201326592/201326592 bytes at offset 0
   -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
   +pwrite: Disk quota exceeded
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad'
  to see the entire diff) 

  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad
   2019-10-16 11:16:44.831139679 +
  @@ -4,5 +4,4 @@
   wrote 4096/4096 bytes at offset 268435456
   XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
   fallocate: Disk quota exceeded
  -wrote 201326592/201326592 bytes at offset 0
  -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
  +pwrite: Disk quota exceeded

  Syslog:
  Oct 16 11:16:43 kili ubuntu: run xfstest btrfs/193
  Oct 16 11:16:43 kili kernel: [ 2143.183330] run fstests btrfs/193 at 
2019-10-16 11:16:43
  Oct 16 11:16:43 kili kernel: [ 2143.463462] BTRFS: device fsid 
1f04a683-4df8-4adb-9cac-13a57fb79aa0 devid 1 transid 5 /dev/sdb2
  Oct 16 11:16:43 kili kernel: [ 2143.483470] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:16:43 kili kernel: [ 2143.483474] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:16:43 kili kernel: [ 2143.483475] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:16:43 kili kernel: [ 2143.487752] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:16:43 kili kernel: [ 2143.488327] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:16:43 kili kernel: [ 2143.493619] BTRFS info (device sdb2): qgroup 
scan completed (inconsistency flag cleared)
  Oct 16 11:16:43 kili kernel: [ 2143.496960] BTRFS info (device sdb2): qgroup 
scan completed (inconsistency flag cleared)
  Oct 16 11:16:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 11:16:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 11:16:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:16:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:16:44 kili kernel: [ 2144.448728] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:16:44 kili kernel: [ 2144.448730] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:16:44 kili kernel: [ 2144.452303] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:16:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:16:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
   crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  btrfs/182 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/182  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad)
   --- tests/btrfs/182.out2019-10-16 10:51:13.104701643 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad
2019-10-16 11:12:32.817591531 +
   @@ -1,2 +1,4 @@
QA output created by 182
   +ERROR: error during balancing 
'/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device
   +There may be more info in syslog - try dmesg | tail
Silence is golden
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad'
  to see the entire diff) 

  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad
   2019-10-16 11:12:32.817591531 +
  @@ -1,2 +1,4 @@
   QA output created by 182
  +ERROR: error during balancing 
'/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device
  +There may be more info in syslog - try dmesg | tail
   Silence is golden

  
  Syslog:
  Oct 16 11:12:28 kili ubuntu: run xfstest btrfs/182
  Oct 16 11:12:28 kili kernel: [ 1887.982615] run fstests btrfs/182 at 
2019-10-16 11:12:28
  Oct 16 11:12:28 kili kernel: [ 1888.168789] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 11:12:28 kili kernel: [ 1888.168791] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 11:12:28 kili kernel: [ 1888.171922] BTRFS info (device sdb1): 
enabling ssd optimizations
  Oct 16 11:12:28 kili kernel: [ 1888.254332] BTRFS: device fsid 
31ebd16f-0464-4373-b2d9-d3beef4d1bf4 devid 1 transid 5 /dev/sdb2
  Oct 16 11:12:28 kili kernel: [ 1888.274317] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:12:28 kili kernel: [ 1888.274319] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:12:28 kili kernel: [ 1888.274320] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:12:28 kili kernel: [ 1888.282340] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:12:28 kili kernel: [ 1888.286045] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:12:32 kili kernel: [ 1892.268108] BTRFS info (device sdb2): 
balance: start -m -s
  Oct 16 11:12:32 kili kernel: [ 1892.268284] BTRFS info (device sdb2): 
relocating block group 1048576 flags system
  Oct 16 11:12:32 kili kernel: [ 1892.272632] BTRFS info (device sdb2): found 1 
extents
  Oct 16 11:12:32 kili kernel: [ 1892.275676] BTRFS info (device sdb2): 2 
enospc errors during balance
  Oct 16 11:12:32 kili kernel: [ 1892.275678] BTRFS info (device sdb2): 
balance: ended with status: -28
  Oct 16 11:12:32 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 11:12:32 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 11:12:32 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:12:32 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:12:32 kili kernel: [ 1892.433637] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:12:32 kili kernel: [ 1892.433639] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:12:32 kili kernel: [ 1892.437048] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:12:32 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:12:32 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: User Name 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  generic/260 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   generic/260[failed, exit status 1]- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad)
   --- tests/generic/260.out  2019-10-16 10:51:13.136701298 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad
  2019-10-16 11:46:46.002804112 +
   @@ -1,14 +1,15 @@
QA output created by 260
[+] Start beyond the end of fs (should fail)
   -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument
   +
[+] Start beyond the end of fs with len set (should fail) 
   -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument
   +
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/260.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad'
  to see the entire diff)

  Syslog:
  Oct 16 11:46:26 kili ubuntu: run xfstest generic/260
  Oct 16 11:46:26 kili kernel: [ 3925.966035] run fstests generic/260 at 
2019-10-16 11:46:26
  Oct 16 11:46:26 kili kernel: [ 3926.146996] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 11:46:26 kili kernel: [ 3926.146998] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 11:46:26 kili kernel: [ 3926.150850] BTRFS info (device sdb1): 
enabling ssd optimizations
  Oct 16 11:46:26 kili kernel: [ 3926.233032] BTRFS: device fsid 
38d9a8f4-3115-4a21-adaa-a1a68be4d42c devid 1 transid 5 /dev/sdb2
  Oct 16 11:46:26 kili kernel: [ 3926.252529] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:46:26 kili kernel: [ 3926.252530] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:46:26 kili kernel: [ 3926.252531] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:46:26 kili kernel: [ 3926.257694] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:46:26 kili kernel: [ 3926.259525] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:46:33 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:46:33 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:46:33 kili kernel: [ 3933.374556] BTRFS: device fsid 
cd6d9b8b-abdd-4c38-b9bb-c97b36cb3117 devid 1 transid 5 /dev/sdb2
  Oct 16 11:46:33 kili kernel: [ 3933.394698] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:46:33 kili kernel: [ 3933.394700] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:46:33 kili kernel: [ 3933.394701] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:46:33 kili kernel: [ 3933.399463] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:46:33 kili kernel: [ 3933.401342] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:46:41 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:46:41 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:46:41 kili kernel: [ 3941.143873] BTRFS: device fsid 
f10eab55-8c80-402c-84d2-002a6a1339de devid 1 transid 5 /dev/sdb2
  Oct 16 11:46:41 kili kernel: [ 3941.162874] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:46:41 kili kernel: [ 3941.170124] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:46:41 kili kernel: [ 3941.172812] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:46:42 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:46:42 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:46:43 kili kernel: [ 3942.718482] BTRFS: device fsid 
030f6bb2-f009-4cf6-91f0-75ea33b909c6 devid 1 transid 5 /dev/sdb2
  Oct 16 11:46:43 kili kernel: [ 3942.737021] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:46:43 kili kernel: [ 3942.737022] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:46:43 kili kernel: [ 

[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend

[Kai-Heng Feng]

We've discussed this with Nvidia and they confirmed [1] and/or [2] can solve 
the issue. Can you please try:
- [PATCH] PCI: PM: Fix pci_power_up() [1]
- [PATCH v2 0/2] PCI: Add missing link delays [2]

Let me know if you need a kernel binary package.

[1] 
https://lore.kernel.org/linux-pci/cajz5v0jd_-phnm6neonc6z0onkedelt+6q_p1hnopm_invt...@mail.gmail.com/T/#mf60a04c0abefe088af45e706f5619e7fa584cc7e
[2] 
https://lore.kernel.org/linux-pci/20191008090540.gy2...@lahna.fi.intel.com/T/#m1eff5c97b885fcc655874be028074a48c0d1d21f

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

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

Title:
  'gpu has fallen off the bus' after return from suspend

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With this message the only way to resume work is to reboot the system
  using power button.

  With kernel linux-image-5.3.0-13-generic everything is OK.
  Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still 
happens in linux-image-5.3.0-18-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  player 4451 F pulseaudio
   /dev/snd/controlC1:  player 4451 F pulseaudio
   /dev/snd/controlC0:  player 4451 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Oct 14 01:27:04 2019
  HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e
  MachineType: LENOVO 20BG0016US
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current 
loglevel=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago)
  WifiSyslog:
   
  dmi.bios.date: 05/30/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET88WW (2.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BG0016US
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BG0016US
  dmi.product.sku: LENOVO_MT_20BG
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  btrfs/187 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/187  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad)
   --- tests/btrfs/187.out2019-10-16 10:51:13.104701643 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad
2019-10-16 11:16:39.519207382 +
   @@ -1,3 +1,6 @@
QA output created by 187
Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap1'
Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap2'
   +[ 2109.330631] BTRFS error (device sdb2): parent transid verify failed 
on 18814697472 wanted 396 found 415
   +[ 2113.554514] BTRFS error (device sdb2): parent transid verify failed 
on 19921420288 wanted 423 found 445
   +[ 2117.693224] BTRFS error (device sdb2): parent transid verify failed 
on 20514979840 wanted 446 found 458
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad'
  to see the entire diff)

  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad
   2019-10-16 11:16:39.519207382 +
  @@ -1,3 +1,6 @@
   QA output created by 187
   Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap1'
   Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap2'
  +[ 2109.330631] BTRFS error (device sdb2): parent transid verify failed on 
18814697472 wanted 396 found 415
  +[ 2113.554514] BTRFS error (device sdb2): parent transid verify failed on 
19921420288 wanted 423 found 445
  +[ 2117.693224] BTRFS error (device sdb2): parent transid verify failed on 
20514979840 wanted 446 found 458

  
  Please find the attachment for the syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
   crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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 Oct 17 04:33:53 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S2600WTT
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WTT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G92187-350
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...:ct23:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600WTT
  dmi.product.sku: 

[Kernel-packages] [Bug 1848424] [NEW] generic/471 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 generic/471- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad)
 --- tests/generic/471.out  2019-10-16 10:51:13.156701083 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad
  2019-10-16 12:16:10.594841128 +
 @@ -2,12 +2,10 @@
  pwrite: Resource temporarily unavailable
  wrote 8388608/8388608 bytes at offset 0
  XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 -RWF_NOWAIT time is within limits.
 +pwrite: Resource temporarily unavailable 
 +(standard_in) 1: syntax error
 +RWF_NOWAIT took  seconds
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad'
  to see the entire diff) 


$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/471.out
  2019-10-16 10:51:13.156701083 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/471.out.bad
   2019-10-16 12:16:10.594841128 +
@@ -2,12 +2,10 @@
 pwrite: Resource temporarily unavailable
 wrote 8388608/8388608 bytes at offset 0
 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-RWF_NOWAIT time is within limits.
+pwrite: Resource temporarily unavailable
+(standard_in) 1: syntax error
+RWF_NOWAIT took  seconds
 :  aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa  
 *
-0020:  bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb bb  
-*
-0030:  aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa  
-*
 read 8388608/8388608 bytes at offset 0
 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)

Syslog:
Oct 16 12:16:09 kili ubuntu: run xfstest generic/471
Oct 16 12:16:09 kili kernel: [ 5708.949736] run fstests generic/471 at 
2019-10-16 12:16:09
Oct 16 12:16:10 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 12:16:10 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 12:16:10 kili kernel: [ 5710.290570] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 12:16:10 kili kernel: [ 5710.290573] BTRFS info (device sdb1): has 
skinny extents
Oct 16 12:16:10 kili kernel: [ 5710.294454] BTRFS info (device sdb1): enabling 
ssd optimizations

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
 crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
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 Oct 17 04:55:08 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S2600WTT
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-31-generic N/A
 linux-backports-modules-5.0.0-31-generic  N/A
 linux-firmware1.178.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/19/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: S2600WTT
dmi.board.vendor: Intel Corporation
dmi.board.version: G92187-350
dmi.chassis.asset.tag: 
dmi.chassis.type: 23
dmi.chassis.vendor: ...
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...:ct23:cvr..:
dmi.product.family: Family
dmi.product.name: S2600WTT
dmi.product.sku: SKU Number
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: 

[Kernel-packages] [Bug 1848423] [NEW] generic/260 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 generic/260[failed, exit status 1]- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad)
 --- tests/generic/260.out  2019-10-16 10:51:13.136701298 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad
  2019-10-16 11:46:46.002804112 +
 @@ -1,14 +1,15 @@
  QA output created by 260
  [+] Start beyond the end of fs (should fail)
 -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument
 +
  [+] Start beyond the end of fs with len set (should fail) 
 -fstrim: SCRATCH_MNT: FITRIM ioctl failed: Invalid argument
 +
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/260.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/260.out.bad'
  to see the entire diff)

Syslog:
Oct 16 11:46:26 kili ubuntu: run xfstest generic/260
Oct 16 11:46:26 kili kernel: [ 3925.966035] run fstests generic/260 at 
2019-10-16 11:46:26
Oct 16 11:46:26 kili kernel: [ 3926.146996] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 11:46:26 kili kernel: [ 3926.146998] BTRFS info (device sdb1): has 
skinny extents
Oct 16 11:46:26 kili kernel: [ 3926.150850] BTRFS info (device sdb1): enabling 
ssd optimizations
Oct 16 11:46:26 kili kernel: [ 3926.233032] BTRFS: device fsid 
38d9a8f4-3115-4a21-adaa-a1a68be4d42c devid 1 transid 5 /dev/sdb2
Oct 16 11:46:26 kili kernel: [ 3926.252529] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:46:26 kili kernel: [ 3926.252530] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:46:26 kili kernel: [ 3926.252531] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:46:26 kili kernel: [ 3926.257694] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:46:26 kili kernel: [ 3926.259525] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:46:33 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:33 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:33 kili kernel: [ 3933.374556] BTRFS: device fsid 
cd6d9b8b-abdd-4c38-b9bb-c97b36cb3117 devid 1 transid 5 /dev/sdb2
Oct 16 11:46:33 kili kernel: [ 3933.394698] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:46:33 kili kernel: [ 3933.394700] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:46:33 kili kernel: [ 3933.394701] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:46:33 kili kernel: [ 3933.399463] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:46:33 kili kernel: [ 3933.401342] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:46:41 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:41 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:41 kili kernel: [ 3941.143873] BTRFS: device fsid 
f10eab55-8c80-402c-84d2-002a6a1339de devid 1 transid 5 /dev/sdb2
Oct 16 11:46:41 kili kernel: [ 3941.162874] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:46:41 kili kernel: [ 3941.162876] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:46:41 kili kernel: [ 3941.170124] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:46:41 kili kernel: [ 3941.172812] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:46:42 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:42 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:43 kili kernel: [ 3942.718482] BTRFS: device fsid 
030f6bb2-f009-4cf6-91f0-75ea33b909c6 devid 1 transid 5 /dev/sdb2
Oct 16 11:46:43 kili kernel: [ 3942.737021] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:46:43 kili kernel: [ 3942.737022] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:46:43 kili kernel: [ 3942.737023] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:46:43 kili kernel: [ 3942.741503] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:46:43 kili kernel: [ 3942.743221] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:46:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:46:44 kili kernel: [ 3944.219218] BTRFS: device fsid 
8a84d9a8-a3aa-41f4-bd5d-d55f664bb6e1 devid 1 transid 5 /dev/sdb2
Oct 16 11:46:44 

[Kernel-packages] [Bug 1846308] Re: generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

[Po-Hsu Lin]

The same failure could be found with btrfs filesystem on Disco as well:

 generic/228- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad)
 --- tests/generic/228.out  2019-10-16 10:51:13.132701342 + 
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad
  2019-10-16 11:43:15.476459874 +
 @@ -1,6 +1,6 @@
  QA output created by 228
  File size limit is now set to 100 MB.
  Let us try to preallocate 101 MB. This should fail.
 -File size limit exceeded
 +fallocate: File too large
  Let us now try to preallocate 50 MB. This should succeed.
  Test over.
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/228.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad'
  to see the entire diff) 


** Summary changed:

- generic/228 from ubuntu_xfstests_ext4 / xfs failed on D
+ generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

** Tags added: ubuntu-xfstests-btrfs

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

Title:
  generic/228 from ubuntu_xfstests_btrfs / ext4 / xfs failed on D

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

Bug description:
  Issue found on node amd64 node "gonzo"

   generic/228- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad)
   --- tests/generic/228.out  2019-10-01 07:38:07.060386413 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad
   2019-10-01 12:27:44.465549241 +
   @@ -1,6 +1,6 @@
QA output created by 228
File size limit is now set to 100 MB.
Let us try to preallocate 101 MB. This should fail.
   -File size limit exceeded
   +fallocate: File too large
Let us now try to preallocate 50 MB. This should succeed.
Test over.
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/tests/generic/228.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad'
  to see the entire diff) 

  
  $ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_ext4/src/xfstests-bld/xfstests-dev/results//generic/228.out.bad
  QA output created by 228
  File size limit is now set to 100 MB.
  Let us try to preallocate 101 MB. This should fail.
  fallocate: File too large
  Let us now try to preallocate 50 MB. This should succeed.
  Test over.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-29-generic 5.0.0-29.31
  ProcVersionSignature: User Name 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  1 11:07 seq
   crw-rw 1 root audio 116, 33 Oct  1 11:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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:
   [68184.314209] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [68184.315939] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed Oct  2 07:45:38 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R415
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=3e0e190e-d425-4d00-a9a9-deb0c452399b ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-29-generic N/A
   linux-backports-modules-5.0.0-29-generic  N/A
   linux-firmware1.178.4
  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/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:

[Kernel-packages] [Bug 1848422] [NEW] btrfs/193 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 btrfs/193  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad)
 --- tests/btrfs/193.out2019-10-16 10:51:13.104701643 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad
2019-10-16 11:16:44.831139679 +
 @@ -4,5 +4,4 @@
  wrote 4096/4096 bytes at offset 268435456
  XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
  fallocate: Disk quota exceeded
 -wrote 201326592/201326592 bytes at offset 0
 -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 +pwrite: Disk quota exceeded
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad'
  to see the entire diff) 

$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/193.out
2019-10-16 10:51:13.104701643 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/193.out.bad
 2019-10-16 11:16:44.831139679 +
@@ -4,5 +4,4 @@
 wrote 4096/4096 bytes at offset 268435456
 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 fallocate: Disk quota exceeded
-wrote 201326592/201326592 bytes at offset 0
-XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+pwrite: Disk quota exceeded

Syslog:
Oct 16 11:16:43 kili ubuntu: run xfstest btrfs/193
Oct 16 11:16:43 kili kernel: [ 2143.183330] run fstests btrfs/193 at 2019-10-16 
11:16:43
Oct 16 11:16:43 kili kernel: [ 2143.463462] BTRFS: device fsid 
1f04a683-4df8-4adb-9cac-13a57fb79aa0 devid 1 transid 5 /dev/sdb2
Oct 16 11:16:43 kili kernel: [ 2143.483470] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:16:43 kili kernel: [ 2143.483474] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:16:43 kili kernel: [ 2143.483475] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:16:43 kili kernel: [ 2143.487752] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:16:43 kili kernel: [ 2143.488327] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:16:43 kili kernel: [ 2143.493619] BTRFS info (device sdb2): qgroup 
scan completed (inconsistency flag cleared)
Oct 16 11:16:43 kili kernel: [ 2143.496960] BTRFS info (device sdb2): qgroup 
scan completed (inconsistency flag cleared)
Oct 16 11:16:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 11:16:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 11:16:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:16:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:16:44 kili kernel: [ 2144.448728] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:16:44 kili kernel: [ 2144.448730] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:16:44 kili kernel: [ 2144.452303] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:16:44 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:16:44 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
 crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
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 Oct 17 04:44:16 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S2600WTT
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-31-generic N/A
 linux-backports-modules-5.0.0-31-generic  N/A
 linux-firmware1.178.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'

[Kernel-packages] [Bug 1848360] Re: [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full brightness after wake up

[Kai-Heng Feng]

This commit should fix it:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb264220d9316f6bd7c1fd84b8da398c93912931

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

Title:
  [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full
  brightness after wake up

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Every time when I open up my lid of my laptop, and wake up my system
  from sleeping,the screen will return to full brightness.Either I press
  the brightness - or + button,the brightness will back to normal
  immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 00:05:56 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:380c]
  InstallationDate: Installed on 2019-09-28 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN30WW:bd07/04/2018:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.sku: LENOVO_MT_81BR_BU_idea_FM_ideapad 720S-13ARR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1848421] [NEW] btrfs/187 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 btrfs/187  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad)
 --- tests/btrfs/187.out2019-10-16 10:51:13.104701643 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad
2019-10-16 11:16:39.519207382 +
 @@ -1,3 +1,6 @@
  QA output created by 187
  Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap1'
  Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap2'
 +[ 2109.330631] BTRFS error (device sdb2): parent transid verify failed on 
18814697472 wanted 396 found 415
 +[ 2113.554514] BTRFS error (device sdb2): parent transid verify failed on 
19921420288 wanted 423 found 445
 +[ 2117.693224] BTRFS error (device sdb2): parent transid verify failed on 
20514979840 wanted 446 found 458
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad'
  to see the entire diff)


$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/187.out
2019-10-16 10:51:13.104701643 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/187.out.bad
 2019-10-16 11:16:39.519207382 +
@@ -1,3 +1,6 @@
 QA output created by 187
 Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap1'
 Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap2'
+[ 2109.330631] BTRFS error (device sdb2): parent transid verify failed on 
18814697472 wanted 396 found 415
+[ 2113.554514] BTRFS error (device sdb2): parent transid verify failed on 
19921420288 wanted 423 found 445
+[ 2117.693224] BTRFS error (device sdb2): parent transid verify failed on 
20514979840 wanted 446 found 458


Please find the attachment for the syslog.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
 crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
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 Oct 17 04:33:53 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S2600WTT
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-31-generic N/A
 linux-backports-modules-5.0.0-31-generic  N/A
 linux-firmware1.178.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/19/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: S2600WTT
dmi.board.vendor: Intel Corporation
dmi.board.version: G92187-350
dmi.chassis.asset.tag: 
dmi.chassis.type: 23
dmi.chassis.vendor: ...
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...:ct23:cvr..:
dmi.product.family: Family
dmi.product.name: S2600WTT
dmi.product.sku: SKU Number
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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


** Tags: 5.0 amd64 apport-bug disco sru-20190930 ubuntu-xfstests-btrfs 
uec-images

** Attachment added: "btrfs-187.syslog"
   
https://bugs.launchpad.net/bugs/1848421/+attachment/5297674/+files/btrfs-187.syslog

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

** Also affects: 

[Kernel-packages] [Bug 1848418] [NEW] btrfs/182 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 btrfs/182  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad)
 --- tests/btrfs/182.out2019-10-16 10:51:13.104701643 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad
2019-10-16 11:12:32.817591531 +
 @@ -1,2 +1,4 @@
  QA output created by 182
 +ERROR: error during balancing 
'/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device
 +There may be more info in syslog - try dmesg | tail
  Silence is golden
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad'
  to see the entire diff) 


$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/182.out
2019-10-16 10:51:13.104701643 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/182.out.bad
 2019-10-16 11:12:32.817591531 +
@@ -1,2 +1,4 @@
 QA output created by 182
+ERROR: error during balancing 
'/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device
+There may be more info in syslog - try dmesg | tail
 Silence is golden


Syslog:
Oct 16 11:12:28 kili ubuntu: run xfstest btrfs/182
Oct 16 11:12:28 kili kernel: [ 1887.982615] run fstests btrfs/182 at 2019-10-16 
11:12:28
Oct 16 11:12:28 kili kernel: [ 1888.168789] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 11:12:28 kili kernel: [ 1888.168791] BTRFS info (device sdb1): has 
skinny extents
Oct 16 11:12:28 kili kernel: [ 1888.171922] BTRFS info (device sdb1): enabling 
ssd optimizations
Oct 16 11:12:28 kili kernel: [ 1888.254332] BTRFS: device fsid 
31ebd16f-0464-4373-b2d9-d3beef4d1bf4 devid 1 transid 5 /dev/sdb2
Oct 16 11:12:28 kili kernel: [ 1888.274317] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:12:28 kili kernel: [ 1888.274319] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:12:28 kili kernel: [ 1888.274320] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:12:28 kili kernel: [ 1888.282340] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:12:28 kili kernel: [ 1888.286045] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:12:32 kili kernel: [ 1892.268108] BTRFS info (device sdb2): balance: 
start -m -s
Oct 16 11:12:32 kili kernel: [ 1892.268284] BTRFS info (device sdb2): 
relocating block group 1048576 flags system
Oct 16 11:12:32 kili kernel: [ 1892.272632] BTRFS info (device sdb2): found 1 
extents
Oct 16 11:12:32 kili kernel: [ 1892.275676] BTRFS info (device sdb2): 2 enospc 
errors during balance
Oct 16 11:12:32 kili kernel: [ 1892.275678] BTRFS info (device sdb2): balance: 
ended with status: -28
Oct 16 11:12:32 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 11:12:32 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 11:12:32 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:12:32 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:12:32 kili kernel: [ 1892.433637] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:12:32 kili kernel: [ 1892.433639] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:12:32 kili kernel: [ 1892.437048] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:12:32 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:12:32 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
 crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
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 Oct 17 04:26:10 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  btrfs/172 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/172  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad)
   --- tests/btrfs/172.out2019-10-16 10:51:13.104701643 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad
2019-10-16 11:12:14.297724635 +
   @@ -1,2 +1,5 @@
QA output created by 172
   +fallocate: No space left on device 
   +fallocate: No space left on device 
   +fallocate: No space left on device 
Silence is golden
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad'
  to see the entire diff) 

  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad
   2019-10-16 11:12:14.297724635 +
  @@ -1,2 +1,5 @@
   QA output created by 172
  +fallocate: No space left on device
  +fallocate: No space left on device
  +fallocate: No space left on device
   Silence is golden

  Syslog:
  Oct 16 11:12:12 kili ubuntu: run xfstest btrfs/172
  Oct 16 11:12:12 kili kernel: [ 1871.836387] run fstests btrfs/172 at 
2019-10-16 11:12:12
  Oct 16 11:12:12 kili kernel: [ 1872.017295] BTRFS info (device sdb1): disk 
space caching is enabled
  Oct 16 11:12:12 kili kernel: [ 1872.017299] BTRFS info (device sdb1): has 
skinny extents
  Oct 16 11:12:12 kili kernel: [ 1872.020831] BTRFS info (device sdb1): 
enabling ssd optimizations
  Oct 16 11:12:12 kili kernel: [ 1872.126224] BTRFS: device fsid 
319cee42-25fa-4cac-8de6-5230ebedf99f devid 1 transid 5 /dev/sdb2
  Oct 16 11:12:12 kili kernel: [ 1872.151545] BTRFS info (device sdb2): 
max_inline at 0
  Oct 16 11:12:12 kili kernel: [ 1872.151550] BTRFS info (device sdb2): setting 
nodatacow, compression disabled
  Oct 16 11:12:12 kili kernel: [ 1872.151552] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:12:12 kili kernel: [ 1872.151553] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:12:12 kili kernel: [ 1872.151555] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:12:12 kili kernel: [ 1872.158799] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:12:12 kili kernel: [ 1872.159342] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:12:14 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 11:12:14 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
  Oct 16 11:12:14 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:12:14 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:12:14 kili kernel: [ 1873.906816] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:12:14 kili kernel: [ 1873.906819] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:12:14 kili kernel: [ 1873.909937] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:12:14 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
  Oct 16 11:12:14 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
   crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  

[Kernel-packages] [Bug 1848417] [NEW] btrfs/172 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 btrfs/172  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad)
 --- tests/btrfs/172.out2019-10-16 10:51:13.104701643 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad
2019-10-16 11:12:14.297724635 +
 @@ -1,2 +1,5 @@
  QA output created by 172
 +fallocate: No space left on device 
 +fallocate: No space left on device 
 +fallocate: No space left on device 
  Silence is golden
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad'
  to see the entire diff) 

$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/172.out
2019-10-16 10:51:13.104701643 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/172.out.bad
 2019-10-16 11:12:14.297724635 +
@@ -1,2 +1,5 @@
 QA output created by 172
+fallocate: No space left on device
+fallocate: No space left on device
+fallocate: No space left on device
 Silence is golden

Syslog:
Oct 16 11:12:12 kili ubuntu: run xfstest btrfs/172
Oct 16 11:12:12 kili kernel: [ 1871.836387] run fstests btrfs/172 at 2019-10-16 
11:12:12
Oct 16 11:12:12 kili kernel: [ 1872.017295] BTRFS info (device sdb1): disk 
space caching is enabled
Oct 16 11:12:12 kili kernel: [ 1872.017299] BTRFS info (device sdb1): has 
skinny extents
Oct 16 11:12:12 kili kernel: [ 1872.020831] BTRFS info (device sdb1): enabling 
ssd optimizations
Oct 16 11:12:12 kili kernel: [ 1872.126224] BTRFS: device fsid 
319cee42-25fa-4cac-8de6-5230ebedf99f devid 1 transid 5 /dev/sdb2
Oct 16 11:12:12 kili kernel: [ 1872.151545] BTRFS info (device sdb2): 
max_inline at 0
Oct 16 11:12:12 kili kernel: [ 1872.151550] BTRFS info (device sdb2): setting 
nodatacow, compression disabled
Oct 16 11:12:12 kili kernel: [ 1872.151552] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:12:12 kili kernel: [ 1872.151553] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:12:12 kili kernel: [ 1872.151555] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:12:12 kili kernel: [ 1872.158799] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:12:12 kili kernel: [ 1872.159342] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:12:14 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 11:12:14 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
Oct 16 11:12:14 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:12:14 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:12:14 kili kernel: [ 1873.906816] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:12:14 kili kernel: [ 1873.906819] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:12:14 kili kernel: [ 1873.909937] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:12:14 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
Oct 16 11:12:14 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
 crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
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 Oct 17 04:22:00 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S2600WTT
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-31-generic N/A
 linux-backports-modules-5.0.0-31-generic  N/A
 linux-firmware1.178.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 

[Kernel-packages] [Bug 1848409] Re: btrfs/153 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

** Description changed:

  Issue found on node amd64 node "kili"
  
-  btrfs/153  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad)
-  --- tests/btrfs/153.out2019-10-16 10:51:13.104701643 +
-  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
2019-10-16 11:11:43.217948903 +
-  @@ -1,2 +1,5 @@
-   QA output created by 153
-  +pwrite: Disk quota exceeded
-  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
-  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
-   Silence is golden
-  ...
-  (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad'
  to see the entire diff) 
- 
+  btrfs/153  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad)
+  --- tests/btrfs/153.out2019-10-16 10:51:13.104701643 +
+  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
2019-10-16 11:11:43.217948903 +
+  @@ -1,2 +1,5 @@
+   QA output created by 153
+  +pwrite: Disk quota exceeded
+  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
+  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
+   Silence is golden
+  ...
+  (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad'
  to see the entire diff)
  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
   2019-10-16 11:11:43.217948903 +
  @@ -1,2 +1,5 @@
-  QA output created by 153
+  QA output created by 153
  +pwrite: Disk quota exceeded
  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk quota 
exceeded
  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk quota 
exceeded
-  Silence is golden
+  Silence is golden
+ 
+ Syslog:
+ Oct 16 11:11:42 kili ubuntu: run xfstest btrfs/153
+ Oct 16 11:11:42 kili kernel: [ 1842.274698] run fstests btrfs/153 at 
2019-10-16 11:11:42
+ Oct 16 11:11:42 kili kernel: [ 1842.462616] BTRFS info (device sdb1): disk 
space caching is enabled
+ Oct 16 11:11:42 kili kernel: [ 1842.462618] BTRFS info (device sdb1): has 
skinny extents
+ Oct 16 11:11:42 kili kernel: [ 1842.466867] BTRFS info (device sdb1): 
enabling ssd optimizations
+ Oct 16 11:11:42 kili kernel: [ 1842.589118] BTRFS: device fsid 
a48a1e75-d879-4c6b-b97a-f90804fa8e7e devid 1 transid 5 /dev/sdb2
+ Oct 16 11:11:42 kili kernel: [ 1842.608328] BTRFS info (device sdb2): disk 
space caching is enabled
+ Oct 16 11:11:42 kili kernel: [ 1842.608330] BTRFS info (device sdb2): has 
skinny extents
+ Oct 16 11:11:42 kili kernel: [ 1842.608330] BTRFS info (device sdb2): 
flagging fs with big metadata feature
+ Oct 16 11:11:42 kili kernel: [ 1842.619467] BTRFS info (device sdb2): 
enabling ssd optimizations
+ Oct 16 11:11:42 kili kernel: [ 1842.621633] BTRFS info (device sdb2): 
checking UUID tree
+ Oct 16 11:11:42 kili kernel: [ 1842.627105] BTRFS info (device sdb2): qgroup 
scan completed (inconsistency flag cleared)
+ Oct 16 11:11:42 kili kernel: [ 1842.629891] BTRFS info (device sdb2): qgroup 
scan completed (inconsistency flag cleared)
+ Oct 16 11:11:42 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
+ Oct 16 11:11:42 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dtest.mount: Succeeded.
+ Oct 16 11:11:43 kili systemd[1894]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
+ Oct 16 11:11:43 kili systemd[1]: 
home-ubuntu-autotest-client-tmp-tmp-xfstests\x2dscratch.mount: Succeeded.
+ Oct 16 11:11:43 kili kernel: [ 1842.852837] BTRFS info (device sdb2): disk 
space caching is enabled
+ Oct 16 11:11:43 kili kernel: [ 1842.852839] BTRFS info (device sdb2): has 
skinny extents
+ Oct 16 11:11:43 kili kernel: [ 1842.856849] BTRFS info (device sdb2): 
enabling ssd optimizations
+ Oct 16 11:11:43 kili systemd[1894]: 

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

[Ubuntu Kernel Bot]

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

apport-collect 1848409

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

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

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

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

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

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

Title:
  btrfs/153 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/153  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad)
   --- tests/btrfs/153.out2019-10-16 10:51:13.104701643 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
2019-10-16 11:11:43.217948903 +
   @@ -1,2 +1,5 @@
QA output created by 153
   +pwrite: Disk quota exceeded
   +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
   +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
Silence is golden
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad'
  to see the entire diff) 

  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
   2019-10-16 11:11:43.217948903 +
  @@ -1,2 +1,5 @@
   QA output created by 153
  +pwrite: Disk quota exceeded
  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk quota 
exceeded
  +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk quota 
exceeded
   Silence is golden

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
   crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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 Oct 17 03:03:57 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S2600WTT
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600WTT
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G92187-350
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...:ct23:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600WTT
  dmi.product.sku: SKU 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

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

Title:
  btrfs/156 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/156  [failed, exit status 1]- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad)
   --- tests/btrfs/156.out2019-10-16 10:51:13.104701643 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad
2019-10-16 11:11:52.205883927 +
   @@ -1,2 +1,3 @@
QA output created by 156
   -Silence is golden
   +failed: '/usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch'
   +(see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.full
 for details)
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/156.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad'
  to see the entire diff) 

  
  $ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/156.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad
  --- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/156.out
  2019-10-16 10:51:13.104701643 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad
   2019-10-16 11:11:52.205883927 +
  @@ -1,2 +1,3 @@
   QA output created by 156
  -Silence is golden
  +failed: '/usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch'
  +(see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.full
 for details)

  $ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.full
  # /usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch
  Done, had to relocate 9 out of 9 chunks
  # /usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch
  ERROR: error during balancing 
'/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device
  There may be more info in syslog - try dmesg | tail
  failed: '/usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch'

  
  syslog:
  Oct 16 11:11:44 kili ubuntu: run xfstest btrfs/156
  Oct 16 11:11:44 kili kernel: [ 1844.007779] run fstests btrfs/156 at 
2019-10-16 11:11:44
  Oct 16 11:11:44 kili kernel: [ 1844.228410] BTRFS: device fsid 
e7e53e40-f4fe-4460-b7bc-3dfcf846bc16 devid 1 transid 5 /dev/sdb2
  Oct 16 11:11:44 kili kernel: [ 1844.247603] BTRFS info (device sdb2): disk 
space caching is enabled
  Oct 16 11:11:44 kili kernel: [ 1844.247605] BTRFS info (device sdb2): has 
skinny extents
  Oct 16 11:11:44 kili kernel: [ 1844.247605] BTRFS info (device sdb2): 
flagging fs with big metadata feature
  Oct 16 11:11:44 kili kernel: [ 1844.253106] BTRFS info (device sdb2): 
enabling ssd optimizations
  Oct 16 11:11:44 kili kernel: [ 1844.253767] BTRFS info (device sdb2): 
checking UUID tree
  Oct 16 11:11:48 kili kernel: [ 1848.546002] BTRFS info (device sdb2): 
balance: start -d -m -s
  Oct 16 11:11:48 kili kernel: [ 1848.546141] BTRFS info (device sdb2): 
relocating block group 609222656 flags data
  Oct 16 11:11:49 kili kernel: [ 1848.826415] BTRFS info (device sdb2): found 
57 extents
  Oct 16 11:11:49 kili kernel: [ 1848.834890] BTRFS info (device sdb2): found 
57 extents
  Oct 16 11:11:49 kili kernel: [ 1848.840949] BTRFS info (device sdb2): 
relocating block group 491782144 flags data
  Oct 16 11:11:49 kili kernel: [ 1849.379712] BTRFS info (device sdb2): found 
112 extents
  Oct 16 11:11:49 kili kernel: [ 1849.389757] BTRFS info (device sdb2): found 
112 extents
  Oct 16 11:11:49 kili kernel: [ 1849.395737] BTRFS info (device sdb2): 
relocating block group 374341632 flags data
  Oct 16 11:11:50 kili kernel: [ 1849.943236] BTRFS info (device sdb2): found 
115 extents
  Oct 16 11:11:50 kili kernel: [ 1849.954160] BTRFS info (device sdb2): found 
114 extents
  Oct 16 11:11:50 kili kernel: [ 1849.960252] BTRFS info (device sdb2): 
relocating block group 

[Kernel-packages] [Bug 1848410] [NEW] btrfs/156 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 btrfs/156  [failed, exit status 1]- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad)
 --- tests/btrfs/156.out2019-10-16 10:51:13.104701643 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad
2019-10-16 11:11:52.205883927 +
 @@ -1,2 +1,3 @@
  QA output created by 156
 -Silence is golden
 +failed: '/usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch'
 +(see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.full
 for details)
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/156.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad'
  to see the entire diff) 


$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/156.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/156.out
2019-10-16 10:51:13.104701643 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.out.bad
 2019-10-16 11:11:52.205883927 +
@@ -1,2 +1,3 @@
 QA output created by 156
-Silence is golden
+failed: '/usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch'
+(see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.full
 for details)

$ cat 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/156.full
# /usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch
Done, had to relocate 9 out of 9 chunks
# /usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch
ERROR: error during balancing 
'/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch': No space left on device
There may be more info in syslog - try dmesg | tail
failed: '/usr/bin/btrfs balance start --full-balance 
/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch'


syslog:
Oct 16 11:11:44 kili ubuntu: run xfstest btrfs/156
Oct 16 11:11:44 kili kernel: [ 1844.007779] run fstests btrfs/156 at 2019-10-16 
11:11:44
Oct 16 11:11:44 kili kernel: [ 1844.228410] BTRFS: device fsid 
e7e53e40-f4fe-4460-b7bc-3dfcf846bc16 devid 1 transid 5 /dev/sdb2
Oct 16 11:11:44 kili kernel: [ 1844.247603] BTRFS info (device sdb2): disk 
space caching is enabled
Oct 16 11:11:44 kili kernel: [ 1844.247605] BTRFS info (device sdb2): has 
skinny extents
Oct 16 11:11:44 kili kernel: [ 1844.247605] BTRFS info (device sdb2): flagging 
fs with big metadata feature
Oct 16 11:11:44 kili kernel: [ 1844.253106] BTRFS info (device sdb2): enabling 
ssd optimizations
Oct 16 11:11:44 kili kernel: [ 1844.253767] BTRFS info (device sdb2): checking 
UUID tree
Oct 16 11:11:48 kili kernel: [ 1848.546002] BTRFS info (device sdb2): balance: 
start -d -m -s
Oct 16 11:11:48 kili kernel: [ 1848.546141] BTRFS info (device sdb2): 
relocating block group 609222656 flags data
Oct 16 11:11:49 kili kernel: [ 1848.826415] BTRFS info (device sdb2): found 57 
extents
Oct 16 11:11:49 kili kernel: [ 1848.834890] BTRFS info (device sdb2): found 57 
extents
Oct 16 11:11:49 kili kernel: [ 1848.840949] BTRFS info (device sdb2): 
relocating block group 491782144 flags data
Oct 16 11:11:49 kili kernel: [ 1849.379712] BTRFS info (device sdb2): found 112 
extents
Oct 16 11:11:49 kili kernel: [ 1849.389757] BTRFS info (device sdb2): found 112 
extents
Oct 16 11:11:49 kili kernel: [ 1849.395737] BTRFS info (device sdb2): 
relocating block group 374341632 flags data
Oct 16 11:11:50 kili kernel: [ 1849.943236] BTRFS info (device sdb2): found 115 
extents
Oct 16 11:11:50 kili kernel: [ 1849.954160] BTRFS info (device sdb2): found 114 
extents
Oct 16 11:11:50 kili kernel: [ 1849.960252] BTRFS info (device sdb2): 
relocating block group 256901120 flags data
Oct 16 11:11:50 kili kernel: [ 1850.497052] BTRFS info (device sdb2): found 112 
extents
Oct 16 11:11:50 kili kernel: [ 1850.507137] BTRFS info (device sdb2): found 112 
extents
Oct 16 11:11:50 kili kernel: [ 1850.513496] BTRFS info (device sdb2): 
relocating block group 139460608 flags data
Oct 16 11:11:51 kili kernel: [ 1851.093126] BTRFS info (device sdb2): found 112 
extents
Oct 16 11:11:51 kili kernel: [ 1851.102458] BTRFS info (device sdb2): found 112 
extents
Oct 16 11:11:51 kili kernel: [ 1851.108771] BTRFS info (device sdb2): 
relocating block group 22020096 flags metadata
Oct 16 

[Kernel-packages] [Bug 1730924]

[gbhat]

Hi verdre,

>> went back to a clean kernel and tried disabling L1.2 to fix the command
>> timeout. While that indeed fixed the command timeout issue, the "Firmware
>> wakeup 
failed" issue wasn't fixed.

could you share your changes, with which command timeout is not seen;

Regards,
Ganapathi

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1730924]

[gbhat]

>> 1. Command timeout after second suspend could be recreated in my Surface 4;
more specific observation on this(you could cross check, if possible):
1. timeout happens after a resume, if we see below message in dmesg:
   "mwifiex_pci :02:00.0: Refused to change power state, currently in D0"

2. if device is connected before the 1st suspend, no issue is seen after
1st resume;

3. if device is connected before 2nd suspend(i.e after 1st suspend_resume), 
then issue is seen after 2nd resume

4. if device is not at all connected during suspend_resume stress test, no 
issue is seen

Regards,
Ganapathi

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled

[A.M.Danischewski]

Same deal here on:

Distributor ID: Ubuntu
Description:Ubuntu 19.04
Release:19.04
Codename:   disco

Linux amdubuntu 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05:32 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

I'd just like to clarify that Comment #31 has the appropriate syntax for
multiple disks.

I'm not sure how I had this working before but as of the 5.0.0-29-generic 
kernel - if you have multiple entries in your 
/etc/modprobe.d/blacklist-.conf: 
options usb-storage quirks=0x0bc2:0xab20:u
options usb-storage quirks=0x0bc2:0xab00:u

They will clobber each other, so per the above you only would be
blacklisting 0x0bc2:0xab00:u.

You don't need 0x, if you want to cut down on the syntax a bit, but you do need 
to put them all on the same line:  
/etc/modprobe.d/blacklist-.conf: 
options usb-storage quirks=0bc2:ab20:u,0bc2:ab00:u,0bc2:3322:u,152d:1561:u

Note: if you have a /etc/modprobe.d/usb3-disk-bug.conf and create your own 
blacklist file make sure you remove the "options usb-storage quirks..." entries 
from usb3-disk-bug.conf to prevent them from clobbering your blacklist file. 
 
Update your initramfs: 
sudo update-initramfs -u

And reboot.

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

Title:
  Seagate external drive causes SCSI bus resets when UAS enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
  continuous SCSI bus resets by default. As a workaround, disabling UAS
  causes the device to work fine.

  To disable UAS, I created a file in /etc/modprobe.d with the following 
contents:
  options usb-storage quirks=0bc2:02322:u

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun May 22 22:02:26 2016
  InstallationDate: Installed on 2012-10-07 (1323 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago)

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

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

[Kernel-packages] [Bug 1848409] [NEW] btrfs/153 from ubuntu_xfstests_btrfs failed on D

[Po-Hsu Lin]

Public bug reported:

Issue found on node amd64 node "kili"

 btrfs/153  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad)
 --- tests/btrfs/153.out2019-10-16 10:51:13.104701643 +
 +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
2019-10-16 11:11:43.217948903 +
 @@ -1,2 +1,5 @@
  QA output created by 153
 +pwrite: Disk quota exceeded
 +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
 +/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk 
quota exceeded
  Silence is golden
 ...
 (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad'
  to see the entire diff) 


$ diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
--- 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/btrfs/153.out
2019-10-16 10:51:13.104701643 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//btrfs/153.out.bad
 2019-10-16 11:11:43.217948903 +
@@ -1,2 +1,5 @@
 QA output created by 153
+pwrite: Disk quota exceeded
+/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk quota 
exceeded
+/home/ubuntu/autotest/client/tmp/tmp/xfstests-scratch/testfile2: Disk quota 
exceeded
 Silence is golden

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-31-generic 5.0.0-31.33
ProcVersionSignature: User Name 5.0.0-31.33-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 16 10:41 seq
 crw-rw 1 root audio 116, 33 Oct 16 10:41 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
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 Oct 17 03:03:57 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S2600WTT
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=72dbdd83-0e2a-4fdd-99ca-70869e30b925 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-31-generic N/A
 linux-backports-modules-5.0.0-31-generic  N/A
 linux-firmware1.178.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/19/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SE5C610.86B.01.01.1008.031920151331
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: S2600WTT
dmi.board.vendor: Intel Corporation
dmi.board.version: G92187-350
dmi.chassis.asset.tag: 
dmi.chassis.type: 23
dmi.chassis.vendor: ...
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.1008.031920151331:bd03/19/2015:svnIntelCorporation:pnS2600WTT:pvr:rvnIntelCorporation:rnS2600WTT:rvrG92187-350:cvn...:ct23:cvr..:
dmi.product.family: Family
dmi.product.name: S2600WTT
dmi.product.sku: SKU Number
dmi.product.version: 
dmi.sys.vendor: Intel Corporation

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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


** Tags: 5.0 amd64 apport-bug disco sru-20190930 ubuntu-xfstests-btrfs 
uec-images

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

** Tags added: 5.0

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

** Tags added: ubuntu-xfstests-btrfs

** Tags added: sru-20190930

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

Title:
  btrfs/153 from ubuntu_xfstests_btrfs failed on D

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

Bug description:
  Issue found on node amd64 node "kili"

   btrfs/153  - output mismatch (see 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full
  brightness after wake up

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Every time when I open up my lid of my laptop, and wake up my system
  from sleeping,the screen will return to full brightness.Either I press
  the brightness - or + button,the brightness will back to normal
  immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 00:05:56 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:380c]
  InstallationDate: Installed on 2019-09-28 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN30WW:bd07/04/2018:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.sku: LENOVO_MT_81BR_BU_idea_FM_ideapad 720S-13ARR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1848360] Re: Screen alway returns to full brightness after wake up

[Daniel van Vugt]

** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Screen alway returns to full brightness after wake up
+ [amdgpu] Screen alway returns to full brightness after wake up

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

** Summary changed:

- [amdgpu] Screen alway returns to full brightness after wake up
+ [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full brightness 
after wake up

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

Title:
  [amdgpu] [Lenovo ideapad 720S-13ARR] Screen always returns to full
  brightness after wake up

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Every time when I open up my lid of my laptop, and wake up my system
  from sleeping,the screen will return to full brightness.Either I press
  the brightness - or + button,the brightness will back to normal
  immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 00:05:56 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:380c]
  InstallationDate: Installed on 2019-09-28 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=d149e099-9234-443a-8b59-fa39ca1a8631 ro idle=nomwait 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN30WW:bd07/04/2018:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.sku: LENOVO_MT_81BR_BU_idea_FM_ideapad 720S-13ARR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work

[Daniel van Vugt]

** Summary changed:

- Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an 
i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it
+ Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but 
kernels 5.0/5.2 work

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

Title:
  Lightdm is just a black screen when booting kernel 5.3 on an i5-6500,
  but kernels 5.0/5.2 work

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg freeze at boot on Intel Corporation HD Graphics 530 with 
linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan 
Ermine (development branch).
  If i boot with linux-image-5.0.0-31-generic the Xorg works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 14 11:15:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  

[Kernel-packages] [Bug 1846073] Re: disco/linux-raspi2: 5.0.0-1020.20 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  variant: debs

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

Title:
  disco/linux-raspi2: 5.0.0-1020.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  variant: debs

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

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

[Kernel-packages] [Bug 1846089] Re: disco/linux-oracle: 5.0.0-1005.9 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-oracle-edge: bug 1846088
  variant: debs

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

Title:
  disco/linux-oracle: 5.0.0-1005.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  New
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 verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-oracle-edge: bug 1846088
  variant: debs

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

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

[Kernel-packages] [Bug 1846086] Re: disco/linux-gcp: 5.0.0-1021.21 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-gcp: bug 1846082
bionic/linux-gke-5.0: bug 1847930
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1021.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  New
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 verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-gcp: bug 1846082
bionic/linux-gke-5.0: bug 1847930
  variant: debs

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

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

[Kernel-packages] [Bug 1846079] Re: disco/linux-azure: 5.0.0-1023.24 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-azure: bug 1846078
  variant: debs

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

Title:
  disco/linux-azure: 5.0.0-1023.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  New
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 stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-azure: bug 1846078
  variant: debs

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

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

[Kernel-packages] [Bug 1846091] Re: disco/linux-snapdragon: 5.0.0-1024.25 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  variant: debs

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

Title:
  disco/linux-snapdragon: 5.0.0-1024.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  variant: debs

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

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

[Kernel-packages] [Bug 1846087] Re: disco/linux-kvm: 5.0.0-1020.21 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  variant: debs

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

Title:
  disco/linux-kvm: 5.0.0-1020.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
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 verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  variant: debs

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

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

[Kernel-packages] [Bug 1846075] Re: disco/linux-aws: 5.0.0-1019.21 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-aws-edge: bug 1846074
  variant: debs

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

Title:
  disco/linux-aws: 5.0.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
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 verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846097
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:57 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-aws-edge: bug 1846074
  variant: debs

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

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

[Kernel-packages] [Bug 1846097] Re: disco/linux: 5.0.0-32.34 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ reason:
+   promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-bluefield: bug 1846096
bionic/linux-hwe: bug 1846092
bionic/linux-oem-osp1: bug 1846095
disco/linux-aws: bug 1846075
disco/linux-azure: bug 1846079
disco/linux-gcp: bug 1846086
disco/linux-kvm: bug 1846087
disco/linux-oracle: bug 1846089
disco/linux-raspi2: bug 1846073
disco/linux-snapdragon: bug 1846091
  variant: debs

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

Title:
  disco/linux: 5.0.0-32.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  New
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 verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Security
  phase-changed: Wednesday, 16. October 2019 06:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
  trackers:
bionic/linux-bluefield: bug 1846096
bionic/linux-hwe: bug 1846092
bionic/linux-oem-osp1: bug 1846095
disco/linux-aws: bug 1846075
disco/linux-azure: bug 1846079
disco/linux-gcp: bug 1846086
disco/linux-kvm: bug 1846087
disco/linux-oracle: bug 1846089
disco/linux-raspi2: bug 1846073
disco/linux-snapdragon: bug 1846091
  variant: debs

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

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

[Kernel-packages] [Bug 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines

[Hui Wang]

** Tags added: verification-done-bionic verification-done-disco

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

Title:
  update firmware for sound sof driver to fix the hang issue on several
  Dell machines

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  We expect this firmware update could be released with 19.10

  [Impact]
  We have a couple of Dell machines, after installing the system, it
  will hang randomly, and this issue was reported by factory, they met
  this issue a couple of times. Then we tried to reproduce this issue,
  finally reproduced it.

  [Fix]
  Intel debugged this issue as well, and they provided 4 kernel patches
  and a new firmware, we tested them, they really can fix the issue.
  And the patches were sent the SRU already, now it is time to update
  firmware.

  [Test Case]
  Install the system repeatedly and there is no hang issue anymore.

  [Regression Risk]
  Low, Intel told us there is no ABI change for the firmware, so
  it is safe to run this firmware both with the old driver (not applied
  those 4 patches) and the new driver (applied those 4 patches).

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

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

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

[Luke Williams]

So the latest Disco Kernel (Bionic HWE 5.0.0-31-generic) seems to have fixed 
all the issues with the touchpad. I can now touch the touchpad with all 5 
fingers and it doesn't lock up and require me to restart the multitouch-hid 
module. 
It also seems that this version of the kernel also fixed the keyboard issues 
where the brightness Fn keys work as well as the keyboard brightness, airplane 
mode and sleep mode.

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

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Triaged

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

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

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

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

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

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

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

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

[Kernel-packages] [Bug 1848212] Re: Optane PM access times are much longer than they should be

[steve heller]

I believe this bug is due to a change that causes files on a dax volume
to be allocated as sparse files, so that every write to a new allocation
unit causes another physical allocation. The previous behavior was to
allocate the whole file up to the allocated size as one operation.

This is just by observing the behavior and running experiments to try to
figure it out. I haven't looked at the code.

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

Title:
  Optane PM access times are much longer than they should be

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have 4 128GB Optane DC Persistent Memory devices in my server,
  assigned to AppDirect access (i.e., accessed via memory-mapping at the
  cache line level), and have run into a severe performance issue with
  the latest kernel 5.0.0-31.

  I realize that not many people have this storage type as yet, but it
  is becoming increasingly important in the server world, so I think
  this bug is pretty important.

  Bug details:

  When running with kernel 5.0.0-29, write access times to the Optane PM
  devices are in the sub-microsecond range, as they should be.

  When running with kernel 5.0.0-31, write access times are much slower,
  averaging in the 30 microsecond range, until a large number of writes
  (see below) have been executed. Then they return to normal speed.

  My application is a hash table implementation optimized for the Optane
  PM devices (see webpage at www.threemisses.com). Since it is a hash
  table, it has very poor locality of reference, and is filled
  "randomly", so I don't know exactly what the sequence of writes is.

  However, I can say that the speed is very slow until the fill ratio of
  the hash table is about 50%, then it returns to the normal sub-
  microsecond range.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Oct 15 09:01:06 2019
  InstallationDate: Installed on 2019-09-02 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   lono wireless extensions.

   eno0  no wireless extensions.

   enp181s0f1  no wireless extensions.
  MachineType: Supermicro SYS-7039A-I
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=3239f211-86a3-44bb-8251-62037ebea848 ro transparent_hugepage=always 
quiet splash nomodeset vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: ZM193S000653
  dmi.board.name: X11DAi-N
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd03/06/2019:svnSupermicro:pnSYS-7039A-I:pvr123456789:rvnSupermicro:rnX11DAi-N:rvr1.02:cvnSupermicro:ct1:cvr123456789:
  dmi.product.family: SMC X11
  dmi.product.name: SYS-7039A-I
  dmi.product.sku: 097A15D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1847801] Re: bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Monday, 14. October 2019 14:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1059.68 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
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 verification-testing series:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1846131
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Monday, 14. October 2019 14:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1845355] Re: Support Hi1620 zip hw accelerator

[dann frazier]

** Changed in: kunpeng920/ubuntu-19.04
   Status: Fix Committed => Fix Released

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

Title:
  Support Hi1620 zip hw accelerator

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Hi1620 SoC has an onboard zip accelerator that is currently not exposd to 
userspace by Ubuntu.

  [Test Case]
  ubuntu@scobee:~$ dmesg | grep zip
  [   29.688222] hisi_zip :75:00.0: enabling device ( -> 0002)
  [   29.697720] hisi_zip :b5:00.0: enabling device ( -> 0002)
  ubuntu@scobee:~$ lspci | grep ZIP
  75:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)
  b5:00.0 Processing accelerators: Huawei Technologies Co., Ltd. HiSilicon ZIP 
Engine (rev 21)

  [Fix]
  263c9959c9376 crypto: hisilicon - add queue management driver for HiSilicon 
QM module
  dfed0098ab91f crypto: hisilicon - add hardware SGL support
  62c455ca853e3 crypto: hisilicon - add HiSilicon ZIP accelerator support
  79e09f30eeba8 crypto: hisilicon - add SRIOV support for ZIP
  8201fdf49ff09 Documentation: Add debugfs doc for hisi_zip
  72c7a68d2ea34 crypto: hisilicon - add debugfs for ZIP and QM
  ad3f0a93b639c MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller 
driver
  00ae05db583a7 crypto: hisilicon - fix kbuild warnings
  db01e4818bbda crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
  5c0861989cc19 crypto: hisilicon - init curr_sgl_dma to fix compile warning
  902f0babf5457 crypto: hisilicon - add missing single_release
  1ed2002f891dc crypto: hisilicon - fix error handle in hisi_zip_create_req_q
  b395ed4f948a2 crypto: hisilicon - Fix warning on printing %p with dma_addr_t
  62a9d9fc7a210 crypto: hisilicon - Fix return value check in 
hisi_zip_acompress()
  bf6a7a5ad6fa6 crypto: hisilicon - avoid unused function warning

  [Regression Risk]
  This is a new driver which will only load automatically on systems that 
expose a supported PCI device.

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

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

[Kernel-packages] [Bug 1847628] Re: When using swap in ZFS, system stops when you start using swap

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 19.10.21

---
ubiquity (19.10.21) eoan; urgency=medium

  [ Dimitri John Ledkov ]
  * scripts/plugininstall.py: skip installing extras with multiarch
dependencies in the first pass.

  [ Mathieu Trudel-Lapierre ]
  * Updated translations from Launchpad.

  [ Adam Conrad ]
  * Rewrite zsys-setup swap handling to use a swap partition (LP: #1847628)

 -- Adam Conrad   Wed, 16 Oct 2019 17:36:10 +0100

** Changed in: ubiquity (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  When using swap in ZFS, system stops when you start using swap

Status in Release Notes for Ubuntu:
  Fix Released
Status in Native ZFS for Linux:
  Unknown
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  # Problem

  When using swap in ZFS, system stops when you start using swap.

  > stress --vm 100

  if you doing swapoff will only occur OOM and the system will not stop.

  # Environment

  jehos@MacBuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10
  Codename:   eoan

  jehos@MacBuntu:~$ dpkg -l | grep zfs
  ii  libzfs2linux   0.8.1-1ubuntu13
 amd64OpenZFS filesystem library for Linux
  ii  zfs-initramfs  0.8.1-1ubuntu13
 amd64OpenZFS root filesystem capabilities for Linux - initramfs
  ii  zfs-zed0.8.1-1ubuntu13
 amd64OpenZFS Event Daemon
  ii  zfsutils-linux 0.8.1-1ubuntu13
 amd64command-line tools to manage OpenZFS filesystems

  jehos@MacBuntu:~$ uname -a
  Linux MacBuntu 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  jehos@MacBuntu:~$ zpool list
  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
  bpool  1.88G  66.1M  1.81G- -  - 3%  1.00xONLINE  
-
  rpool   230G   124G   106G- - 9%53%  1.00xONLINE  
-

  jehos@MacBuntu:~$ zfs get all rpool/swap
  NAMEPROPERTY  VALUESOURCE
  rpool/swap  type  volume   -
  rpool/swap  creation  목 10월 10 15:56 2019  -
  rpool/swap  used  2.13G-
  rpool/swap  available 98.9G-
  rpool/swap  referenced72K  -
  rpool/swap  compressratio 1.11x-
  rpool/swap  reservation   none default
  rpool/swap  volsize   2G   local
  rpool/swap  volblocksize  4K   -
  rpool/swap  checksum  on   default
  rpool/swap  compression   zle  local
  rpool/swap  readonly  off  default
  rpool/swap  createtxg 34   -
  rpool/swap  copies1default
  rpool/swap  refreservation2.13Glocal
  rpool/swap  guid  18209330213704683244 -
  rpool/swap  primarycache  metadata local
  rpool/swap  secondarycachenone local
  rpool/swap  usedbysnapshots   0B   -
  rpool/swap  usedbydataset 72K  -
  rpool/swap  usedbychildren0B   -
  rpool/swap  usedbyrefreservation  2.13G-
  rpool/swap  logbias   throughput   local
  rpool/swap  objsetid  393  -
  rpool/swap  dedup off  default
  rpool/swap  mlslabel  none default
  rpool/swap  sync  always   local
  rpool/swap  refcompressratio  1.11x-
  rpool/swap  written   72K  -
  rpool/swap  logicalused   40K  -
  rpool/swap  logicalreferenced 40K  -
  rpool/swap  volmode   default  default
  rpool/swap  snapshot_limitnone default
  rpool/swap  snapshot_countnone default
  rpool/swap  snapdev   hidden   default
  rpool/swap  context   none default
  rpool/swap  fscontext none default
  rpool/swap  defcontextnone

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

[Sean Feole]

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

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

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux-aws source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in linux-aws source package in Eoan:
  New

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

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

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "crypto_user02 crypto_user02" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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 Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': '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.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error

[Manoj Iyer]

SRU for Eoan: https://lists.ubuntu.com/archives/kernel-
team/2019-October/104757.html

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

Title:
  [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check
  Error

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New

Bug description:
  [IMPACT]
  MCE test renders the system unresponsive on P9 open power hardware 
(Withersoon)

  [TEST]
  A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see 
the [OTHER] section for test details and comment #7 for results with the PPA 
kernel. 

  [FIX]
  IBM has identified the following patch that fixes this issue:
  commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee
  Author: Balbir Singh 
  Date:   Tue Aug 20 13:43:47 2019 +0530

  powerpc/mce: Fix MCE handling for huge pages

  [REGRESSION POTENTIAL]
  The patch is applicable the powerpc architecture and limited in scope to MCE 
handling for huge pages. Patch does not touch any generic code. Regression if 
any is limited to powerpc MCE handling.

  [OTHER]
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-05-07 
23:31:20 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images built  
from the upstream op-build git tree.

  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
   open-power-witherspoon-v2.3-rc2-58-g59fd0743
  buildroot-2019.02.2-17-g93b841d204
  skiboot-v6.3-rc2
  hostboot-19a436e
  occ-58e422d
  linux-5.0.9-openpower1-p3a4d5a4
  petitboot-v1.10.3
  machine-xml-a6f4df3
  hostboot-binaries-hw043019a.940
  capp-ucode-p9-dd2-v4
  sbe-249671d
  hcode-hw040319a.940

  Then enable sw xstop manually by using below command:

  root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable
  root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config
  "ibm,skiboot" Partition
  --
  experimental-fast-reset=1
  snarf-mode=noo
  opal-sw-xstop=enable

  Then from the Linux HOST injected the MCE UE Error on the machine as
  follows:

  root@ltc-wspoon11:~# ./probe_cpus.sh -L
  CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs:  0 1 2 3
  CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs:  4 5 6 7
  CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs:  8 9 10 11
  CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs:  12 13 14 15
  CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs:  16 17 18 19
  CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs:  20 21 22 23
  CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs:  24 25 26 27
  CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs:  28 29 30 31
  CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs:  32 33 34 35
  CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs:  36 37 38 39
  CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs:  40 41 42 43
  CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs:  44 45 46 47
  CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs:  48 49 50 51
  CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs:  52 53 54 55
  CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs:  56 57 58 59
  CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs:  60 61 62 63
  CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs:  64 65 66 67
  CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs:  68 69 70 71
  CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs:  72 73 74 75
  CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs:  76 77 78 79
  CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs:  80 81 82 83
  CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs:  84 85 86 87
  CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs:  88 89 90 91
  CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs:  92 93 94 95
  CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs:  96 97 98 99
  CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs:  100 101 102 103
  CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs:  104 105 106 107
  CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs:  108 109 110 111
  CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs:  112 113 114 115
  CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs:  116 117 118 119
  CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs:  120 121 122 123
  CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs:  124 125 126 127
  CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs:  128 129 130 131
  CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs:  132 133 134 135
  CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs:  136 137 138 139
  CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs:  140 141 142 143

  -
  p[0]
     eq[0,1,2,3,4,5]
     ex[0,1,3,4,5,6,8,9,10]
  c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21]
  p[8]
     eq[1,2,3,4,5]
     ex[3,4,5,6,7,8,9,10,11]
  

[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error

[Manoj Iyer]

** Description changed:

+ [IMPACT]
+ MCE test renders the system unresponsive on P9 open power hardware 
(Withersoon)
+ 
+ [TEST]
+ A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see 
the [OTHER] section for test details and comment #7 for results with the PPA 
kernel. 
+ 
+ [FIX]
+ IBM has identified the following patch that fixes this issue:
+ commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee
+ Author: Balbir Singh 
+ Date:   Tue Aug 20 13:43:47 2019 +0530
+ 
+ powerpc/mce: Fix MCE handling for huge pages
+ 
+ [REGRESSION POTENTIAL]
+ The patch is applicable the powerpc architecture and limited in scope to MCE 
handling for huge pages. Patch does not touch any generic code. Regression if 
any is limited to powerpc MCE handling.
+ 
+ [OTHER]
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2019-05-07 
23:31:20 ==
  Install a P9 Open Power Hardware with the latest OP930 Firmware images built  
from the upstream op-build git tree.
  
  root@witherspoon:~# cat /etc/os-release
  ID="openbmc-phosphor"
  NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
  VERSION="ibm-v2.3"
  VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0"
  PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 
ibm-v2.3"
  BUILD_ID="ibm-v2.3-476-g2d622cb-r32"
  root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION
-   open-power-witherspoon-v2.3-rc2-58-g59fd0743
- buildroot-2019.02.2-17-g93b841d204
- skiboot-v6.3-rc2
- hostboot-19a436e
- occ-58e422d
- linux-5.0.9-openpower1-p3a4d5a4
- petitboot-v1.10.3
- machine-xml-a6f4df3
- hostboot-binaries-hw043019a.940
- capp-ucode-p9-dd2-v4
- sbe-249671d
- hcode-hw040319a.940
+  open-power-witherspoon-v2.3-rc2-58-g59fd0743
+ buildroot-2019.02.2-17-g93b841d204
+ skiboot-v6.3-rc2
+ hostboot-19a436e
+ occ-58e422d
+ linux-5.0.9-openpower1-p3a4d5a4
+ petitboot-v1.10.3
+ machine-xml-a6f4df3
+ hostboot-binaries-hw043019a.940
+ capp-ucode-p9-dd2-v4
+ sbe-249671d
+ hcode-hw040319a.940
  
  Then enable sw xstop manually by using below command:
  
  root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable
  root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config
  "ibm,skiboot" Partition
  --
  experimental-fast-reset=1
  snarf-mode=noo
  opal-sw-xstop=enable
  
  Then from the Linux HOST injected the MCE UE Error on the machine as
  follows:
  
  root@ltc-wspoon11:~# ./probe_cpus.sh -L
  CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs:  0 1 2 3
  CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs:  4 5 6 7
  CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs:  8 9 10 11
  CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs:  12 13 14 15
  CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs:  16 17 18 19
  CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs:  20 21 22 23
  CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs:  24 25 26 27
  CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs:  28 29 30 31
  CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs:  32 33 34 35
  CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs:  36 37 38 39
  CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs:  40 41 42 43
  CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs:  44 45 46 47
  CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs:  48 49 50 51
  CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs:  52 53 54 55
  CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs:  56 57 58 59
  CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs:  60 61 62 63
  CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs:  64 65 66 67
  CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs:  68 69 70 71
  CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs:  72 73 74 75
  CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs:  76 77 78 79
  CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs:  80 81 82 83
  CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs:  84 85 86 87
  CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs:  88 89 90 91
  CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs:  92 93 94 95
  CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs:  96 97 98 99
  CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs:  100 101 102 103
  CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs:  104 105 106 107
  CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs:  108 109 110 111
  CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs:  112 113 114 115
  CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs:  116 117 118 119
  CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs:  120 121 122 123
  CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs:  124 125 126 127
  CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs:  128 129 130 131
  CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs:  132 133 134 135
  CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs:  136 137 138 139
  CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs:  140 141 142 143
  
  -
  p[0]
-eq[0,1,2,3,4,5]
-ex[0,1,3,4,5,6,8,9,10]
- c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21]
+    eq[0,1,2,3,4,5]
+    ex[0,1,3,4,5,6,8,9,10]
+ c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21]
  p[8]
-eq[1,2,3,4,5]
-ex[3,4,5,6,7,8,9,10,11]
- c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]

[Kernel-packages] [Bug 1847139] Re: [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04

[Marcelo Cerri]

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

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

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

Title:
  [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04
  and 18.04

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  Microsoft would like to request the following mainline commit be added to 
linux-azure 16.04 and 18.04:
  f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain 
numbers

  This commit was added to mainline in v5.4-rc1~63^2~8^2

  This was recommended by Azure host team, the bytes 4, 5 have more
  uniqueness(info entropy) than bytes 8, 9, so we should use them as the
  PCI domain numbers.

  This patch should be added to both 16.04 and 18.04 images.

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

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

[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?

[Joe Barnett]

** Tags added: patch-accepted-upstream

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

Title:
  apparent memory usage regression - not getting freed?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In eoan on a 5.3 kernel, have noticed a few incidents of the system
  becoming sluggish/unresponsive, which appears to be caused by low
  available memory.  top is reporting 13 of 16G are "used", but adding
  up the memory reported by top sorted by memory usage appears like it
  should be closer to 3-4G "used".

  Attaching two top screenshots, one shows 3.3G used and system behaving
  well, the other shows 14G used and system lagging.  In both cases,
  approximately the same programs are being run taking up approximately
  the same amount of resident memory, so not sure where all the memory
  usage is coming from.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-10-generic 5.3.0-10.11
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   5046 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 22 21:26:02 2019
  InstallationDate: Installed on 2019-08-17 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint 
Device 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash 
usbcore.dyndbg=+p vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

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

[ALinuxUser]

dr_strangehate:

Thanks.

I keep a Windows-to-Go drive around for just this sort of nonsense. I
haven't run it for months. Running it now, and running the Lenovo update
program, the only firmware update that I see (as against Windows
software updates) is for Intel ME. So I suspect the following. I have
the firmware update that you had in mind installed *already* (installed
earlier via the same method) and it does not fix the problem for me.

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1848367] [NEW] Disco update: upstream stable patchset 2019-10-16

[Kamal Mostafa]

Public bug reported:

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 2019-10-16

Ported from the following upstream stable releases:
v4.19.77, v5.2.19

   from git://git.kernel.org/

arcnet: provide a buffer big enough to actually receive packets
cdc_ncm: fix divide-by-zero caused by invalid wMaxPacketSize
macsec: drop skb sk before calling gro_cells_receive
net/phy: fix DP83865 10 Mbps HDX loopback disable function
net: qrtr: Stop rx_worker before freeing node
net/sched: act_sample: don't push mac header on ip6gre ingress
net_sched: add max len check for TCA_KIND
nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs
openvswitch: change type of UPCALL_PID attribute to NLA_UNSPEC
ppp: Fix memory leak in ppp_write
sch_netem: fix a divide by zero in tabledist()
skge: fix checksum byte order
usbnet: ignore endpoints with invalid wMaxPacketSize
usbnet: sanity checking of packet sizes and device mtu
net: sched: fix possible crash in tcf_action_destroy()
tcp: better handle TCP_USER_TIMEOUT in SYN_SENT state
net/mlx5: Add device ID of upcoming BlueField-2
nfp: flower: prevent memory leak in nfp_flower_spawn_phy_reprs
ALSA: hda: Flush interrupts on disabling
regulator: lm363x: Fix off-by-one n_voltages for lm3632 ldo_vpos/ldo_vneg
ASoC: tlv320aic31xx: suppress error message for EPROBE_DEFER
ASoC: sgtl5000: Fix of unmute outputs on probe
ASoC: sgtl5000: Fix charge pump source assignment
firmware: qcom_scm: Use proper types for dma mappings
dmaengine: bcm2835: Print error in case setting DMA mask fails
leds: leds-lp5562 allow firmware files up to the maximum length
media: dib0700: fix link error for dibx000_i2c_set_speed
media: mtk-cir: lower de-glitch counter for rc-mm protocol
media: exynos4-is: fix leaked of_node references
media: hdpvr: Add device num check and handling
media: i2c: ov5640: Check for devm_gpiod_get_optional() error
time/tick-broadcast: Fix tick_broadcast_offline() lockdep complaint
sched/fair: Fix imbalance due to CPU affinity
sched/core: Fix CPU controller for !RT_GROUP_SCHED
x86/apic: Make apic_pending_intr_clear() more robust
sched/deadline: Fix bandwidth accounting at all levels after offline migration
x86/reboot: Always use NMI fallback when shutdown via reboot vector IPI fails
x86/apic: Soft disable APIC before initializing it
ALSA: hda - Show the fatal CORB/RIRB error more clearly
ALSA: i2c: ak4xxx-adda: Fix a possible null pointer dereference in 
build_adc_controls()
EDAC/mc: Fix grain_bits calculation
media: iguanair: add sanity checks
base: soc: Export soc_device_register/unregister APIs
ALSA: usb-audio: Skip bSynchAddress endpoint check if it is invalid
ia64:unwind: fix double free for mod->arch.init_unw_table
EDAC/altera: Use the proper type for the IRQ status bits
ASoC: rsnd: don't call clk_get_rate() under atomic context
arm64/prefetch: fix a -Wtype-limits warning
md/raid1: end bio when the device faulty
md: don't call spare_active in md_reap_sync_thread if all member devices can't 
work
md: don't set In_sync if array is frozen
media: media/platform: fsl-viu.c: fix build for MICROBLAZE
ACPI / processor: don't print errors for processorIDs == 0xff
loop: Add LOOP_SET_DIRECT_IO to compat ioctl
EDAC, pnd2: Fix ioremap() size in dnv_rd_reg()
efi: cper: print AER info of PCIe fatal error
firmware: arm_scmi: Check if platform has released shmem before using
sched/fair: Use rq_lock/unlock in online_fair_sched_group
idle: Prevent late-arriving interrupts from disrupting offline
media: gspca: zero usb_buf on error
perf config: Honour $PERF_CONFIG env var to specify alternate .perfconfig
perf test vfs_getname: Disable ~/.perfconfig to get default output
media: mtk-mdp: fix reference count on old device tree
media: fdp1: Reduce FCP not found message level to debug
media: em28xx: modules workqueue not inited for 2nd device
media: rc: imon: Allow iMON RC protocol for ffdc 7e device
dmaengine: iop-adma: use correct printk format strings
perf record: Support aarch64 random socket_id assignment
media: vsp1: fix memory leak of dl on error return path
media: i2c: ov5645: Fix power sequence
media: omap3isp: Don't set streaming state on random subdevs
media: imx: mipi csi-2: Don't fail if initial state times-out
net: lpc-enet: fix printk format strings
m68k: Prevent some compiler warnings in Coldfire builds
ARM: dts: imx7d: cl-som-imx7: make ethernet work again
ARM: dts: imx7-colibri: disable HS400
media: radio/si470x: kill urb on error
media: hdpvr: add terminating 0 at end of string
ASoC: uniphier: Fix double reset assersion 

[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?

[Joe Barnett]

in drm-next: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
next=06f7f57e87d09900a7c3109a357b73521ab40771

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

Title:
  apparent memory usage regression - not getting freed?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In eoan on a 5.3 kernel, have noticed a few incidents of the system
  becoming sluggish/unresponsive, which appears to be caused by low
  available memory.  top is reporting 13 of 16G are "used", but adding
  up the memory reported by top sorted by memory usage appears like it
  should be closer to 3-4G "used".

  Attaching two top screenshots, one shows 3.3G used and system behaving
  well, the other shows 14G used and system lagging.  In both cases,
  approximately the same programs are being run taking up approximately
  the same amount of resident memory, so not sure where all the memory
  usage is coming from.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-10-generic 5.3.0-10.11
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   5046 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 22 21:26:02 2019
  InstallationDate: Installed on 2019-08-17 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 004: ID 27c6:5395 HTMicroelectronics Goodix Fingerprint 
Device 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic 
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash 
usbcore.dyndbg=+p vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1848075] Re: eoan server image does not boot on RPI3-A+

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1848247
   3A+ boot failure on Eoan

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

Title:
  eoan server image does not boot on RPI3-A+

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I've tried with both the  20191010.1 and  20191012 image, and it boots
  on all other pi devices I have, but not on the rpi3-a+.  On the serial
  console, it only gets as far as "Starting kernel..." but over hdmi,
  there are some more details reported. I'll try to attach a screenshot
  in a moment.

  After talking to Dave Jones about this, it sounds like some dtb files
  are missing to make this work on a+

  From the 20191012 image:
  ii  linux-raspi25.3.0.1007.3arm64
Complete Linux kernel for the BCM2709 architecture.
  ii  linux-firmware-raspi2   1.20190819-0ubuntu2 arm64
Raspberry Pi 2/3/4 GPU firmware and bootloaders

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

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

[Kernel-packages] [Bug 1848013] Re: liburing package missing for >= 5.1 kernels

[Bryce Harrington]

Thanks for this bug report, it does look like liburing would be worthy
of packaging and inclusion in debian and ubuntu, although I don't think
it's correct to have this filed against libaio.  Instead I'm tagging it
as 'needs packaging', per the New Package Policy, which covers this
situation:  https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages

It sounds like a 0.2 release of liburing is pending, and since FF for eoan has 
already closed, maybe worth waiting until 0.2 is out:
https://www.mail-archive.com/linux-block@vger.kernel.org/msg39689.html

Fwiw, there is a RPM package of 0.1
(https://pkgs.org/download/liburing), and from its .spec file the
packaging looks super straightforward.  Hopefully someone will grab it
from the needs-packaging queue soon.  Or, if you'd be interested in
taking a first crack at the deb packaging, that would certainly be a
great way to get this moved forward.


** Tags added: needs-packaging

** Package changed: libaio (Ubuntu) => ubuntu

** Summary changed:

- liburing package missing for >= 5.1 kernels
+ [needs-packaging] liburing package needed for >= 5.1 kernels

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

Title:
  [needs-packaging] liburing package needed for >= 5.1 kernels

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

Bug description:
  eoan will ship with a 5.3 kernel and has support for the io_uring
  interface.

  In order to allow applications to use that the userspace library
  liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in
  addition to the 5.3 kernel.

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

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

[Kernel-packages] [Bug 1843775] Re: [CML-U] Comet lake platform need ISH driver support

[Kleber Sacilotto de Souza]

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

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

Title:
  [CML-U] Comet lake platform need ISH driver support

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  New

Bug description:
  [Impact]
  Enable Integrated Sensor Hub (ISH) driver for Comet lake platform

  CML-U ISH device_ID is: 02fc

  a50e8e2ecc1428df28c748c6af6255eb65faf9f3

  Target Release: 19.10
  Target Kernel: 5.1

  [Test case]
  Boot the kernel on a CML machine and check that the ISH driver is used.

  
  [Regression potential]
  none, it just adds a device id for ISH

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

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

[Kernel-packages] [Bug 1848013] Re: liburing package missing for >= 5.1 kernels

[Bryce Harrington]

** Changed in: libaio (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  liburing package missing for >= 5.1 kernels

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

Bug description:
  eoan will ship with a 5.3 kernel and has support for the io_uring
  interface.

  In order to allow applications to use that the userspace library
  liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in
  addition to the 5.3 kernel.

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

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

[Kernel-packages] [Bug 1846486] Re: revert the revert of ext4: make __ext4_get_inode_loc plug

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Eoan)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

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

Title:
  revert the revert of ext4: make __ext4_get_inode_loc plug

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

Bug description:
  == SRU Justification Eoan ==

  Now that 5.4 contains a fix to the bootup regression due to the lack
  of entropy at bootable we should apply this fix and also revert the
  revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".

  == Fix ==

  So, to clarify, apply the two upstream 5.4-rc commits:

  commit 50ee7529ec4500c88f8664560770a7a1b65db72b
  Author: Linus Torvalds 
  Date:   Sat Sep 28 16:53:52 2019 -0700

  random: try to actively add entropy rather than passively wait for
  it

  commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
  Author: Linus Torvalds 
  Date:   Sun Sep 29 17:59:23 2019 -0700

  Revert "Revert "ext4: make __ext4_get_inode_loc plug""

  I've benchmarked the Eoan kernel with these two patches and found theo
  following speed improvements on an i7-3770 CPU @ 3.40GHz with 8GB and a
  WDC WD10EZEX-21WN4A HDD (7200RPM, 64MB cache).

  git grep of the kernel: 0.14%
  building fwts: 0.40%
  build stress-ng 0.45%
  tar up kernel source: 7.6%
  boot time of eoan cloud image: 10.5%

  So I think the speed improvements justify the SRU.

  == Regression potential ==

  minor change to ext4, which has been regression tested, so risk here
  is small.  The entropy change will alter the random number generation,
  but I believe this does not change the cryptographical security of the
  random numbers being generated, so think this change is not security
  risk.

  originally the ext4 change caused boot time user space regressions
  because of the entropy change of this fix, but the random fix
  addresses this, so I believe this risk is now zero.

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

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

[Kernel-packages] [Bug 1845584] Re: intel-lpss driver conflicts with write-combining MTRR region

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  intel-lpss driver conflicts with write-combining MTRR region

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem source package in Eoan:
  Invalid
Status in linux source package in FF-Series:
  In Progress
Status in linux-oem source package in FF-Series:
  Invalid

Bug description:
  [Impact]
  The memory region intel-lpss-pci uses has been declared as
  write-combining
  [0.001728]   5 base 40 mask 60 write-combining
  This leads to the system hangs up during booting up.

  This is a BIOS issue, but there are some platforms on the market and
  users are struggling on booting up the machines. So, we may have to
  fix this in the kernel.

  [Fix]
  Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss
  driver to claim to use un-catchable memory while calling
  __devm_ioremap(), and it works well. But it didn't be accepted by 
  maintainer yet.

  To avoid the potential impact on other machines, I add a quirk to list
  the machines which has the write-combining area in MTRR which overlaps
  with the address that intel-lpss uses, only the machines in the list
  pass the DEVM_IOREMAP_UC to __devm_ioremap().

  [Test]
  Verified on Dell XPS 13 7390 2-in-1

  [Regression Potential]
  Low, without this patch, the machine even can't boot. And the quirk only for 
specific machines, so the modification won't affect other machines.

  1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23

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

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

[Kernel-packages] [Bug 1847063] Re: Fix non-working Realtek USB ethernet after system resume

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: Incomplete => Fix Committed

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

Title:
  Fix non-working Realtek USB ethernet after system resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work
  under the following steps:
  1. Connect to a Dell dock
  2. Suspend the system
  3. Re-plug the dock 
  4. Resume the system
  5. Ethernet stops working

  [Fix]
  The USB port lose its power when the dock gets replugged, so we need to
  re-write the MAC address at reset_resume callback.

  [Test]
  The fix is succesfully tested on Dell WD15 dock and TB16 dock.

  [Regression Potential]
  Low. The fix limits to one single device and only take affect when MAC
  passthrough is enabled.

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

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

[Kernel-packages] [Bug 1847063] Re: Fix non-working Realtek USB ethernet after system resume

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

Title:
  Fix non-working Realtek USB ethernet after system resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Incomplete
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work
  under the following steps:
  1. Connect to a Dell dock
  2. Suspend the system
  3. Re-plug the dock 
  4. Resume the system
  5. Ethernet stops working

  [Fix]
  The USB port lose its power when the dock gets replugged, so we need to
  re-write the MAC address at reset_resume callback.

  [Test]
  The fix is succesfully tested on Dell WD15 dock and TB16 dock.

  [Regression Potential]
  Low. The fix limits to one single device and only take affect when MAC
  passthrough is enabled.

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

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

[Kernel-packages] [Bug 1847109] Re: Ubuntu 18.04 - wrong cpu-mf counter number

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu 18.04  - wrong cpu-mf counter number

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * wrong cpu-mf counter number of LAST_HOST_TRANSLATIONS

  [Fix]

  * 81507f38d427ebed3291a3c153a798937c998140 81507f38 "s390/cpum_cf:
  correct counter number of LAST_HOST_TRANSLATIONS"

  [Test Case]

  * inspect the counter number of the LAST_HOST_TRANSLATIONS (virtual)
  file

  * cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS

  * returns 'event=0x00e9', but should be 'event=0x00e8'

  * event is only available on z14 and higher, hence Canonical can only
  do regression testing - IBM the functional verification

  [Regression Potential]

  * very minimal, patch just changes one hex number in one code line

  * change is limited to z14 (and higher) hardware counters only

  [Other Info]

  * fix/patch got upstream accepted with 4.16

  * hence it's already in (cosmic and) disco and eoan and only need to be 
applied to bionic 4.15
  __

  Kernel:
  Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

  Description/Reproduction:
  The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

  # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
  event=0x00e9

  should be event=0x00e8

  Fix already available:
  commit 81507f38d427ebed3291a3c153a798937c998140

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

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

[Kernel-packages] [Bug 1846272] Re: overlayfs: allow with shiftfs as underlay

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  overlayfs: allow with shiftfs as underlay

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Currently it is not possible to use overlayfs on top of
  shiftfs. This means Docker inside of LXD cannot make user of the
  overlay2 graph driver which is blocking users such as Travis from
  making use of it efficiently.

  Regression Potential: Limited to shiftfs and overlayfs on top of
  shiftfs. Overlayfs does prevent "remote" filesystems such as ceph,
  nfs, etc. from being used as the underlay. With this patch shiftfs
  however can be used as an underlay and we special case it as a
  suitable filesystem to be used under overlayfs. I verified that the
  patch does not lead to regression on overlayfs workloads that do not
  make use of shiftfs as underlay. Additionally, I tested Docker with
  the overlay2 graphdriver on top of shiftfs. This also has not lead to
  any regressions.

  Test case: Building a kernel with the patch:
  sudo snap install lxd
  sudo lxd init
  sudo lxc launch images:ubuntu/bionic b1
  sudo lxc config set b1 security.nesting true
  sudo lxc restart --force b1
  sudo lxc shell b1
  sudo apt-get install \
  apt-transport-https \
  ca-certificates \
  curl \
  gnupg-agent \
  software-properties-common

  curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
  curl -fsSL get.docker.com | CHANNEL=test sh

  sudo add-apt-repository \
 "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
 $(lsb_release -cs) \
 stable"

  sudo apt-get update

  sudo apt-get install docker-ce docker-ce-cli containerd.io

  sudo systemctl stop docker

  cat 

[Kernel-packages] [Bug 1847109] Re: Ubuntu 18.04 - wrong cpu-mf counter number

[Kleber Sacilotto de Souza]

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

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

Title:
  Ubuntu 18.04  - wrong cpu-mf counter number

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * wrong cpu-mf counter number of LAST_HOST_TRANSLATIONS

  [Fix]

  * 81507f38d427ebed3291a3c153a798937c998140 81507f38 "s390/cpum_cf:
  correct counter number of LAST_HOST_TRANSLATIONS"

  [Test Case]

  * inspect the counter number of the LAST_HOST_TRANSLATIONS (virtual)
  file

  * cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS

  * returns 'event=0x00e9', but should be 'event=0x00e8'

  * event is only available on z14 and higher, hence Canonical can only
  do regression testing - IBM the functional verification

  [Regression Potential]

  * very minimal, patch just changes one hex number in one code line

  * change is limited to z14 (and higher) hardware counters only

  [Other Info]

  * fix/patch got upstream accepted with 4.16

  * hence it's already in (cosmic and) disco and eoan and only need to be 
applied to bionic 4.15
  __

  Kernel:
  Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 
s390x s390x s390x GNU/Linux

  Description/Reproduction:
  The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number.

  # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS
  event=0x00e9

  should be event=0x00e8

  Fix already available:
  commit 81507f38d427ebed3291a3c153a798937c998140

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

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

[Kernel-packages] [Bug 1847478] Re: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule"

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Eoan)
   Importance: High
 Assignee: Tyler Hicks (tyhicks)
   Status: In Progress

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF
  is set on suppress rule"

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  An unprivileged local attacker could cause a denial of service, or
  possibly execute arbitrary code due to an ipv6 regression.

  [Test Case]

  An unpatched system will crash with the following command:

  $ unshare -rUn sh -c 'ip link add dummy1 type dummy && ip link set
  dummy1 up && ip -6 route add default dev dummy1 && ip -6 rule add
  table main suppress_prefixlength 0 && ping -f 1234::1'

  [Regression Potential]

  Low. The change could theoretically introduce a memory leak but that
  would still be an improvement over immediate loss of system
  availability.

  [Original Description]

  Having recently upgraded to Eoan Ermine from Disco Dingo, my
  previously rock-solid wireguard now locks the system up shortly after
  I take the connection down with wg-quick down wg0.

  Package:

  wireguard:
    Installed: 0.0.20190913-1ubuntu1
    Candidate: 0.0.20190913-1ubuntu1
    Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  Kernel:
  5.3.0-13-generic

  Snipped from /var/log/syslog:

  kernel: [  776.930804] BUG: unable to handle page fault for address: 
1070
  kernel: [  776.930807] #PF: supervisor read access in kernel mode
  kernel: [  776.930808] #PF: error_code(0x) - not-present page
  kernel: [  776.930809] PGD 0 P4D 0
  kernel: [  776.930811] Oops:  [#1] SMP NOPTI
  kernel: [  776.930813] CPU: 3 PID: 2598 Comm: Chrome_ChildIOT Tainted: G  
 OE 5.3.0-13-generic #14-Ubuntu
  kernel: [  776.930813] Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 
1.7.0 08/05/2019
  kernel: [  776.930817] RIP: 0010:ip6_sk_dst_store_flow+0x80/0xc0
  kernel: [  776.930819] Code: 48 8b 42 30 48 33 47 40 48 09 c1 0f b6 4f 12 b8 
01 00 00 00 4d 0f 45 e9 31 db d3 e0 a9 bf ef ff ff 74 07 48 8b 9f f8 02 00 00 
<48> 8b 46 70 31 d2 48 85 c0 74 0c 48 8b 40 10 48 85 c0 74 03 8b 50
  kernel: [  776.930820] RSP: 0018:beb841a9fcd8 EFLAGS: 00010202
  kernel: [  776.930821] RAX: 0080 RBX: a0933c829360 RCX: 
0007
  kernel: [  776.930822] RDX: beb841a9fd20 RSI: 1000 RDI: 
a0933c828f00
  kernel: [  776.930823] RBP: beb841a9fcf0 R08:  R09: 

  kernel: [  776.930823] R10:  R11: a093948fd800 R12: 
a0933c829360
  kernel: [  776.930824] R13: a0933c828f38 R14: 0001 R15: 
a0933c829360
  kernel: [  776.930825] FS:  7fbcd8a82700() GS:a0939e4c() 
knlGS:
  kernel: [  776.930826] CS:  0010 DS:  ES:  CR0: 80050033
  kernel: [  776.930827] CR2: 1070 CR3: 00049172a004 CR4: 
003606e0
  kernel: [  776.930828] Call Trace:
  kernel: [  776.930832]  ip6_datagram_dst_update+0x15e/0x280
  kernel: [  776.930835]  ? _raw_read_unlock_bh+0x20/0x30
  kernel: [  776.930837]  __ip6_datagram_connect+0x1da/0x380
  kernel: [  776.930839]  ip6_datagram_connect+0x2d/0x50
  kernel: [  776.930841]  inet_dgram_connect+0x3f/0xc0
  kernel: [  776.930843]  __sys_connect+0xf1/0x130
  kernel: [  776.930846]  ? do_fcntl+0xe4/0x550
  kernel: [  776.930848]  ? fput+0x13/0x15
  kernel: [  776.930849]  __x64_sys_connect+0x1a/0x20
  kernel: [  776.930852]  do_syscall_64+0x5a/0x130
  kernel: [  776.930854]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  kernel: [  776.930855] RIP: 0033:0x7fbcde6324eb
  kernel: [  776.930856] Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 
ab fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 
<48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 fa ff ff 8b 44
  kernel: [  776.930857] RSP: 002b:7fbcd8a7ec90 EFLAGS: 0293 ORIG_RAX: 
002a
  kernel: [  776.930859] RAX: ffda RBX: ff94 RCX: 
7fbcde6324eb
  kernel: [  776.930859] RDX: 001c RSI: 7fbcd8a7ecf0 RDI: 
0022
  kernel: [  776.930860] RBP: 7fbcd8a7edb0 R08:  R09: 
7fbcd8a7edf8
  kernel: [  776.930861] R10: 7fbcd8a7edf0 R11: 0293 R12: 
250e77c19710
  kernel: [  776.930862] R13: 250e77c19900 R14: 7fbcd8a7edc8 R15: 
7fbcd8a7edc8
  kernel: [  776.930863] Modules linked in: binfmt_misc wireguard(OE) 
ip6_udp_tunnel 

[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Fix Committed

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

Title:
  [regression] NoNewPrivileges incompatible with Apparmor

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  Description:

  Host: Bionic 64 bit with GA kernel (4.15)
  Container: Bionic 64 bit

  The container runs a binary (/usr/sbin/nsd) locked by an Apparmor
  profile. The systemd service is configured with NoNewPrivileges=yes.

    # systemctl show nsd | grep ^NoNew
    NoNewPrivileges=yes

  This setup worked fine with 4.15.0-58-generic and before but stopped
  working with the 4.15.0-60-generic update. When running the bogus
  kernel, starting the nsd service fails and the following is logged in
  the host's dmesg:

  audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" 
info="no new privs" error=-1 profile="lxd-ns0_" 
name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" 
fsuid=1065536 ouid=1065536 
target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd"
  audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" 
info="no new privs" error=-1 
namespace="root//lxd-ns0_" profile="unconfined" 
name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" 
fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd"

  Disabling the Apparmor profile OR setting NoNewPrivileges=no in the
  container makes it work again.

  I check with a couple of kernels:

  4.15.0-52-generic works
  4.15.0-58-generic works
  4.15.0-60-generic is broken

  The 5.0 HWE kernel has always been broken it seems:

  5.0.0-15-generic is broken
  5.0.0-17-generic is broken
  5.0.0-20-generic is broken
  5.0.0-23-generic is broken
  5.0.0-25-generic is broken
  5.0.0-27-generic is broken

  I have another similar setup but using Xenial host/container and it
  broke in a similar fashion where 4.4.0-159-generic works but
  4.4.0-161-generic is broken.

  Additional information:

  # lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  # apt-cache policy nsd
  nsd:
    Installed: 4.1.26-1ubuntu0.18.04.1~ppa2
    Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2
    Version table:
   *** 4.1.26-1ubuntu0.18.04.1~ppa2 500
  500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status
   4.1.17-1build1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  nsd comes from a custom backport this should be irrelevant.
  nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-60-generic 4.15.0-60.67
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 16 18:02 seq
   crw-rw 1 root audio 116, 33 Sep 16 18:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  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:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Sep 16 18:14:02 2019
  InstallationDate: Installed on 2019-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. Inspiron 530s
  PciMultimedia:

  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic 
root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false 
apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-27-generic N/A
   linux-backports-modules-5.0.0-27-generic  N/A
   linux-firmware1.173.9
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.18
  dmi.board.name: 0RY007
  dmi.board.vendor: 

[Kernel-packages] [Bug 1829942] Re: Address performance issue w/ GICv4-based guests

[Kleber Sacilotto de Souza]

This fix has already been released with disco linux 5.0.0-21.22, as part
of the update to 5.0.12 upstream stable release (LP: #1830934).
Therefore I'm marking it as 'Fix Released'.

** Changed in: linux (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  Address performance issue w/ GICv4-based guests

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

Bug description:
  [Impact]
  Performance is degraded when a guest is booted w/ vgic v4 support enabled. 

  [Test Case]
  I used a HiSilicon D06 system w/ an Intel 82599 10Gbps NIC. I passed through 
a VF to a guest, and ran "netperf -H " against a 10Gbps-capable target. 
With vgic v4 support, I'm only seeing 5-6Gbps. With vgic v3 support, this was 
in the 9Gbps spectrum. And, after applying the upstream fix, I'm also seeing 
>9Gbps w/ vgic v4 enabled.

  Note: to enable vgic v4 support, pass "kvm-arm.vgic_v4_enable=1" on
  the host kernel cmdline.

  [Fix]
  ca71228b42a96 arm64: KVM: Always set ICH_HCR_EL2.EN if GICv4 is enabled

  [Regression Risk]
  The fix is restricted to the ARM/KVM subsystem.

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

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

[Kernel-packages] [Bug 1847628] Re: When using swap in ZFS, system stops when you start using swap

[Brian Murray]

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

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

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

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

Title:
  When using swap in ZFS, system stops when you start using swap

Status in Release Notes for Ubuntu:
  Fix Released
Status in Native ZFS for Linux:
  Unknown
Status in ubiquity package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  # Problem

  When using swap in ZFS, system stops when you start using swap.

  > stress --vm 100

  if you doing swapoff will only occur OOM and the system will not stop.

  # Environment

  jehos@MacBuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10
  Codename:   eoan

  jehos@MacBuntu:~$ dpkg -l | grep zfs
  ii  libzfs2linux   0.8.1-1ubuntu13
 amd64OpenZFS filesystem library for Linux
  ii  zfs-initramfs  0.8.1-1ubuntu13
 amd64OpenZFS root filesystem capabilities for Linux - initramfs
  ii  zfs-zed0.8.1-1ubuntu13
 amd64OpenZFS Event Daemon
  ii  zfsutils-linux 0.8.1-1ubuntu13
 amd64command-line tools to manage OpenZFS filesystems

  jehos@MacBuntu:~$ uname -a
  Linux MacBuntu 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  jehos@MacBuntu:~$ zpool list
  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
  bpool  1.88G  66.1M  1.81G- -  - 3%  1.00xONLINE  
-
  rpool   230G   124G   106G- - 9%53%  1.00xONLINE  
-

  jehos@MacBuntu:~$ zfs get all rpool/swap
  NAMEPROPERTY  VALUESOURCE
  rpool/swap  type  volume   -
  rpool/swap  creation  목 10월 10 15:56 2019  -
  rpool/swap  used  2.13G-
  rpool/swap  available 98.9G-
  rpool/swap  referenced72K  -
  rpool/swap  compressratio 1.11x-
  rpool/swap  reservation   none default
  rpool/swap  volsize   2G   local
  rpool/swap  volblocksize  4K   -
  rpool/swap  checksum  on   default
  rpool/swap  compression   zle  local
  rpool/swap  readonly  off  default
  rpool/swap  createtxg 34   -
  rpool/swap  copies1default
  rpool/swap  refreservation2.13Glocal
  rpool/swap  guid  18209330213704683244 -
  rpool/swap  primarycache  metadata local
  rpool/swap  secondarycachenone local
  rpool/swap  usedbysnapshots   0B   -
  rpool/swap  usedbydataset 72K  -
  rpool/swap  usedbychildren0B   -
  rpool/swap  usedbyrefreservation  2.13G-
  rpool/swap  logbias   throughput   local
  rpool/swap  objsetid  393  -
  rpool/swap  dedup off  default
  rpool/swap  mlslabel  none default
  rpool/swap  sync  always   local
  rpool/swap  refcompressratio  1.11x-
  rpool/swap  written   72K  -
  rpool/swap  logicalused   40K  -
  rpool/swap  logicalreferenced 40K  -
  rpool/swap  volmode   default  default
  rpool/swap  snapshot_limitnone default
  rpool/swap  snapshot_countnone default
  rpool/swap  snapdev   hidden   default
  rpool/swap  context   none default
  rpool/swap  fscontext none default
  rpool/swap  defcontextnone default
  rpool/swap  rootcontext   none default
  rpool/swap  redundant_metadataall  default
  rpool/swap  encryptionoff  default
  rpool/swap  keylocation   none default
  rpool/swap  keyformat 

[Kernel-packages] [Bug 1847189] Re: Bad posix clock speculation mitigation backport

[Kleber Sacilotto de Souza]

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

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

Title:
  Bad posix clock speculation mitigation backport

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

Bug description:
  [Impact]

  Vitaly Nikolenko pointed out that syscall(__NR_clock_gettime, 10, 0)
  can be used to perform a denial of service (system crash) or possibly
  execute arbitrary code in the Ubuntu Xenial kernel:

https://twitter.com/vnik5287/status/1180666151216435200

  [Test Case]

  Execute the following test program and verify that it prints out
  "clock_gettime: Invalid argument" rather than triggering a NULL
  pointer dereference and stack trace in the kernel logs.

  ==
  #include 
  #include 

  int main(void)
  {
  int rc = clock_gettime(10, 0);

  if (rc < 0)
  perror("clock_gettime");

  return rc;
  }
  ==

  [Regression Potential]

  Low. The fix is easy to review and fixes a denial of service issue
  that's trivial to trigger.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1846978

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

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

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

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

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

Title:
  wifi bug oscillating

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the 2.4ghz band wifi network does not work properly and the other
  networks is oscillating is not stable, is oscillating and dropping the
  network all the time using this system, I've done testing on other
  systems like windows and works normally, an information about my
  machine and a hp pavilion dv4 notebook

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.13
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun Oct  6 17:10:07 2019
  InstallationDate: Installed on 2019-10-02 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Lenovo ThinkPad e580 touchpad and trackpoint stopped working lately

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The device isn't listed in xinput nor devices list from
  /proc/bus/input/devices. External mouse works as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spurlos3258 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 15:50:52 2019
  InstallationDate: Installed on 2018-09-20 (390 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KS001QRT
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=a98572ba-317f-4569-b9cf-49ae45dd9308 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-19 (180 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KS001QRT
  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:bvrR0PET42W(1.19):bd06/14/2018:svnLENOVO:pn20KS001QRT:pvrThinkPadE580:rvnLENOVO:rn20KS001QRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E580
  dmi.product.name: 20KS001QRT
  dmi.product.sku: LENOVO_MT_20KS_BU_Think_FM_ThinkPad E580
  dmi.product.version: ThinkPad E580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1847118] Re: PM / hibernate: fix potential memory corruption

[Kleber Sacilotto de Souza]

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

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

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  PM / hibernate: fix potential memory corruption

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  A caching bug in the hibernation code can lead to potential memory
  corruptions on resume.

  The hibernation code is representing all the allocated pages in memory
  (pfn) using a list of extents, inside each extent it uses a radix tree
  and each node in the tree contains a bitmap. This structure is used to
  save the memory image to disk.

  To speed up lookups in this structure the kernel is caching the
  position of the previous lookup in the form (current_extent,
  current_node). However, if two consecutive lookups are distant enough
  from each other, the extent can change, but the kernel can still use
  the cached node (current_node), accessing the wrong bitmap and ending
  up saving to disk the wrong pfn's.

  [Test Case]

  Bug has been reproduced in Xenial and Bionic trying to hibernate a
  large instance with a lot of RAM (100GB+).

  But we also wrote a custom kernel module to better isolate the code
  that triggers the problem:
  https://code.launchpad.net/~arighi/+git/mybitmap

  This module has exactly the same code as the hibernation code, but it
  can be used as a fast test case to reproduce the problem without
  actually triggering a real hibernation/resume cycle.

  [Fix]

  This bug can be fixed by properly invalidating the cached pair
  (extent, node) when the next lookup falls in a different extent or a
  different node.

  [Regression Potential]

  The fix has been sent to the LKML for review/feedback
  (https://lkml.org/lkml/2019/9/25/393), we have not received any
  feedback so far, but the bug is pretty clear and well tested on the
  affected platforms. Moreover, the code is isolated to the hibernation
  area, so the overall regression potential is minimal.

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

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

[Kernel-packages] [Bug 1846978] Re: wifi bug oscillating

[Sebastien Bacher]

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  wifi bug oscillating

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  the 2.4ghz band wifi network does not work properly and the other
  networks is oscillating is not stable, is oscillating and dropping the
  network all the time using this system, I've done testing on other
  systems like windows and works normally, an information about my
  machine and a hp pavilion dv4 notebook

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.13
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun Oct  6 17:10:07 2019
  InstallationDate: Installed on 2019-10-02 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1827314] Re: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup

[Pehkawn]

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

I experience the same issue. After suspend the lock screen and
background image is gone, leaving only a "white noise" (see attached
image). From what I can tell, this bug is purely aesthetical, and has no
practical implications. I can still log in and use my computer like
nothing happened.

I am far from any expert, but the description of [bug
#1809407](https://bugs.launchpad.net/bugs/1809407) does not sound
entirely similar to what I experience and what OP describes, and the bug
might not be a duplicate.

** Attachment added: "White noise background and lock screen."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827314/+attachment/5297501/+files/Skjermbilde%20fra%202019-10-16%2015-16-38.png

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

Title:
  Ubuntu 19.04 Background and lockscreen image turns into white noise
  after sleep and wakeup

Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 Background and lockscreen image turns into white noise after 
sleep and wakeup
  the lock screen is Disco Dingo default image and bg is custom but both turn 
into a noisy broken image
  my laptop is MSI CX627QL
  Core i5 7th gen
  Ram 12 gb

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

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

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

[bugproxy]

--- Comment From mu...@br.ibm.com 2019-10-16 09:05 EDT---
Using the 2.11+dfsg-1ubuntu7.20~ppa2 build the performance is still the same 
and no functional issues were seen, here are the numbers for numjobs=4 and 
numjobs=64 cases, respectively:

READ: bw=1155MiB/s (1211MB/s), 285MiB/s-295MiB/s (299MB/s-309MB/s),
io=67.7GiB (72.7GB), run=60001-60001msec

READ: bw=4273MiB/s (4481MB/s), 42.7MiB/s-106MiB/s (44.7MB/s-111MB/s),
io=250GiB (269GB), run=60001-60005msec

# dpkg -l | grep ppa2
ii  qemu   
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  fast processor emulator
ii  qemu-block-extra:ppc64el   
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  extra block backend modules 
for qemu-system and qemu-utils
ii  qemu-kvm   
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU Full virtualization on 
x86 hardware
ii  qemu-system
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries
ii  qemu-system-arm
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (arm)
ii  qemu-system-common 
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (common files)
ii  qemu-system-mips   
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (mips)
ii  qemu-system-misc   
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (miscellaneous)
ii  qemu-system-ppc
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (ppc)
ii  qemu-system-s390x  
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (s390x)
ii  qemu-system-sparc  
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (sparc)
ii  qemu-system-x86
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU full system emulation 
binaries (x86)
ii  qemu-user  
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU user mode emulation 
binaries
ii  qemu-user-binfmt   
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU user mode binfmt 
registration for qemu-user
ii  qemu-utils 
1:2.11+dfsg-1ubuntu7.20~ppa2   ppc64el  QEMU utilities

As an important note, this respin version was only tested with the newer
custom kernel mentioned in the previous comment. Christian, let me know
if you need this tested with the vanillla kernel 4.15.0-65.74 as well.

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

Title:
  Improve NVMe guest performance on Bionic QEMU

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in qemu source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO.
 But there can be platforms (like ppc64 spapr) that can and want to do 
 exactly that.

   * Backport two patches from upstream (in since qemu 2.12 / Disco).

   * Due to that there is a tremendous speedup, especially useful with page 
 size bigger than 4k. This avoids that being split into chunks and makes 
 direct MMIO access possible for the guest.

  [Test Case]

   * On ppc64 pass through an NVME device to the guest and run I/O 
 benchmarks, see below for Details how to set that up.
 Note this needs the HWE kernel or another kernel fixup for [1].

  [Regression Potential]

   * Changes:
 a) if the host driver allows mapping of MSI-X data the entire BAR is 
mapped. This is only done if the kernel reports that capability [1].
This ensures that only on kernels able to do so qemu does expose the 
new behavior (safe against regression in that regard)
 b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local 
to just this HW and will not affect other HW.

 Generally the regressions that come to mind are slight changes in 
 behavior (real HW vs the former emulation) that on some weird/old 
 guests could cause trouble. But then it is limited to only PPC where 
 only a small set of certified HW is really allowed.

 The mapping that might be added even on other platforms should not 
 consume too much extra memory as long as it isn't used. 

[Kernel-packages] [Bug 1848173] Re: Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not established by zcrypt device driver

[Frank Heimes]

Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2019-October/thread.html#104727
Changing status to In Progress.

** Description changed:

+ SRU Justification:
+ ==
+ 
+ [Impact]
+ 
+ * Ubuntu 16.04.6 systems on z15 with crypto CEX7C adapters under z/VM
+ cannot see and make use of their hw crypto resources.
+ 
+ * The patch/backport adds CEX7 toleration support (by mapping it to
+ CEX5) to kernel 4.4.
+ 
+ [Fix]
+ 
+ * Backport:
+ 
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848173/+attachment/5297314/+files/s390
+ -zcrypt-CEX7-toleration-support.patch
+ 
+ [Test Case]
+ 
+ * Define a z/VM guest with 'apvirt' (hardware crypto adapter
+ virtualization) having CryptoExpress 7S adapters attached to z/VM LPAR.
+ 
+ * Use lszcrypt command (ideally lszcrypt -VVV) from the s390-tools
+ package to list the detected and available hardware crypto resources.
+ 
+ * Canonical can only do a toleration test: IBM needs to do the
+ functional test (due to hardware availability).
+ 
+ [Regression Potential]
+ 
+ * The regression potential can be considered as moderate since this is
+ purely s390x specific
+ 
+ * and limited to CryptoExpress 7S (CEX7) adapter cards
+ 
+ * and again if they running under z/VM (on z15) with 'apvirt' configured
+ for the guest.
+ 
+ * and again only with 16.04.6's kernel 4.4.
+ 
+ [Other Info]
+ 
+ * The patch was already applied, kernel compiled and things tested on
+ z15 und z/VM.
+ 
+ __
+ 
  System: IBM Z15 z/VM with shared CEX7C adapters
  OS:  Ubuntu 16.04.6 LTS ( 4.4.0-165-generic kernel ) with latest updates
  Shared CEX7C adapters are not displayed on Ubuntu even though APAR 66266 had 
been installed onto the unterlying z/VM system.
- 
  
  Details
  ===
  Defined shared CEX7C CCA adapters to provide cryptographic accelerators based 
on CCA cards to a z/VM guest system running Ubuntu 16.04.6 LTS.
  
  The adapters display all right under vm or when running vmcp commands
  under Linux.
  
  lszcrypt -VVV does not display any adapter.
  
  We observed that zcrypt_cex4 was not automatically loaded via dependency
  by modprobe ap. Explicitly loading by modprobe zcrypt_cex4 did not
  change card availability.
  
  Please investigate.
  
  Thanks.
- 
  
  Terminal output
  ==
  root@system:/sys/bus/ap/devices/card01# ls -l
  total 0
  -r--r--r-- 1 root root 4096 Oct  8 17:51 ap_functions
  -r--r--r-- 1 root root 4096 Oct  8 17:51 depth
  -r--r--r-- 1 root root 4096 Oct  8 17:51 hwtype
  -r--r--r-- 1 root root 4096 Oct  8 17:51 interrupt
  -r--r--r-- 1 root root 4096 Oct  8 17:51 modalias
  -r--r--r-- 1 root root 4096 Oct  8 17:51 pendingq_count
  drwxr-xr-x 2 root root0 Oct  8 17:51 power
  -r--r--r-- 1 root root 4096 Oct  8 17:51 raw_hwtype
  -r--r--r-- 1 root root 4096 Oct  8 17:51 request_count
  -r--r--r-- 1 root root 4096 Oct  8 17:51 requestq_count
  -r--r--r-- 1 root root 4096 Oct  8 17:51 reset
  lrwxrwxrwx 1 root root0 Oct  8 17:51 subsystem -> ../../../bus/ap
  -rw-r--r-- 1 root root 4096 Oct  8 17:50 uevent
  
  # lszcrypt -V// < No output displayed >
  # vmcp q v crypto
  AP 001 CEX7C Domain 001 shared online
  
  root@system:/sys/bus/ap/devices/card01# cat hwtype
  13
  root@system:/sys/bus/ap/devices/card01# cat raw_hwtype
  13
  
  # lsmod
  Module  Size  Used by
  ap 36864  0
  ghash_s390 16384  0
  prng   16384  0
  aes_s390   20480  0
  des_s390   16384  0
  des_generic28672  1 des_s390
  sha512_s39016384  0
  qeth_l253248  1
  sha256_s39016384  0
  sha1_s390  16384  0
  sha_common 16384  3 sha256_s390,sha1_s390,sha512_s390
  qeth  151552  1 qeth_l2
  vmur   20480  0
  ccwgroup   20480  1 qeth
  dm_multipath   36864  0
  zfcp  143360  0
  dasd_eckd_mod 118784  8
  qdio   73728  3 qeth,zfcp,qeth_l2
  scsi_transport_fc  86016  1 zfcp
  dasd_mod  135168  5 dasd_eckd_mod
  
  # modprobe zcrypt_cex4
  ...
  zcrypt_cex416384  0
  zcrypt_api 36864  1 zcrypt_cex4
  ap 36864  2 zcrypt_cex4,zcrypt_api
  ...
  
-  
- Contact Information = christian.r...@de.ibm.com 
-  
+ Contact Information = christian.r...@de.ibm.com
+ 
  ---uname output---
  Linux system 4.4.0-164-generic #192-Ubuntu SMP Fri Sep 13 12:01:28 UTC 2019 
s390x s390x s390x GNU/Linux
-  
- Machine Type = IBM Type: 8561 Model:403   
   T01 
-  
+ 
+ Machine Type = IBM Type: 8561 Model:403
+ T01
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  1.) Define shared CEX7 CCA cards to z/VM Guest 
- 2.) boot up Ubuntu 16.04.6 LTS 
+  1.) Define shared CEX7 CCA cards to z/VM Guest
+ 2.) boot up Ubuntu 16.04.6 

[Kernel-packages] [Bug 1846978] [NEW] wifi bug oscillating

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

the 2.4ghz band wifi network does not work properly and the other
networks is oscillating is not stable, is oscillating and dropping the
network all the time using this system, I've done testing on other
systems like windows and works normally, an information about my machine
and a hp pavilion dv4 notebook

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.13
ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
Uname: Linux 5.3.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
Date: Sun Oct  6 17:10:07 2019
InstallationDate: Installed on 2019-10-02 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade eoan
-- 
wifi bug oscillating
https://bugs.launchpad.net/bugs/1846978
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1847118] Re: PM / hibernate: fix potential memory corruption

[Kleber Sacilotto de Souza]

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Andrea Righi (arighi)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Andrea Righi (arighi)

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Andrea Righi (arighi)

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

Title:
  PM / hibernate: fix potential memory corruption

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]

  A caching bug in the hibernation code can lead to potential memory
  corruptions on resume.

  The hibernation code is representing all the allocated pages in memory
  (pfn) using a list of extents, inside each extent it uses a radix tree
  and each node in the tree contains a bitmap. This structure is used to
  save the memory image to disk.

  To speed up lookups in this structure the kernel is caching the
  position of the previous lookup in the form (current_extent,
  current_node). However, if two consecutive lookups are distant enough
  from each other, the extent can change, but the kernel can still use
  the cached node (current_node), accessing the wrong bitmap and ending
  up saving to disk the wrong pfn's.

  [Test Case]

  Bug has been reproduced in Xenial and Bionic trying to hibernate a
  large instance with a lot of RAM (100GB+).

  But we also wrote a custom kernel module to better isolate the code
  that triggers the problem:
  https://code.launchpad.net/~arighi/+git/mybitmap

  This module has exactly the same code as the hibernation code, but it
  can be used as a fast test case to reproduce the problem without
  actually triggering a real hibernation/resume cycle.

  [Fix]

  This bug can be fixed by properly invalidating the cached pair
  (extent, node) when the next lookup falls in a different extent or a
  different node.

  [Regression Potential]

  The fix has been sent to the LKML for review/feedback
  (https://lkml.org/lkml/2019/9/25/393), we have not received any
  feedback so far, but the bug is pretty clear and well tested on the
  affected platforms. Moreover, the code is isolated to the hibernation
  area, so the overall regression potential is minimal.

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

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

[Kernel-packages] [Bug 1848340] [NEW] Lenovo ThinkPad e580 touchpad and trackpoint stopped working lately

[Vladislav Shumkin]

Public bug reported:

The device isn't listed in xinput nor devices list from
/proc/bus/input/devices. External mouse works as intended.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-32-generic 5.0.0-32.34
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  spurlos3258 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Oct 16 15:50:52 2019
InstallationDate: Installed on 2018-09-20 (390 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20KS001QRT
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=a98572ba-317f-4569-b9cf-49ae45dd9308 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-32-generic N/A
 linux-backports-modules-5.0.0-32-generic  N/A
 linux-firmware1.178.3
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-19 (180 days ago)
dmi.bios.date: 06/14/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0PET42W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KS001QRT
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:bvrR0PET42W(1.19):bd06/14/2018:svnLENOVO:pn20KS001QRT:pvrThinkPadE580:rvnLENOVO:rn20KS001QRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E580
dmi.product.name: 20KS001QRT
dmi.product.sku: LENOVO_MT_20KS_BU_Think_FM_ThinkPad E580
dmi.product.version: ThinkPad E580
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco third-party-packages

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1848340/+attachment/5297484/+files/devices

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

Title:
  Lenovo ThinkPad e580 touchpad and trackpoint stopped working lately

Status in linux package in Ubuntu:
  New

Bug description:
  The device isn't listed in xinput nor devices list from
  /proc/bus/input/devices. External mouse works as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spurlos3258 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 15:50:52 2019
  InstallationDate: Installed on 2018-09-20 (390 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KS001QRT
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=a98572ba-317f-4569-b9cf-49ae45dd9308 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-19 (180 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KS001QRT
  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:bvrR0PET42W(1.19):bd06/14/2018:svnLENOVO:pn20KS001QRT:pvrThinkPadE580:rvnLENOVO:rn20KS001QRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E580
  dmi.product.name: 20KS001QRT
  dmi.product.sku: LENOVO_MT_20KS_BU_Think_FM_ThinkPad E580
  dmi.product.version: ThinkPad E580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1846453] Re: Microphone-Mute keyboard LED is always on/off on Dell Latitude 3310

[Kleber Sacilotto de Souza]

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

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

Title:
  Microphone-Mute keyboard LED is always on/off on Dell Latitude 3310

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

Bug description:
  [SRU Justification]

  [Impact]
  Micphone-mute LED indicator on Dell Latitude 3310 keyboard may always
  shown as on or off.

  [Fix]
  * fe486138788ba4 [1]: dell-laptop: Add 2-in-1 devices to the DMI whitelist
  * c8ba9db2a790c0 [2]: dell-laptop: Removed duplicates in DMI whitelist

  [Test Case]
  Verified on Dell Latitude 3310.

  [Regression Risk]
  Low. The two target patch was landed to v4.16 and is already in
  production use for a long time. Besides, this changeset only addes new
  IDs (and remove duplicated ones), so it doesn't affect existing systems
  but fix those affected ones.

  ＝ Original Description ＝

  This device has unsupported DMI Chassis Type:

    $ sudo dmidecode | grep -A2 -B1 ^Chassis
    Handle 0x0003, DMI type 3, 22 bytes
    Chassis Information
    Manufacturer: Dell Inc.
    Type: Convertible

  So we need to SRU:
  * fe486138788ba4 [1]: dell-laptop: Add 2-in-1 devices to the DMI whitelist
  * c8ba9db2a790c0 [2]: dell-laptop: Removed duplicates in DMI whitelist

  This should only affect 4.15 kernel as they have been landed to v4.16.

  system-manufacturer: Dell Inc.
  system-product-name: Latitude 3310
  bios-version: 0.1.9
  CPU: Intel(R) Pentium(R) CPU 5405U @ 2.30GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3ea1] (rev 02)
  kernel-version: 4.15.0-1047-oem

  [1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe486138788ba435ffa918c8d7aba05a77b6289a
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c8ba9db2a790c0fcf2f6c4cafd45ff3a0751800e

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

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

[Kernel-packages] [Bug 1846470] Re: xHCI on AMD Stoney Ridge cannot detect USB 2.0 or 1.1 devices.

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => Fix Committed

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

Title:
  xHCI on AMD Stoney Ridge cannot detect USB 2.0 or 1.1 devices.

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  xHCI on AMD Stoney Ridge cannot detect USB 2.0 or 1.1 devices. 

  [Fix]
  The xHCI in question doesn't have proper support for D0 PME, so strip it from 
PM capability.

  [Test]
  The xHCI can detect USB 2.0 and USB 1.1 device with the fix.

  [Regression Potential]
  Low. Has limited scope and doesn't touch any driver code.

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

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

[Kernel-packages] [Bug 1848299] Re: Enable loading GuC firmware for Intel GLK

[Timo Aaltonen]

** Package changed: linux-oem-osp1 (Ubuntu) => linux-oem (Ubuntu)

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

Title:
   Enable loading GuC firmware for Intel GLK

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Triaged

Bug description:
  The needed patch was identified as
  "
  commit 415e7f0a7b89758c752da3f61794614e25939e1b
  > Author: Michal Wajdeczko  >
  > Date:   Mon May 27 18:36:02 2019 +
  >
  > drm/i915/guc: Define GuC firmware version for Geminilake
  >
  > Define GuC firmware version for Geminilake.

  "

  Without it, we got the following message in system log for Intel GLK
  platforms:

   i915 :00:02.0: GuC: No firmware known for this platform!

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

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

[Kernel-packages] [Bug 1848333] Re: wifi problem delays boot in live mode

[sudodus]

I had also an Ubuntu Eoan iso file from Sept 25 and got a new one now.
Both boot fast, but do not behave in the same way. The current Ubuntu
sends a notify message to the desktop:

"Network service discovery disabled
Your current network has a .local domain, which is not recommen..."

This notice is not sent to the desktop by the Ubuntu Eoan iso file from
Sept 25.

I want to mention this, but am not sure it is related to what I think is
a bug in Lubuntu and Xubuntu.

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.sku: PSCBXE
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1847596] Re: rpi3b+: corrupted screen on hdmi

[Francis Ginther]

** Tags added: id-5da6d4ddbf55d385e9c31e0b

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

Title:
  rpi3b+: corrupted screen on hdmi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Eoan daily: 20191010
  Ubuntu Server arm64+raspi3
  HW: Raspberrypi 3 B+

  Initial boot ok but as soon as changing to the high resolution
  framebuffer, the whole screen consists mostly of bright yellow and
  darker yellow vertical stipes. Further boot messages are visible but
  barely readable. Device is accessible via ssh. The dmesg there shows
  some kernel warnings:

  [1.450650] bcm2708_fb soc:fb: FB found 1 display(s)
  [1.452916] WARNING: CPU: 2 PID: 1 at mm/page_alloc.c:4696 
__alloc_pages_nodemask+0x284/0x2c8
  [1.460096] Modules linked in:
  [1.467227] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.3.0-1005-raspi2 
#6-Ubuntu
  [1.474549] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
  [1.481908] pstate: 2045 (nzCv daif +PAN -UAO)
  [1.489237] pc : __alloc_pages_nodemask+0x284/0x2c8
  [1.496499] lr : __dma_direct_alloc_pages+0x100/0x1e8
  ...
  [1.761649] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 
1824x984
  [1.850950] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
  [1.859009] bcm2835-rng 3f104000.rng: hwrng registered
  [1.865102] vc-mem: phys_addr:0x mem_base=0x3ec0 
mem_size:0x4000(1024 MiB)
  ...
  [2.909823] WARN::dwc_otg_hcd_init:1043: FIQ DMA bounce buffers: virt = 
10616000 dma = 0xfad1 len=9024
  ...
  [2.946722] WARN::hcd_init_fiq:496: MPHI regs_base at 10075000

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

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

[Kernel-packages] [Bug 1848318] Re: [DELL][BIONICS] Observed firmware assert during backgroung scan.

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [DELL][BIONICS] Observed firmware assert during backgroung scan.

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

Bug description:
  SRU Justification:
  --

  Impact:
  ---
Observed firmware assert(non responsive state) just 2 min after 
connection.

  Test case:
  --
1) Power up the device, Redpine modules are loaded by default, Nmcli 
initiates the connection and device starts background scan after connection. 
After 2-3 min issue will be replicated. 

  Result:
  ---
 Observed firmware assert while performing background scan.

  Root cause analysis:
  
 There is a redundant null check for ssid info while preparing
  probe request in background scan case, which blocks the probe request pkt
  length update, leads to assert no-71(if probe-req-length is 0 or greater
  the max probe length 120) in firmware.

  Fix:
  
 Removed the redundant null check.

  Regression Potential:
  -
  This is observed just 2 min after connection, fixed and checked the 
driver stability. Every thing ran smooth.

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

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

[Kernel-packages] [Bug 1848318] Re: [DELL][BIONICS] Observed firmware assert during backgroung scan.

[Ganapathi Raju Kondraju]

** Patch added: "0001-OEM-B-rsi-fix-for-fw-assert-during-bg-scan.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848318/+attachment/5297472/+files/0001-OEM-B-rsi-fix-for-fw-assert-during-bg-scan.patch

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

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

Title:
  [DELL][BIONICS] Observed firmware assert during backgroung scan.

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

Bug description:
  SRU Justification:
  --

  Impact:
  ---
Observed firmware assert(non responsive state) just 2 min after 
connection.

  Test case:
  --
1) Power up the device, Redpine modules are loaded by default, Nmcli 
initiates the connection and device starts background scan after connection. 
After 2-3 min issue will be replicated. 

  Result:
  ---
 Observed firmware assert while performing background scan.

  Root cause analysis:
  
 There is a redundant null check for ssid info while preparing
  probe request in background scan case, which blocks the probe request pkt
  length update, leads to assert no-71(if probe-req-length is 0 or greater
  the max probe length 120) in firmware.

  Fix:
  
 Removed the redundant null check.

  Regression Potential:
  -
  This is observed just 2 min after connection, fixed and checked the 
driver stability. Every thing ran smooth.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.sku: PSCBXE
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1848333] Re: wifi problem delays boot in live mode

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1848333

** Tags added: iso-testing

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.sku: PSCBXE
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1848333] Re: wifi problem delays boot in live mode

[sudodus]

attached what I think are relevant lines from 'syslog'

** Attachment added: "relevant lines from 'syslog'"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297468/+files/temp.txt

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.sku: PSCBXE
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1848333] [NEW] wifi problem delays boot in live mode

[sudodus]

Public bug reported:

This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
days ago (Oct 6).

Now there is a delay of 1 min 30 sec during booting, and I think there
is something wrong with the recognition of the wifi hardware or maybe
matching of driver and hardware. It happens in 'this' computer, a
middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also in
a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
another wifi chip.

In both cases both ethernet and wifi works. I see available wifi routers
and can connect (when I have the password).

I tested also with the Xubuntu eoan iso file, and the same delay
happened there.

I think the drivers are OK, but something in the logic for recognition
of them might be bad.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lubuntu2316 F pulseaudio
CasperVersion: 1.426
CurrentDesktop: LXQt
Date: Wed Oct 16 11:36:22 2019
LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
persistent ---
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic  N/A
 linux-firmware1.183
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.sku: PSCBXE
dmi.product.version: PSCBXE-00C00VN5
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug eoan iso-testing

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: