[Kernel-packages] [Bug 1837005] [NEW] cve-2015-3290 in cve from ubuntu_ltp failed with D-i386

[Po-Hsu Lin]

Public bug reported:

This issue was only spotted on an i386 node "pepe" with Disco kernel,
passed with other arch with Disco.

On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
Will need to verify this manually.
 
Test report:
<<>>
tag=cve-2015-3290 stime=1563431630
cmdline="cve-2015-3290"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
cve-2015-3290.c:460: FAIL: corrupted NMI stack

Summary:
passed   0
failed   1
skipped  0
warnings 0

syslog output:
 06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
 06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 
2500), lowering kernel.perf_event_max_sample_rate to 79250
 06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed
 06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general 
protection fault ip:46c0ef sp:b7d43280 error:800
 06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 crashed
 06:33:50 pepe AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760']
 06:33:50 pepe AutotestCrashHandler: Could not determine from which application 
core file 
/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core
 is from

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-20-generic 5.0.0-20.21
ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic i686
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 18 04:53 seq
 crw-rw 1 root audio 116, 33 Jul 18 04:53 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: i386
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:
 [ 6042.144077] LTP: starting cve-2015-3290
 [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79250
 [ 6042.159531] show_signal: 16 callbacks suppressed
 [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef 
sp:b7d43280 error:800
Date: Thu Jul 18 06:36:51 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R310
PciMultimedia:
 
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-20-generic N/A
 linux-backports-modules-5.0.0-20-generic  N/A
 linux-firmware1.178.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 05XKKK
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R310
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug disco i386 uec-images

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

Title:
  cve-2015-3290 in cve from ubuntu_ltp failed with D-i386

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue was only spotted on an i386 node "pepe" with Disco kernel,
  passed with other arch with Disco.

  On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
  Will need to verify this manually.
   
  Test report:
  <<>>
  tag=cve-2015-3290 stime=1563431630
  cmdline="cve-2015-3290"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
  cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
  cve-2015-3290.c:460: FAIL: corrupted NMI stack

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  syslog output:
   06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
   06:33:50 pepe kernel: [ 6042.159521] perf: i

[Kernel-packages] [Bug 1837005] Re: cve-2015-3290 in cve from ubuntu_ltp failed with D-i386

[Po-Hsu Lin]

>From the description of this CVE[1]:
arch/x86/entry/entry_64.S in the Linux kernel before 4.1.6 on the x86_64
platform improperly relies on espfix64 during nested NMI processing, which
allows local users to gain privileges by triggering an NMI within a certain
instruction window.

It looks like this is x86_64 specific.

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

Title:
  cve-2015-3290 in cve from ubuntu_ltp failed with D-i386

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue was only spotted on an i386 node "pepe" with Disco kernel,
  passed with other arch with Disco.

  On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
  Will need to verify this manually.
   
  Test report:
  <<>>
  tag=cve-2015-3290 stime=1563431630
  cmdline="cve-2015-3290"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
  cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
  cve-2015-3290.c:460: FAIL: corrupted NMI stack

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  syslog output:
   06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
   06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 
2500), lowering kernel.perf_event_max_sample_rate to 79250
   06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed
   06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general 
protection fault ip:46c0ef sp:b7d43280 error:800
   06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 
crashed
   06:33:50 pepe AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760']
   06:33:50 pepe AutotestCrashHandler: Could not determine from which 
application core file 
/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core
 is from

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 04:53 seq
   crw-rw 1 root audio 116, 33 Jul 18 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  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:
   [ 6042.144077] LTP: starting cve-2015-3290
   [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79250
   [ 6042.159531] show_signal: 16 callbacks suppressed
   [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef 
sp:b7d43280 error:800
  Date: Thu Jul 18 06:36:51 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1837005] 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 1837005

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

Title:
  cve-2015-3290 in cve from ubuntu_ltp failed with D-i386

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue was only spotted on an i386 node "pepe" with Disco kernel,
  passed with other arch with Disco.

  On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
  Will need to verify this manually.
   
  Test report:
  <<>>
  tag=cve-2015-3290 stime=1563431630
  cmdline="cve-2015-3290"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
  cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
  cve-2015-3290.c:460: FAIL: corrupted NMI stack

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  syslog output:
   06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
   06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 
2500), lowering kernel.perf_event_max_sample_rate to 79250
   06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed
   06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general 
protection fault ip:46c0ef sp:b7d43280 error:800
   06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 
crashed
   06:33:50 pepe AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760']
   06:33:50 pepe AutotestCrashHandler: Could not determine from which 
application core file 
/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core
 is from

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 04:53 seq
   crw-rw 1 root audio 116, 33 Jul 18 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  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:
   [ 6042.144077] LTP: starting cve-2015-3290
   [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79250
   [ 6042.159531] show_signal: 16 callbacks suppressed
   [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef 
sp:b7d43280 error:800
  Date: Thu Jul 18 06:36:51 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpa

[Kernel-packages] [Bug 1836983] Re: [Intel CyclonePeak] Pairing new BT mouse fails sometimes

[AceLan Kao]

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-firmware (Ubuntu Disco)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Changed in: linux-firmware (Ubuntu Disco)
   Status: New => In Progress

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

Title:
  [Intel CyclonePeak] Pairing new BT mouse fails sometimes

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Disco:
  In Progress

Bug description:
  [Impact]
  After update the BT firmware, it requires to pair twice to pair a new device.
  There should be a "SMP: Pairing Request" send from hci0, but it doesn't be 
submitted in the first time.

  [Fix]
  The new firmware fix this issue.

  [Test]
  Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95)

  [Regression Potential]
  Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't 
affect the devices on the market currently.

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

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

[Kernel-packages] [Bug 1836153] Re: [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part

[Stefan Bader]

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

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

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

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

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

Title:
  [18.04 FEAT] zKVM: Add hardware CPU Model - kernel part

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * New hardware is not supported by qemu and won't run run, due to
  missing hardware CPU model

  [Fix]

  * 11ba5961a2156a4f210627ed8421387e2531b100 11ba596 "KVM: s390: add
  debug logging for cpu model subfunctions"

  * 346fa2f891c71a9b98014f8f62c15f4c7dd95ec1 346fa2f "KVM: s390:
  implement subfunction processor calls"

  * 7832e91cd33f21f3cf82b003478c292915a1ec14 7832e91 "KVM: s390: add
  vector enhancements facility 2 to cpumodel"

  * d5cb6ab1e3d4d7e0648a167f6290e89f6e86964e d5cb6ab "KVM: s390: add
  vector BCD enhancements facility to cpumodel"

  * 13209ad0395c4de7fa48108b1dac72e341d5c089 13209ad "KVM: s390: add
  MSA9 to cpumodel"

  * d668139718a9e2260702777bd8d86d71c30b6539 d668139 "KVM: s390: provide
  query function for instructions returning 32 byte"

  * 173aec2d5a9fa5f40e462661a8283fcafe04764f 173aec2 "KVM: s390: add
  enhanced sort facilty to cpu model"

  * 4f45b90e1c03466202fca7f62eaf32243f220830 4f45b90 "KVM: s390: add
  deflate conversion facilty to cpu model"

  * 8ec2fa52eac53bff7ef1cedbc4ad8af650ec937c 8ec2fa5 "KVM: s390: enable
  MSA9 keywrapping functions depending on cpu model"

  [Test Case]

  * need to be tested by IBM on pre-rel. hardware or simulator

  [Regression Potential]

  * The regression potential can be considered as low since these
  changes are limited to arch/s390

  * changes are in support for new and upcoming hardware and shouldn't
  affect existing s390x systems

  [Other Info]

  * the first 2 commits are the key ones, the other 7 are needed to make
  them applly cleanly

  * these patches are already all included in upstream kernel 5.2, hence
  they are in eoan's kernel 5.2

  * qemu package SRU in LP 1836154 complements this SRU - for testing
  both need to be in place

  * I could apply the commit IDs cleanly with 'cherry-picks 
--strategy=recursive -X theirs' and checked that no patches on top were pulled 
in
  _

  Feature request to be applied to  Ubuntu 18.04 - kernel.

  The git commit information is already provided within
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830239

  Once this feature is accepted all information for integration will be 
provided by IBM
  kernel 5.2 down to 4.15.

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

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

[Kernel-packages] [Bug 1837005] Re: cve-2015-3290 in cve from ubuntu_ltp failed with D-i386

[Po-Hsu Lin]

Test case from LTP
https://github.com/linux-test-project/ltp/blob/master/testcases/cve/cve-2015-3290.c

** Summary changed:

- cve-2015-3290 in cve from ubuntu_ltp failed with D-i386
+ cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386

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

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

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

** Tags added: 4.15 5.0 sru-20190701 ubuntu-ltp

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

Title:
  cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386

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

Bug description:
  This issue was only spotted on an i386 node "pepe" with Disco kernel,
  passed with other arch with Disco.

  On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
  Will need to verify this manually.
   
  Test report:
  <<>>
  tag=cve-2015-3290 stime=1563431630
  cmdline="cve-2015-3290"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
  cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
  cve-2015-3290.c:460: FAIL: corrupted NMI stack

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  syslog output:
   06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
   06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 
2500), lowering kernel.perf_event_max_sample_rate to 79250
   06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed
   06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general 
protection fault ip:46c0ef sp:b7d43280 error:800
   06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 
crashed
   06:33:50 pepe AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760']
   06:33:50 pepe AutotestCrashHandler: Could not determine from which 
application core file 
/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core
 is from

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 04:53 seq
   crw-rw 1 root audio 116, 33 Jul 18 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  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:
   [ 6042.144077] LTP: starting cve-2015-3290
   [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79250
   [ 6042.159531] show_signal: 16 callbacks suppressed
   [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef 
sp:b7d43280 error:800
  Date: Thu Jul 18 06:36:51 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

Re: [Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

[Sumneet Kaur Bamrah]

Thanks for sharing Kai! It seems fuzzy. Understanding how it taints a
kernel is challenging.

On Wed, Jul 17, 2019 at 7:50 PM Kai-Heng Feng 
wrote:

> https://unix.stackexchange.com/questions/208638/linux-kernel-meaning-of-
> source-tree-in-tree-and-out-of-tree
> 
>
> A quick search Google shows many results.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1831710
>
> Title:
>   Touchpad not working (Lenevo Ideapad 330 series)
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The touch pad has not been used since the purchase of the product.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>   Uname: Linux 4.18.0-21-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Jun  5 13:41:22 2019
>   InstallationDate: Installed on 2019-06-05 (0 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   SourcePackage: linux-signed-hwe
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  athena 1232 F pulseaudio
>/dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
>/dev/snd/controlC0:  athena 1232 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   InstallationDate: Installed on 2019-06-05 (1 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   MachineType: LENOVO 81D2
>   Package: linux (not installed)
>   ProcFB: 0 amdgpudrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
> root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>   RelatedPackageVersions:
>linux-restricted-modules-4.18.0-21-generic N/A
>linux-backports-modules-4.18.0-21-generic  N/A
>linux-firmware 1.173.6
>   Tags:  bionic
>   Uname: Linux 4.18.0-21-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 12/10/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7VCN46WW
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: NO DPK
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Lenovo ideapad 330-15ARR
>   dmi.modalias:
> dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
>   dmi.product.family: ideapad 330-15ARR
>   dmi.product.name: 81D2
>   dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
>   dmi.product.version: Lenovo ideapad 330-15ARR
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions
>


-- 
Thanks and Regards,
Sumneet Kaur Bamrah

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

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  athena 1232 F pulseaudio
   /dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
   /dev/snd/controlC0:  athena 1232 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-06-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Mac

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

[bugproxy]

--- Comment From tmri...@de.ibm.com 2019-07-18 03:46 EDT---
I have this /etc/apt/sources.list file with the following deb-src lines

root@s8360046:~# fgrep bionic /etc/apt/sources.list | fgrep deb-src
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic main restricted
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-updates main restricted
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic universe
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-updates universe
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic multiverse
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-updates multiverse
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-backports main 
restricted universe multiverse
# deb-src http://archive.canonical.com/ubuntu bionic partner
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-security main restricted
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-security universe
deb-src http://us.ports.ubuntu.com/ubuntu-ports bionic-security multiverse
root@s8360046:~# apt-get source linux-image-$(uname -r)
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
root@s8360046:~# uname -r
4.15.0-55-generic
root@s8360046:~#

But this is not really the issue.

To debug this further I need the linux kernel tree (tarball preferred)
or at least the subdirectory tools inside the linux kernel tree:

root@s8360046:~# ls -ld ubuntu-*
drwxr-xr-x 31 root root 4096 Jul  5 13:37 ubuntu-bionic
drwxr-xr-x 29 root root 4096 Jul 17 14:17 ubuntu-disco
root@s8360046:~# ls -ld ubuntu-bionic/tools/perf
drwxr-xr-x 14 root root 4096 Jul  5 13:47 ubuntu-bionic/tools/perf  < perf 
tool source directory.
root@s8360046:~#

I need this from the build done by kleber-souza  (see entry 38 dated on 
2019-07-15 10:07:50 CDT)
with the kernel named
Linux s8360046 4.15.0-55-generic #60+lp1828166.2-Ubuntu SMP Fri Jul 12 12:49:26
>From this tree I would like to get a tar file of the tools directory.

Thanks a lot.

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

Title:
  perf top problem on z with Ubuntu 18.04

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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

[Kernel-packages] [Bug 1836914] Re: Doing multiple squashfs (and other loop?) mounts in parallel breaks

[Kai-Heng Feng]

Commit that causes the regression:
commit 33ec3e53e7b1869d7851e59e126bdb0fe0bd1982
Author: Jan Kara 
Date:   Thu May 16 16:01:27 2019 +0200

loop: Don't change loop device under exclusive opener

Loop module allows calling LOOP_SET_FD while there are other openers of
the loop device. Even exclusive ones. This can lead to weird
consequences such as kernel deadlocks like:

mount_bdev()lo_ioctl()
  udf_fill_super()
udf_load_vrs()
  sb_set_blocksize() - sets desired block size B
  udf_tread()
sb_bread()
  __bread_gfp(bdev, block, B)
  loop_set_fd()
set_blocksize()
- now __getblk_slow() indefinitely loops because B != bdev
  block size

Fix the problem by disallowing LOOP_SET_FD ioctl when there are
exclusive openers of a loop device.

[Deliberately chosen not to CC stable as a user with priviledges to
trigger this race has other means of taking the system down and this
has a potential of breaking some weird userspace setup]

Seems like it solves a race so I'll raise the issue to the commit
author.

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

Title:
  Doing multiple squashfs (and other loop?) mounts in parallel breaks

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a system running a 5.2 kernel, doing a large number of mounts of
  squashfs filesystems in parallel results in the mounts getting out of
  sync with their backing devices.

  To reproduce,

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

  this breaks people with ~40 snaps (easily achievable given snapd
  leaves up to 3 previous revisions of snaps mounted at any given time,
  so a person with ~13 snaps that get updated often will hit this
  number).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 17 15:11:15 2019
  InstallationDate: Installed on 2019-07-17 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190716)
  IwConfig:
   ens3  no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=9618ebbb-955d-4daf-b29a-37162ec7821a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor

[Timo Aaltonen]

** Description changed:

- Summary:
+ [Impact]
  System does not auto detect disconnection of external monitor
  
  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor
  
  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable
  
  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.
  
  Failure rate:
  2/10 to 1/10
+ 
+ [Fix]
+ two commits from upstream drm-intel-next-queued branch
+ 
+ [Test case]
+ see "steps to reproduce"
+ 
+ [Regression potential]
+ still possible, but for the distro only Eoan will get it. OEM kernels will 
get tested on systems that get it.

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

Title:
  System does not auto detect disconnection of external monitor

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New

Bug description:
  [Impact]
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

  [Fix]
  two commits from upstream drm-intel-next-queued branch

  [Test case]
  see "steps to reproduce"

  [Regression potential]
  still possible, but for the distro only Eoan will get it. OEM kernels will 
get tested on systems that get it.

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

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

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 08:41 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -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: 1834954
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 17. July 2019 20:40 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 08:41 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  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/1836925

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 08:41 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => 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/1835001

Title:
  System does not auto detect disconnection of external monitor

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

  [Fix]
  two commits from upstream drm-intel-next-queued branch

  [Test case]
  see "steps to reproduce"

  [Regression potential]
  still possible, but for the distro only Eoan will get it. OEM kernels will 
get tested on systems that get it.

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

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker

[Canonical Certification Team]

Kernel deb testing completes, no regressions found. Ready for Updates.
Results here: https://trello.com/c/Vvxn0MVK/101-bionic-linux-
image-4150-55-generic-4150-5560

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.15.0-55.60 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -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
  
  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 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

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

Title:
  linux: 4.15.0-55.60 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Łukasz Zemczak (sil2100) => Ubuntu Stable Release Updates Team 
(ubuntu-sru)

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

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 18. July 2019 09:08 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine

[Stefan Bader]

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

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

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: New => Invalid

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

Title:
  alsa/hdmi: add icelake hdmi audio support for a Dell machine

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

Bug description:
  [Impact]
  On a Dell icelake platform, the hdmi audio doesn't work at all, when users
  plug hdmi cable, they can't find hdmi audio from gnome-sound-setting.

  [Fix]
  add icl hdmi audio id and related support patch to alsa driver.

  [Test Case]
  after applying the patchset, we plug hdmi cable and the hdmi audio shows up
  in the sound-setting and works well, after unplugging the cable, the hdmi
  audio disappears as expected.

  [Regression Risk]
  Low. this patchset is specific to a icl hdmi audio codec.

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

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

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -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: 1834954
- phase: Promote to Proposed
- phase-changed: Thursday, 18. July 2019 08:41 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 09:08 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- ready for review
  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/1836925

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 18. July 2019 09:08 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1834884] Re: linux-raspi2: 5.0.0-1013.13 -proposed tracker

[Taihsiang Ho]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-raspi2: 5.0.0-1013.13 -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:
  New
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:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  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: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -proposed tracker

[Taihsiang Ho]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-snapdragon: 5.0.0-1017.18 -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:
  New
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:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  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: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine

[Stefan Bader]

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

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

Title:
  alsa/hdmi: add icelake hdmi audio support for a Dell machine

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

Bug description:
  [Impact]
  On a Dell icelake platform, the hdmi audio doesn't work at all, when users
  plug hdmi cable, they can't find hdmi audio from gnome-sound-setting.

  [Fix]
  add icl hdmi audio id and related support patch to alsa driver.

  [Test Case]
  after applying the patchset, we plug hdmi cable and the hdmi audio shows up
  in the sound-setting and works well, after unplugging the cable, the hdmi
  audio disappears as expected.

  [Regression Risk]
  Low. this patchset is specific to a icl hdmi audio codec.

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

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

[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices

[Stefan Bader]

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

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

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

Title:
  bcache: risk of data loss on I/O errors in backing or caching devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * The bcache code in Bionic lacks several fixes to handle
     I/O errors in both backing devices and caching devices.

   * Partial or permanent errors in backing or caching devices,
     specially in writeback mode, can lead to data loss and/or
     the application is not notified about failed I/O requests.

   * The bcache device might remain available for I/O requests
     even if backing device is offline, so writes are undefined.

  [Test Case]

   * Detailed test cases/steps for the behavior of many patches
     with code logic changes are provided in bug comments.

   * The patchset has been tested for regressions on each cache
     mode (writethrough, writeback, writearound, none) with the
     xfstests test suite (on ext4) and fio (sequential + random
     read-write).

  [Regression Potential]

   * The patchset is relatively large and touches several areas
     in bcache code, however, synthetic testing of the patches
     has been performed, and extensive regression/stress tests
     were run (as mentioned in Test Case section).

   * Many patches in the patchset are 'Fixes' patches to other
     patches, and no further 'Fixes' currently exist upstream.

  [Other Info]

   * Canonical Field Eng. deploys bcache+writeback extensively
     (e.g., BootStack, UA cloud, except rare all-flash cases).

  [Original Bug Description]

  This is a request for a backport of the following upstream patch from
  4.18:

  "bcache: stop bcache device when backing device is offline"
  
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee

  Field engineering uses bcache quite extensively and it would be good
  to have this in the GA/bionic kernel.

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

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

[Kernel-packages] [Bug 1834884] Re: linux-raspi2: 5.0.0-1013.13 -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: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834884

Title:
  linux-raspi2: 5.0.0-1013.13 -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:
  New
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:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  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: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -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: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1834894

Title:
  linux-snapdragon: 5.0.0-1017.18 -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:
  New
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:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Disco:
  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: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Timo Aaltonen]

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

** Summary changed:

- Black screen on skylake after 18.0 => 18.2 update
+ [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault

[Kai-Heng Feng]

Let's fix the wrong altsetting first:
https://lkml.org/lkml/2019/7/18/227

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

Title:
  Line 6 POD HD500 driver fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";

  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  uname:

  Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15
  17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  lspci -vnvn  https://pastebin.com/7KM9bybk


  dmesg:

  usb 1-5: new high-speed USB device number 6 using xhci_hcd
  [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d
  [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 44.209072] usb 1-5: Product: POD HD500
  [ 44.209076] usb 1-5: Manufacturer: Line 6
  [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found
  [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached
  [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found
  [ 44.211289] usb 1-5: selecting invalid altsetting 1
  [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed
  [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected
  [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22
  [ 69.605987] nvidia-modeset: Allocated GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 69.606386] nvidia-modeset: Freed GPU:0
  (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0
  [ 153.206595] usb 1-5: USB disconnect, device number 6
  [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected
  [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd
  [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x1 has invalid maxpacket 64
  [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint
  0x81 has invalid maxpacket 64
  [ 165.843146] usb 1-1: New USB device found, idVendor=0e41,
  idProduct=414d
  [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2,
  SerialNumber=0
  [ 165.843149] usb 1-1: Product: POD HD500
  [ 165.843150] usb 1-1: Manufacturer: Line 6
  [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found
  [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached
  [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
  [ 165.844742] usb 1-1: selecting invalid altsetting 1
  [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed
  [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected
  [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-03 (63 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency 
root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-lowlatency N/A
   linux-backports-modules-4.15.0-33-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.n

[Kernel-packages] [Bug 1815214] Re: Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue

[João Pedro Seara]

Currently facing the same issue myself.

ThinkPad T480s 20L7
Ubuntu 18.04.2 LTS
Linux localhost 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

$ sudo fwupdmgr hwids

Computer Information

BiosVendor: LENOVO
BiosVersion: N22ET54W (1.31 )
BiosMajorRelease: 01
BiosMinorRelease: 1f
Manufacturer: LENOVO
Family: ThinkPad T480s
ProductName: 20L7001LPG
ProductSku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
EnclosureKind: a
BaseboardManufacturer: LENOVO
BaseboardProduct: 20L7001LPG 

** Summary changed:

- Lenovo T480: throttling CPU issue
+ Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue

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

Title:
  Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
  drastically CPU performance under load.

  Apparently many Lenovo laptops (certified for Ubuntu) are affected.
  The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  There is "hacky" workaround (not compatible with SecureBoot, a Python
  script writing MSR registers periodically) :
  https://github.com/erpalma/throttled

  There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
  /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
  Linux/td-p/4028489

  I confirm the issue affect my machine running the latest kernel
  (4.15.0-45-generic, although bug affects previous releases as well)
  and using the latest firmware from Lenovo (1.19).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   4050 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   4050 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb  8 17:14:17 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (309 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04

[Frank Heimes]

'apt-get source' should work - just double checked it here:

# just these two deb-src lines should be sufficient:
$ grep ^deb-src /etc/apt/sources.list
deb-src http://us.ports.ubuntu.com/ubuntu-ports/ bionic main
deb-src http://us.ports.ubuntu.com/ubuntu-ports/ bionic-updates main

$ apt-get source linux-image-$(uname -r)
Reading package lists... Done
Picking 'linux' as source package instead of 'linux-image-4.15.0-54-generic'
NOTICE: 'linux' packaging is maintained in the 'Git' version control system at:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic
Please use:
git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic
to retrieve the latest (possibly unreleased) updates to the package.
Skipping already downloaded file 'linux_4.15.0-54.58.dsc'
Skipping already downloaded file 'linux_4.15.0.orig.tar.gz'
Skipping already downloaded file 'linux_4.15.0-54.58.diff.gz'
Need to get 0 B of source archives.
Skipping unpack of already unpacked source in linux-4.15.0
$

Did you do the required "apt update" after modifying the sources.list
file - to update the local archive package index?

But 'klebers' will share the sources he used ...

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

Title:
  perf top problem on z with Ubuntu 18.04

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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

[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04

[Kleber Sacilotto de Souza]

Hi Thomas,

The tarball with the sources I used to build linux
4.15.0-55.60+lp1828166.2 can be found here:

https://people.canonical.com/~ksouza/lp1828166/bionic/linux-
source-4.15.0.tar.bz2

md5sum:
58e725a4c20dcf3fb0b209e3d6155e74  linux-source-4.15.0.tar.bz2

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

Title:
  perf top problem on z with Ubuntu 18.04

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The perf top tool hangs and shows error messages, like 'Not enough
  memory for annotating'

  [Fix]

  * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop
  fallbacking to kallsyms for vdso symbols lookup"

  [Test Case]

  * start a benchmark (mem_alloc, but it doesn't really matter what)

  * execute perf top in a second terminal

  * the output of perf top is correct

  * now stop the benchmark

  * and perf top shows an error message, like "Not enough memory for
  annotating '__irf_end' symbol!)"

  * and perf top can't be exited anymore

  [Regression Potential]

  * The regression potential can be considered as low since this happens
  only while using the perf top tool

  * and it is known that the commit (above) fixes the problem

  * and the fix is upstream since 4.19

  [Other Info]

  * current disco and eoan kernels don't show that problem

  * bisecting result points to above commit

  * applies cleanly on cosmic, but has a little conflict on bionic (both 
master-next)
  _

  perf top hangs and shows error messages

  ---uname output---
  Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
   I start a benchmark (mem_alloc, but it really doesn't matter) and then issue 
perf top in a second terminal, the output from perf top is correct. Now I stop 
the benchmark: perf top shows a error message (Not enough memory for annotating 
'__irf_end' symbol!) and I can't quit from perf top anymore

  Following analyse took place:
  No problem with current kernel .
  Bi-Secting of perf tool took place and following commit was found:

  commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad)
  Author: Arnaldo Carvalho de Melo 
  Date:   Tue Oct 16 17:08:29 2018 -0300

  perf tools: Stop fallbacking to kallsyms for vdso symbols lookup

  When you apply this patch the issue is gone, however it is contained
  in these versions:

  git tag --contains  edeb0c90df3581b821
  v4.19
  v4.20
  

  The level I was debugging was kernel 4.15 which does not contain this
  patch.

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

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

[Kernel-packages] [Bug 1837005] Re: cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386

[Po-Hsu Lin]

>From the test source code, it looks like this was designed for both
x86_64 and i386

#if HAVE_PERF_EVENT_ATTR && (defined(__x86_64__) || defined(__i386__))

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

Title:
  cve-2015-3290 in cve from ubuntu_ltp failed with B/D-i386

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

Bug description:
  This issue was only spotted on an i386 node "pepe" with Disco kernel,
  passed with other arch with Disco.

  On B/C i386, the CVE test was not successfully executed, failed with Resource 
temporarily unavailable.
  Will need to verify this manually.
   
  Test report:
  <<>>
  tag=cve-2015-3290 stime=1563431630
  cmdline="cve-2015-3290"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 03m 00s
  cve-2015-3290.c:407: INFO: attempting to corrupt nested NMI stack state
  cve-2015-3290.c:460: FAIL: corrupted NMI stack

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0

  syslog output:
   06:33:50 pepe kernel: [ 6042.144077] LTP: starting cve-2015-3290
   06:33:50 pepe kernel: [ 6042.159521] perf: interrupt took too long (2518 > 
2500), lowering kernel.perf_event_max_sample_rate to 79250
   06:33:50 pepe kernel: [ 6042.159531] show_signal: 16 callbacks suppressed
   06:33:50 pepe kernel: [ 6042.159532] traps: cve-2015-3290[7761] general 
protection fault ip:46c0ef sp:b7d43280 error:800
   06:33:50 pepe AutotestCrashHandler: Application cve-2015-3290, PID 7760 
crashed
   06:33:50 pepe AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760']
   06:33:50 pepe AutotestCrashHandler: Could not determine from which 
application core file 
/home/ubuntu/autotest/client/results/default/ubuntu_ltp.fs/debug/crash.cve-2015-3290.7760/core
 is from

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: User Name 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 04:53 seq
   crw-rw 1 root audio 116, 33 Jul 18 04:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  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:
   [ 6042.144077] LTP: starting cve-2015-3290
   [ 6042.159521] perf: interrupt took too long (2518 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79250
   [ 6042.159531] show_signal: 16 callbacks suppressed
   [ 6042.159532] traps: cve-2015-3290[7761] general protection fault ip:46c0ef 
sp:b7d43280 error:800
  Date: Thu Jul 18 06:36:51 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.178.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1815214] Re: Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue

[Anthony Wong]

I think the solution at https://github.com/intel/dptfxtract/issues/6 can
fix this issue?

** Bug watch added: github.com/intel/dptfxtract/issues #6
   https://github.com/intel/dptfxtract/issues/6

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

Title:
  Lenovo ThinkPad T480/T480s/X1: Throttling CPU issue

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
  drastically CPU performance under load.

  Apparently many Lenovo laptops (certified for Ubuntu) are affected.
  The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  There is "hacky" workaround (not compatible with SecureBoot, a Python
  script writing MSR registers periodically) :
  https://github.com/erpalma/throttled

  There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
  /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
  Linux/td-p/4028489

  I confirm the issue affect my machine running the latest kernel
  (4.15.0-45-generic, although bug affects previous releases as well)
  and using the latest firmware from Lenovo (1.19).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   4050 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   4050 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb  8 17:14:17 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (309 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1837035] [NEW] memcg_stat_rss from controllers in ubuntu_ltp failed with D i386

[Po-Hsu Lin]

Public bug reported:

This issue was spotted on an i386 node "pepe" with Disco kernel,
it failed with:

memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up


<<>>
tag=memcg_stat_rss stime=1563448062
cmdline="memcg_stat_rss.sh"
contacts=""
analysis=exit
<<>>
memcg_stat_rss 1 TINFO: Starting test 1
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
memcg_stat_rss 1 TINFO: Warming up pid: 1784
memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784
memcg_stat_rss 1 TPASS: rss is 135168 as expected
memcg_stat_rss 2 TINFO: Starting test 2
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
memcg_stat_rss 2 TINFO: Warming up pid: 1804
memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804
memcg_stat_rss 2 TPASS: rss is 0 as expected
memcg_stat_rss 3 TINFO: Starting test 3
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
memcg_stat_rss 3 TINFO: Warming up pid: 1825
memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825
memcg_stat_rss 3 TPASS: rss is 0 as expected
memcg_stat_rss 4 TINFO: Starting test 4
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 
135168
memcg_stat_rss 4 TINFO: Warming up pid: 1845
memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up
memcg_stat_rss 5 TINFO: Starting test 5
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
memcg_stat_rss 5 TINFO: Warming up pid: 1858
memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858
memcg_stat_rss 5 TPASS: rss is 135168 as expected
memcg_stat_rss 6 TINFO: Starting test 6
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
memcg_stat_rss 6 TINFO: Warming up pid: 1878
memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878
memcg_stat_rss 6 TPASS: rss is 135168 as expected
memcg_stat_rss 7 TPASS: rss is 0 as expected
memcg_stat_rss 8 TINFO: Starting test 7
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
memcg_stat_rss 8 TINFO: Warming up pid: 1901
memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901
memcg_stat_rss 8 TPASS: rss is 0 as expected
memcg_stat_rss 9 TPASS: rss is 0 as expected
memcg_stat_rss 10 TINFO: Starting test 8
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
memcg_stat_rss 10 TINFO: Warming up pid: 1925
memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925
memcg_stat_rss 10 TPASS: rss is 0 as expected
memcg_stat_rss 11 TPASS: rss is 0 as expected
memcg_stat_rss 12 TINFO: Starting test 9
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 
135168
memcg_stat_rss 12 TINFO: Warming up pid: 1948
memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

memcg_stat_rss 12 TFAIL: Process 1948 exited with 1 after warm up
memcg_stat_rss 13 TINFO: Starting test 10
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 13 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 13 TINFO: Running memcg_process --mmap-lock1 -s 135168
memcg_stat_rss 13 TINFO: Warming up pid: 1961
memcg_stat_rss 13 TINFO: Process is still here after warm up: 1961
memcg_stat_rss 13 TPASS: rss is 135168 as expected
memcg_stat_rss 14 TPASS: rss is 0 as expected
<<>>
initiation_status="ok"
duration=11 termination_type=exited termination_id=1 corefile=no
cutime=20 cstime=7
<<>>

Steps to run this test:
  git clone --depth=1

[Kernel-packages] [Bug 1837036] [NEW] Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386

[semreh]

Public bug reported:

As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2 on
AMD64 and i386 are failing to build.

Build logs at (for example):

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386

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


** Tags: i386

** Tags added: build

** Tags removed: build
** Tags added: i386

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

Title:
  Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2
  on AMD64 and i386

Status in linux package in Ubuntu:
  New

Bug description:
  As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2
  on AMD64 and i386 are failing to build.

  Build logs at (for example):

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386

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

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

[Kernel-packages] [Bug 1837037] [NEW] memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with D i386

[Po-Hsu Lin]

Public bug reported:

Similar to bug 1837035

This memcg_move_charge_at_immigrate_test test failed on an i386 node
"pepe" with Disco kernel.

It failed with:
memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1
after warm up

<<>>
tag=memcg_move_charge_at_immigrate stime=1563448078
cmdline="memcg_move_charge_at_immigrate_test.sh"
contacts=""
analysis=exit
<<>>
memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 1 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon 
-s 135168
memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162
memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm 
up: 2162
memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected
memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected
memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected
memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected
memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 5 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon 
--shm --mmap-file -s 135168
memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after 
warm up
memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 6 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process --mmap-anon 
--shm --mmap-file -s 135168
memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207
memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after 
warm up
memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 7 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process --mmap-anon 
--shm -s 135168
memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: 
memcg_process: shmget() failed: Invalid argument
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

memcg_move_charge_at_immigrate_test 7 TFAIL: Process  exited with 1 after 
warm up
<<>>
initiation_status="ok"
duration=4 termination_type=exited termination_id=1 corefile=no
cutime=9 cstime=2
<<>>

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 "memcg_move_charge_at_immigrate  memcg_move_charge_at_immigrate_test.sh" 
> /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 i686
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 18 10:01 seq
 crw-rw 1 root audio 116, 33 Jul 18 10:01 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: i386
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 Jul 18 11:16:36 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R310
PciMultimedia:

ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
RelatedPackageVersions:
 linu

[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed with D i386

[Po-Hsu Lin]

If you run the test again on the same node, it will pass:
<<>>
tag=memcg_stat_rss stime=1563449251
cmdline="memcg_stat_rss.sh"
contacts=""
analysis=exit
<<>>
memcg_stat_rss 1 TINFO: Starting test 1
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
memcg_stat_rss 1 TINFO: Warming up pid: 2865
memcg_stat_rss 1 TINFO: Process is still here after warm up: 2865
memcg_stat_rss 1 TPASS: rss is 135168 as expected
memcg_stat_rss 2 TINFO: Starting test 2
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
memcg_stat_rss 2 TINFO: Warming up pid: 2885
memcg_stat_rss 2 TINFO: Process is still here after warm up: 2885
memcg_stat_rss 2 TPASS: rss is 0 as expected
memcg_stat_rss 3 TINFO: Starting test 3
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
memcg_stat_rss 3 TINFO: Warming up pid: 2905
memcg_stat_rss 3 TINFO: Process is still here after warm up: 2905
memcg_stat_rss 3 TPASS: rss is 0 as expected
memcg_stat_rss 4 TINFO: Starting test 4
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 
135168
memcg_stat_rss 4 TINFO: Warming up pid: 2925
memcg_stat_rss 4 TINFO: Process is still here after warm up: 2925
memcg_stat_rss 4 TPASS: rss is 135168 as expected
memcg_stat_rss 5 TINFO: Starting test 5
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
memcg_stat_rss 5 TINFO: Warming up pid: 2947
memcg_stat_rss 5 TINFO: Process is still here after warm up: 2947
memcg_stat_rss 5 TPASS: rss is 135168 as expected
memcg_stat_rss 6 TINFO: Starting test 6
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
memcg_stat_rss 6 TINFO: Warming up pid: 2967
memcg_stat_rss 6 TINFO: Process is still here after warm up: 2967
memcg_stat_rss 6 TPASS: rss is 135168 as expected
memcg_stat_rss 7 TPASS: rss is 0 as expected
memcg_stat_rss 8 TINFO: Starting test 7
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
memcg_stat_rss 8 TINFO: Warming up pid: 2990
memcg_stat_rss 8 TINFO: Process is still here after warm up: 2990
memcg_stat_rss 8 TPASS: rss is 0 as expected
memcg_stat_rss 9 TPASS: rss is 0 as expected
memcg_stat_rss 10 TINFO: Starting test 8
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
memcg_stat_rss 10 TINFO: Warming up pid: 3013
memcg_stat_rss 10 TINFO: Process is still here after warm up: 3013
memcg_stat_rss 10 TPASS: rss is 0 as expected
memcg_stat_rss 11 TPASS: rss is 0 as expected
memcg_stat_rss 12 TINFO: Starting test 9
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 
135168
memcg_stat_rss 12 TINFO: Warming up pid: 3042
memcg_stat_rss 12 TINFO: Process is still here after warm up: 3042
memcg_stat_rss 12 TPASS: rss is 135168 as expected
memcg_stat_rss 13 TPASS: rss is 0 as expected
memcg_stat_rss 14 TINFO: Starting test 10
/opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
memcg_stat_rss 14 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
memcg_stat_rss 14 TINFO: Running memcg_process --mmap-lock1 -s 135168
memcg_stat_rss 14 TINFO: Warming up pid: 3065
memcg_stat_rss 14 TINFO: Process is still here after warm up: 3065
memcg_stat_rss 14 TPASS: rss is 135168 as expected
memcg_stat_rss 15 TPASS: rss is 0 as expected
<<>>
initiation_status="ok"
duration=11 termination_type=exited termination_id=0 corefile=no
cutime=19 cstime=9
<<>>

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

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed with D i386

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

[Kernel-packages] [Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp failed with D i386

[Po-Hsu Lin]

If you run this test again on the same node, it will pass:
<<>>
tag=memcg_move_charge_at_immigrate stime=1563449267
cmdline="memcg_move_charge_at_immigrate_test.sh"
contacts=""
analysis=exit
<<>>
memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 1 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon 
-s 135168
memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 3263
memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm 
up: 3263
memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected
memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected
memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected
memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected
memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 5 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon 
--shm --mmap-file -s 135168
memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 3293
memcg_move_charge_at_immigrate_test 5 TINFO: Process is still here after warm 
up: 3293
memcg_move_charge_at_immigrate_test 5 TPASS: rss is 135168 as expected
memcg_move_charge_at_immigrate_test 6 TPASS: cache is 0 as expected
memcg_move_charge_at_immigrate_test 7 TPASS: rss is 0 as expected
memcg_move_charge_at_immigrate_test 8 TPASS: cache is 270336 as expected
memcg_move_charge_at_immigrate_test 9 TINFO: Starting test 3
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 9 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 9 TINFO: Running memcg_process --mmap-anon 
--shm --mmap-file -s 135168
memcg_move_charge_at_immigrate_test 9 TINFO: Warming up pid: 3323
memcg_move_charge_at_immigrate_test 9 TINFO: Process is still here after warm 
up: 3323
memcg_move_charge_at_immigrate_test 9 TPASS: rss is 0 as expected
memcg_move_charge_at_immigrate_test 10 TPASS: cache is 270336 as expected
memcg_move_charge_at_immigrate_test 11 TPASS: rss is 135168 as expected
memcg_move_charge_at_immigrate_test 12 TPASS: cache is 0 as expected
memcg_move_charge_at_immigrate_test 13 TINFO: Starting test 4
/opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: 
I/O error
memcg_move_charge_at_immigrate_test 13 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
memcg_move_charge_at_immigrate_test 13 TINFO: Running memcg_process --mmap-anon 
--shm -s 135168
memcg_move_charge_at_immigrate_test 13 TINFO: Warming up pid: 3353
memcg_move_charge_at_immigrate_test 13 TINFO: Process is still here after warm 
up: 3353
memcg_move_charge_at_immigrate_test 13 TPASS: rss is 135168 as expected
memcg_move_charge_at_immigrate_test 14 TPASS: cache is 135168 as expected
memcg_move_charge_at_immigrate_test 15 TPASS: rss is 0 as expected
memcg_move_charge_at_immigrate_test 16 TPASS: cache is 0 as expected
<<>>
initiation_status="ok"
duration=4 termination_type=exited termination_id=0 corefile=no
cutime=13 cstime=3
<<>>

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

Title:
  memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp
  failed with D i386

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

Bug description:
  Similar to bug 1837035

  This memcg_move_charge_at_immigrate_test test failed on an i386 node
  "pepe" with Disco kernel.

  It failed with:
  memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with
  1 after warm up

  <<>>
  tag=memcg_move_charge_at_immigrate stime=1563448078
  cmdline="memcg_move_charge_at_immigrate_test.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 1 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process 
--mmap-anon -s 135168
  memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162
  memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm 
up: 2162
  memcg_move_charge_at_immigrate_test 1 TPASS: r

[Kernel-packages] [Bug 1837035] 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/1837035

Title:
  memcg_stat_rss from controllers in ubuntu_ltp failed with D i386

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

Bug description:
  This issue was spotted on an i386 node "pepe" with Disco kernel,
  it failed with:

  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up

  
  <<>>
  tag=memcg_stat_rss stime=1563448062
  cmdline="memcg_stat_rss.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_stat_rss 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 1 TINFO: Warming up pid: 1784
  memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784
  memcg_stat_rss 1 TPASS: rss is 135168 as expected
  memcg_stat_rss 2 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 2 TINFO: Warming up pid: 1804
  memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804
  memcg_stat_rss 2 TPASS: rss is 0 as expected
  memcg_stat_rss 3 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096
  memcg_stat_rss 3 TINFO: Warming up pid: 1825
  memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825
  memcg_stat_rss 3 TPASS: rss is 0 as expected
  memcg_stat_rss 4 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 4 TINFO: Warming up pid: 1845
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

  memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up
  memcg_stat_rss 5 TINFO: Starting test 5
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168
  memcg_stat_rss 5 TINFO: Warming up pid: 1858
  memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858
  memcg_stat_rss 5 TPASS: rss is 135168 as expected
  memcg_stat_rss 6 TINFO: Starting test 6
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168
  memcg_stat_rss 6 TINFO: Warming up pid: 1878
  memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878
  memcg_stat_rss 6 TPASS: rss is 135168 as expected
  memcg_stat_rss 7 TPASS: rss is 0 as expected
  memcg_stat_rss 8 TINFO: Starting test 7
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096
  memcg_stat_rss 8 TINFO: Warming up pid: 1901
  memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901
  memcg_stat_rss 8 TPASS: rss is 0 as expected
  memcg_stat_rss 9 TPASS: rss is 0 as expected
  memcg_stat_rss 10 TINFO: Starting test 8
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096
  memcg_stat_rss 10 TINFO: Warming up pid: 1925
  memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925
  memcg_stat_rss 10 TPASS: rss is 0 as expected
  memcg_stat_rss 11 TPASS: rss is 0 as expected
  memcg_stat_rss 12 TINFO: Starting test 9
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error
  memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm 
-s 135168
  memcg_stat_rss 12 TINFO: Warming up pid: 1948
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process

[Kernel-packages] [Bug 1837037] 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/1837037

Title:
  memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp
  failed with D i386

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

Bug description:
  Similar to bug 1837035

  This memcg_move_charge_at_immigrate_test test failed on an i386 node
  "pepe" with Disco kernel.

  It failed with:
  memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with
  1 after warm up

  <<>>
  tag=memcg_move_charge_at_immigrate stime=1563448078
  cmdline="memcg_move_charge_at_immigrate_test.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 1 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process 
--mmap-anon -s 135168
  memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162
  memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm 
up: 2162
  memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected
  memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected
  memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected
  memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected
  memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 5 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process 
--mmap-anon --shm --mmap-file -s 135168
  memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after 
warm up
  memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 6 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process 
--mmap-anon --shm --mmap-file -s 135168
  memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after 
warm up
  memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 7 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process 
--mmap-anon --shm -s 135168
  memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: 
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 7 TFAIL: Process  exited with 1 after 
warm up
  <<>>
  initiation_status="ok"
  duration=4 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=2
  <<>>

  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 "memcg_move_charge_at_immigrate  
memcg_move_charge_at_immigrate_test.sh" > /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 i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 10:01 seq
   crw-rw 1 root audio 116, 33 Jul 18 10:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer']

[Kernel-packages] [Bug 1837036] 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 1837036

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

Title:
  Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2
  on AMD64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2
  on AMD64 and i386 are failing to build.

  Build logs at (for example):

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386

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

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

[Kernel-packages] [Bug 1837036] Re: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386

[semreh]

The bug is in the Ubuntu controlled mainline kernel build system, and a
link to the logs generated by that system has been provided.

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

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

Title:
  Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2
  on AMD64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2
  on AMD64 and i386 are failing to build.

  Build logs at (for example):

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386

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

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

[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  linux: 4.4.0-156.183 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -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
  
  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 17. July 2019 20:34 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  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/1836880

Title:
  linux: 4.4.0-156.183 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

[AceLan Kao]

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

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

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

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

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

[Kernel-packages] [Bug 1837036] Re: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386

[semreh]

** Tags added: amd64 build kernel mainline

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

Title:
  Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2
  on AMD64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2
  on AMD64 and i386 are failing to build.

  Build logs at (for example):

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386

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

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

[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -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
  
  derivatives: bug 1836875 (pi2-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 17. July 2019 20:42 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 12:03 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  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/1836876

Title:
  linux-raspi2: 4.4.0-1116.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1836875 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:03 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- packages copied to Proposed signed:building
  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/1836880

Title:
  linux: 4.4.0-156.183 -proposed tracker

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

  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
promote-to-proposed: Pending -- packages copied to Proposed signed:building
  variant: debs

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

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

[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  linux-snapdragon: 4.4.0-1120.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1836877 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:10 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  linux-raspi2: 4.4.0-1116.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1836875 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:03 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1837040] [NEW] function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Disco ARM64

[Po-Hsu Lin]

Public bug reported:

Test failed with the disco master-next branch:

TAP version 13
selftests: ftrace: ftracetest

=== Ftrace unit tests ===
[1] Basic trace file check  [PASS]
[2] Basic test for tracers  [PASS]
[3] Basic trace clock test  [PASS]
[4] Basic event tracing check   [PASS]
[5] Change the ringbuffer size  [PASS]
[6] Snapshot and tracing setting[PASS]
[7] trace_pipe and trace_marker [PASS]
[8] Generic dynamic event - add/remove kprobe events[PASS]
[9] Generic dynamic event - add/remove synthetic events [PASS]
[10] Generic dynamic event - selective clear (compatibility)[PASS]
[11] Generic dynamic event - generic clear event[PASS]
[12] event tracing - enable/disable with event level files  [PASS]
[13] event tracing - restricts events based on pid  [PASS]
[14] event tracing - enable/disable with subsystem level files  [PASS]
[15] event tracing - enable/disable with top level files[PASS]
[16] Test trace_printk from module  [PASS]
[17] ftrace - function graph filters with stack tracer  [PASS]
[18] ftrace - function graph filters[PASS]
[19] ftrace - function glob filters [PASS]
[20] ftrace - function pid filters  [PASS]
[21] ftrace - stacktrace filter command [PASS]
[22] ftrace - function trace with cpumask   [PASS]
[23] ftrace - test for function event triggers  [PASS]
[24] ftrace - function trace on module  [PASS]
[25] ftrace - function profiling[PASS]
[26] ftrace - function profiler with function tracing   [PASS]
[27] ftrace - test reading of set_ftrace_filter [PASS]
[28] ftrace - Max stack tracer  [PASS]
[29] ftrace - test for function traceon/off triggers[FAIL]
[30] Test creation and deletion of trace instances while setting an event   
[PASS]
[31] Test creation and deletion of trace instances  [PASS]
[32] Kprobe dynamic event - adding and removing [PASS]
[33] Kprobe dynamic event - busy event check[PASS]
[34] Kprobe dynamic event with arguments[PASS]
[35] Kprobe event with comm arguments   [PASS]
[36] Kprobe event string type argument  [PASS]
[37] Kprobe event symbol argument   [PASS]
[38] Kprobe event argument syntax   [PASS]
[39] Kprobes event arguments with types [PASS]
[40] Kprobe event auto/manual naming[PASS]
[41] Kprobe dynamic event with function tracer  [PASS]
[42] Kprobe dynamic event - probing module  [PASS]
[43] Kretprobe dynamic event with arguments [PASS]
[44] Kretprobe dynamic event with maxactive [PASS]
[45] Register/unregister many kprobe events [PASS]
[46] Kprobe events - probe points   [PASS]
[47] Kprobe dynamic event - adding and removing [PASS]
[48] test for the preemptirqsoff tracer [UNSUPPORTED]
[49] Test wakeup tracer [PASS]
[50] Test wakeup RT tracer  [PASS]
[51] event trigger - test extended error support[PASS]
[52] event trigger - test field variable support[PASS]
[53] event trigger - test inter-event combined histogram trigger[PASS]
[54] event trigger - test multiple actions on hist trigger  [PASS]
[55] event trigger - test inter-event histogram trigger onmatch action  [PASS]
[56] event trigger - test inter-event histogram trigger onmatch-onmax action
[PASS]
[57] event trigger - test inter-event histogram trigger onmax action[PASS]
[58] event trigger - test synthetic event create remove [PASS]
[59] event trigger - test synthetic_events syntax parser[PASS]
[60] event trigger - test event enable/disable trigger  [PASS]
[61] event trigger - test trigger filter[PASS]
[62] event trigger - test histogram modifiers   [PASS]
[63] event trigger - test histogram trigger [PASS]
[64] event trigger - test multiple histogram triggers   [PASS]
[65] event trigger - test snapshot-trigger  [PASS]
[66] event trigger - test stacktrace-trigger[PASS]
[67] trace_marker trigger - test histogram trigger  [PASS]
[68] trace_marker trigger - test snapshot trigger   [PASS]
[69] trace_marker trigger - test histogram with synthetic event against kernel 
event[PASS]
[70] trace_marker trigger - test histogram with synthetic event [PASS]
[71] event trigger - test traceon/off trigger   [PASS]
[72] (instance)  Basic test for tracers [PASS]
[73] (instance)  Basic trace clock test [PASS]
[74] (instance)  Change the ringbuffer size [PASS]
[75] (instance)  Snapshot and tracing setting   [PASS]
[76] (instance)  trace_pipe and trace_marker[PASS]
[77] (instance)  event tracing - enable/disable with event level files  [PASS]
[78] (instance)  event tracing - restricts events based on pid  [PASS]
[79] (instance)  event tracing - enable/disable with subsystem level files  
[PASS]
[80] (instance)  ftrace - stacktrace filter command [PASS]
[81] (instance)  ftrace - test for function event triggers  [PASS]
[82] (instance)  ftrace - test for function traceon/off triggers[PASS]
[83] (instance)  event trigger - test event enable/disable trigg

[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  derivatives: bug 1836875 (pi2-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:03 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  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/1836876

Title:
  linux-raspi2: 4.4.0-1116.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1836875 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:03 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  derivatives: bug 1836877 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 17. July 2019 20:42 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 12:10 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  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/1836878

Title:
  linux-snapdragon: 4.4.0-1120.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1836877 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:10 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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: 1834954
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 17. July 2019 12:37 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 12:10 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
+ sync
  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/1834944

Title:
  linux-fips: 4.15.0-1012.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:10 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync
  variant: debs

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

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

[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: Confirmed => 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/1834944

Title:
  linux-fips: 4.15.0-1012.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:10 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync
  variant: debs

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

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

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:17 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on Disco ARM64

[Po-Hsu Lin]

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

** Tags added: 5.0 sru-20190701 ubuntu-kernel-selftests

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

Title:
  function traceon/off triggers in ftace from ubuntu_kernel_selftests
  failed on Disco ARM64

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

Bug description:
  Test failed with the disco master-next branch:

  TAP version 13
  selftests: ftrace: ftracetest
  
  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] Change the ringbuffer size[PASS]
  [6] Snapshot and tracing setting  [PASS]
  [7] trace_pipe and trace_marker   [PASS]
  [8] Generic dynamic event - add/remove kprobe events  [PASS]
  [9] Generic dynamic event - add/remove synthetic events   [PASS]
  [10] Generic dynamic event - selective clear (compatibility)  [PASS]
  [11] Generic dynamic event - generic clear event  [PASS]
  [12] event tracing - enable/disable with event level files[PASS]
  [13] event tracing - restricts events based on pid[PASS]
  [14] event tracing - enable/disable with subsystem level files[PASS]
  [15] event tracing - enable/disable with top level files  [PASS]
  [16] Test trace_printk from module[PASS]
  [17] ftrace - function graph filters with stack tracer[PASS]
  [18] ftrace - function graph filters  [PASS]
  [19] ftrace - function glob filters   [PASS]
  [20] ftrace - function pid filters[PASS]
  [21] ftrace - stacktrace filter command   [PASS]
  [22] ftrace - function trace with cpumask [PASS]
  [23] ftrace - test for function event triggers[PASS]
  [24] ftrace - function trace on module[PASS]
  [25] ftrace - function profiling  [PASS]
  [26] ftrace - function profiler with function tracing [PASS]
  [27] ftrace - test reading of set_ftrace_filter   [PASS]
  [28] ftrace - Max stack tracer[PASS]
  [29] ftrace - test for function traceon/off triggers  [FAIL]
  [30] Test creation and deletion of trace instances while setting an event 
[PASS]
  [31] Test creation and deletion of trace instances[PASS]
  [32] Kprobe dynamic event - adding and removing   [PASS]
  [33] Kprobe dynamic event - busy event check  [PASS]
  [34] Kprobe dynamic event with arguments  [PASS]
  [35] Kprobe event with comm arguments [PASS]
  [36] Kprobe event string type argument[PASS]
  [37] Kprobe event symbol argument [PASS]
  [38] Kprobe event argument syntax [PASS]
  [39] Kprobes event arguments with types   [PASS]
  [40] Kprobe event auto/manual naming  [PASS]
  [41] Kprobe dynamic event with function tracer[PASS]
  [42] Kprobe dynamic event - probing module[PASS]
  [43] Kretprobe dynamic event with arguments   [PASS]
  [44] Kretprobe dynamic event with maxactive   [PASS]
  [45] Register/unregister many kprobe events   [PASS]
  [46] Kprobe events - probe points [PASS]
  [47] Kprobe dynamic event - adding and removing   [PASS]
  [48] test for the preemptirqsoff tracer   [UNSUPPORTED]
  [49] Test wakeup tracer   [PASS]
  [50] Test wakeup RT tracer[PASS]
  [51] event trigger - test extended error support  [PASS]
  [52] event trigger - test field variable support  [PASS]
  [53] event trigger - test inter-event combined histogram trigger  [PASS]
  [54] event trigger - test multiple actions on hist trigger[PASS]
  [55] event trigger - test inter-event histogram trigger onmatch action
[PASS]
  [56] event trigger - test inter-event histogram trigger onmatch-onmax action  
[PASS]
  [57] event trigger - test inter-event histogram trigger onmax action  [PASS]
  [58] event trigger - test synthetic event create remove   [PASS]
  [59] event trigger - test synthetic_events syntax parser  [PASS]
  [60] event trigger - test event enable/disable trigger[PASS]
  [61] event trigger - test trigger filter  [PASS]
  [62] event trigger - test histogram modifiers [PASS]
  [63] event trigger - test histogram trigger   [PASS]
  [64] event trigger - test multiple histogram triggers [PASS]
  [65] event trigger - test snapshot-trigger[PASS]
  [66] event trigger - test stacktrace-trigger  [PASS]
  [67] trace_marker trigger - test histogram trigger[PASS]
  [68] trace_marker trigger - test snapshot trigger [PASS]
  [69] trace_marker trigger - test histogram with synthetic event against 
kernel event  [PASS]
  [70] trace_marker trigger - test histogram with synthetic event   [PASS]
  [71] event trigger - test traceon/off trigger [PASS]
  [72] (instance)  Basic test for tracers   [PASS]
 

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -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: 1834954
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 18. July 2019 09:08 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 18. July 2019 12:17 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  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/1836925

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:17 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837040] 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/1837040

Title:
  function traceon/off triggers in ftace from ubuntu_kernel_selftests
  failed on Disco ARM64

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

Bug description:
  Test failed with the disco master-next branch:

  TAP version 13
  selftests: ftrace: ftracetest
  
  === Ftrace unit tests ===
  [1] Basic trace file check[PASS]
  [2] Basic test for tracers[PASS]
  [3] Basic trace clock test[PASS]
  [4] Basic event tracing check [PASS]
  [5] Change the ringbuffer size[PASS]
  [6] Snapshot and tracing setting  [PASS]
  [7] trace_pipe and trace_marker   [PASS]
  [8] Generic dynamic event - add/remove kprobe events  [PASS]
  [9] Generic dynamic event - add/remove synthetic events   [PASS]
  [10] Generic dynamic event - selective clear (compatibility)  [PASS]
  [11] Generic dynamic event - generic clear event  [PASS]
  [12] event tracing - enable/disable with event level files[PASS]
  [13] event tracing - restricts events based on pid[PASS]
  [14] event tracing - enable/disable with subsystem level files[PASS]
  [15] event tracing - enable/disable with top level files  [PASS]
  [16] Test trace_printk from module[PASS]
  [17] ftrace - function graph filters with stack tracer[PASS]
  [18] ftrace - function graph filters  [PASS]
  [19] ftrace - function glob filters   [PASS]
  [20] ftrace - function pid filters[PASS]
  [21] ftrace - stacktrace filter command   [PASS]
  [22] ftrace - function trace with cpumask [PASS]
  [23] ftrace - test for function event triggers[PASS]
  [24] ftrace - function trace on module[PASS]
  [25] ftrace - function profiling  [PASS]
  [26] ftrace - function profiler with function tracing [PASS]
  [27] ftrace - test reading of set_ftrace_filter   [PASS]
  [28] ftrace - Max stack tracer[PASS]
  [29] ftrace - test for function traceon/off triggers  [FAIL]
  [30] Test creation and deletion of trace instances while setting an event 
[PASS]
  [31] Test creation and deletion of trace instances[PASS]
  [32] Kprobe dynamic event - adding and removing   [PASS]
  [33] Kprobe dynamic event - busy event check  [PASS]
  [34] Kprobe dynamic event with arguments  [PASS]
  [35] Kprobe event with comm arguments [PASS]
  [36] Kprobe event string type argument[PASS]
  [37] Kprobe event symbol argument [PASS]
  [38] Kprobe event argument syntax [PASS]
  [39] Kprobes event arguments with types   [PASS]
  [40] Kprobe event auto/manual naming  [PASS]
  [41] Kprobe dynamic event with function tracer[PASS]
  [42] Kprobe dynamic event - probing module[PASS]
  [43] Kretprobe dynamic event with arguments   [PASS]
  [44] Kretprobe dynamic event with maxactive   [PASS]
  [45] Register/unregister many kprobe events   [PASS]
  [46] Kprobe events - probe points [PASS]
  [47] Kprobe dynamic event - adding and removing   [PASS]
  [48] test for the preemptirqsoff tracer   [UNSUPPORTED]
  [49] Test wakeup tracer   [PASS]
  [50] Test wakeup RT tracer[PASS]
  [51] event trigger - test extended error support  [PASS]
  [52] event trigger - test field variable support  [PASS]
  [53] event trigger - test inter-event combined histogram trigger  [PASS]
  [54] event trigger - test multiple actions on hist trigger[PASS]
  [55] event trigger - test inter-event histogram trigger onmatch action
[PASS]
  [56] event trigger - test inter-event histogram trigger onmatch-onmax action  
[PASS]
  [57] event trigger - test inter-event histogram trigger onmax action  [PASS]
  [58] event trigger - test synthetic event create remove   [PASS]
  [59] event trigger - test synthetic_events syntax parser  [PASS]
  [60] event trigger - test event enable/disable trigger[PASS]
  [61] event trigger - test trigger filter  [PASS]
  [62] event trigger - test histogram modifiers [PASS]
  [63] event trigger - test histogram trigger   [PASS]
  [64] event trigger - test multiple histogram triggers [PASS]
  [65] event trigger - test snapshot-trigger[PASS]
  [66] event trigger - test stacktrace-trigger  [PASS]
  [67] trace_marker trigger - test histogram trigger[PASS]
  [68] trace_marker trigger - test snapshot trigger [PASS]
  [69] trace_marker trigger - test histogram with synthetic event against 
kernel event  [PASS]
  [70] trace_marker trigger - test histogram with synthetic event   [PASS]
  [71] event trigger - test traceon/off trigger [PASS]
  [72] (instance)  Basic test f

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:17 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  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/1836925

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 12:17 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  derivatives: bug 1834924 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
- phase: Testing
- phase-changed: Thursday, 11. July 2019 13:10 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1834925

Title:
  linux-snapdragon: 4.15.0-1058.64 -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:
  Confirmed
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:
  New
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:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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

  derivatives: bug 1834924 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1834925/+subscriptions

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

[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open

[Claudio Matsuoka]

Thanks. I tested the proposed kernel and it does not prevent the crash,
which still occurs under the same circumstances when cryptsetup open
runs. It's possible, however, that the patch decreases the likehood of a
crash. In a very un-scientific test the latest patched kernel crashed in
3 out of 10 attempts, while the stock unpatched kernel crashed in 6 out
of 10 attempts.

To mitigate the issue, with both the original and patched kernels, I'm
manually loading the dm-crypt module before running cryptsetup
luksFormat. Note that manually loading the module between cryptsetup
luksFormat and cryptsetup open does not prevent the crash.

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

Title:
  4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open

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

Bug description:
  This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc
  version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun
  24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc-
  kernel_240.snap

  Version signature: 4.15.0-54.58-generic 4.15.18

  Issue is non-deterministic, and happens in roughly 20% of the
  attempts.

  Running on: qemu-kvm, command line:  kvm \
    -bios /usr/share/ovmf/OVMF.fd \
    -smp 2 -m 512 -netdev 
user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \
    -device virtio-net-pci,netdev=mynet0 \
    -drive file=pc.img,format=raw

  Commands that caused the problem:
  cryptsetup -q --type luks2 --key-file  luksFormat /dev/sda4
  LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file  open 
/dev/sda4 crypt-data

  Notes:
  - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for 
more information on the no-udev workaround.
  - The commands are scripted. Also tried to add a 200ms and 1s interval before 
opening the device.

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

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

[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat

[Guilherme G. Piccoli]

SRU sent to kernel-team mailing list: https://lists.ubuntu.com/archives
/kernel-team/2019-July/102357.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/1824981

Title:
  cifs set_oplock buffer overflow in strcat

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * We got reports of a kernel crash in cifs module with the following
  signature:

  detected buffer overflow in strcat
  kernel BUG at <...>/lib/string.c:1052!
  invalid opcode:  [#1] SMP PTI
  RIP: 0010:fortify_panic+0x13/0x1f
  Call Trace:
   smb21_set_oplock_level+0xde/0x190 [cifs]
   smb3_set_oplock_level+0x22/0x90 [cifs]
   smb2_set_fid+0x76/0xb0 [cifs]
   cifs_new_fileinfo+0x268/0x3c0 [cifs]
   ? smb2_get_lease_key+0x40/0x40 [cifs]
   ? cifs_new_fileinfo+0x268/0x3c0 [cifs]
   cifs_open+0x57c/0x8d0 [cifs]
   do_dentry_open+0x1fe/0x320
  [...]

  * By analyzing the code of smb21_set_oplock_level(), we've noticed the
  only way fortify function strcat() would get overflow was if the value
  of cinode->oplock got corrupted in a another thread leading to a
  buffer write bigger then buffer size. In this function, the 'message'
  buffer writes are governed by cinode->oplock, so only a different
  thread cleaning the oplock value would lead to 'message' overflow.

  * By the same time we worked this analysis, a fix was proposed
  upstream for this issue  in the form of commit 6a54b2e002c9 ("cifs:
  fix strcat buffer overflow and reduce raciness in
  smb21_set_oplock_level()"), by the same reporter of this LP. The fix
  is simple and directly addresses this problem, so we hereby request
  its SRU into Bionic kernel - it's already present in linux stable
  branches.

  [Test case]

  * Unfortunately we cannot reproduce the issue. The patch proposed here was
  validated by us with xfstests (instructions followed from
  https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.

  * Using xfstest with the exclusions proposed in the link above we
  managed to get the same results as a non-patched kernel, i.e., the
  same tests failed in both kernels, we didn't get worse results with
  the patch. Fio also didn't show noticeable performance regression with
  the patch.

  [Regression potential]

  * The patch was validated by the cifs filesystem maintainers and by
  the aforementioned tests; also, the scope is restricted to cifs only
  so the likelihood of regressions is considered low. The commit
  introduces no functional changes and the only affected path was just
  refactored in a way to prevent overflow and reduce race potential.

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

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

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

[Alberto Milone]

I can apply the change depending on the availability of the new nvme_*
functions, so that kernels which don't include the two commits will not
be affected.

I am going to notify NVIDIA too.

-- 
You 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:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  New

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 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

[Alberto Milone]

Actually, the calls are not exposed, so, maybe we should rely on the
kernel version instead.

-- 
You 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:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  New

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 1836880] Re: linux: 4.4.0-156.183 -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
  
  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
-   promote-to-proposed: Pending -- packages copied to Proposed signed:building
+   promote-to-proposed: Pending -- packages copied to Proposed signed:queued
  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/1836880

Title:
  linux: 4.4.0-156.183 -proposed tracker

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

  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
promote-to-proposed: Pending -- packages copied to Proposed signed:queued
  variant: debs

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

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

[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

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

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

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

** 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
  
  derivatives: bug 1836877 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
- phase: Promote to Proposed
- phase-changed: Thursday, 18. July 2019 12:10 UTC
+ phase: Testing
+ phase-changed: Thursday, 18. July 2019 13:41 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1836878

Title:
  linux-snapdragon: 4.4.0-1120.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1836877 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Testing
  phase-changed: Thursday, 18. July 2019 13:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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/1836878/+subscriptions

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

[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

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

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

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

** 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
  
  derivatives: bug 1836875 (pi2-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
- phase: Promote to Proposed
- phase-changed: Thursday, 18. July 2019 12:03 UTC
+ phase: Testing
+ phase-changed: Thursday, 18. July 2019 13:40 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1836876

Title:
  linux-raspi2: 4.4.0-1116.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1836875 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Testing
  phase-changed: Thursday, 18. July 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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/1836876/+subscriptions

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

[Kernel-packages] [Bug 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

** 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: 1834954
- phase: Promote to Proposed
- phase-changed: Thursday, 18. July 2019 12:10 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 13:40 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1834944

Title:
  linux-fips: 4.15.0-1012.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-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/1834944/+subscriptions

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

[Kernel-packages] [Bug 1836899] [NEW] Wowlan capability on rtl2783be driver doesn't work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have an all-in-one HP pc with rtl8723be wireless wifi card.
I'm trying to enable wowlan capability on the card, but I can't.

This is my system:

supervisore@Aula16:~$ uname -a
Linux Aula16 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
supervisore@Aula16:~$ 
supervisore@Aula16:~$ sudo lshw -class network
  *-network 
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: enp2s0
   version: 10
   serial: b4:b6:86:db:b2:8e
   size: 10Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8168g-3_0.0.1 04/23/13 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
   resources: irq:18 ioport:e000(size=256) memory:81304000-81304fff 
memory:8130-81303fff
  *-network
   description: Wireless interface
   product: RTL8723BE PCIe Wireless Network Adapter
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlp3s0
   version: 00
   serial: 50:5b:c2:a8:ab:eb
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=rtl8723be 
driverversion=4.15.0-54-generic firmware=N/A ip=192.168.3.116 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:19 ioport:d000(size=256) memory:8120-81203fff
supervisore@Aula16:~$ 

Reading on the Realtek site https://www.realtek.com/en/products
/communications-network-ics/item/rtl8723be I see that the wifi card has
the wowlan capability, but when I try to enable it I receive

supervisore@Aula16:~$ sudo iw phy0 wowlan enable magic-packet
command failed: Operation not supported (-95)

I really need to enable the wowlan feature on the card, how?

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


** Tags: bot-comment
-- 
Wowlan capability on rtl2783be driver doesn't work
https://bugs.launchpad.net/bugs/1836899
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware 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 1837036] Re: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386

[semreh]

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

According to this comment (
https://www.phoronix.com/forums/forum/software/general-linux-open-
source/1113503-linux-5-2-1-released-for-riding-the-latest-stable-
kernel?p=1113668#post1113668 )at Phoronix, the underlying cause is:

"Ubuntu is using -fcf-protection by default now and that isn't
compatible with -mindirect-branch that the kernel uses for retpolines. "

Bug 1830961 appears to be an earllier report, so this is a duplicate of
that bug, as is bug 1836373


** This bug has been marked a duplicate of bug 1830961
   Kernels & kernel drivers fail to build with gcc-9 [error: 
‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

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

Title:
  Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2
  on AMD64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2
  on AMD64 and i386 are failing to build.

  Build logs at (for example):

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386

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

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

[Kernel-packages] [Bug 1836899] Re: Wowlan capability on rtl2783be driver doesn't work

[smurf]

** Package changed: ubuntu => linux-firmware (Ubuntu)

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

Title:
  Wowlan capability on rtl2783be driver doesn't work

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have an all-in-one HP pc with rtl8723be wireless wifi card.
  I'm trying to enable wowlan capability on the card, but I can't.

  This is my system:

  supervisore@Aula16:~$ uname -a
  Linux Aula16 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  supervisore@Aula16:~$ 
  supervisore@Aula16:~$ sudo lshw -class network
*-network 
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 10
 serial: b4:b6:86:db:b2:8e
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8168g-3_0.0.1 04/23/13 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:18 ioport:e000(size=256) memory:81304000-81304fff 
memory:8130-81303fff
*-network
 description: Wireless interface
 product: RTL8723BE PCIe Wireless Network Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 00
 serial: 50:5b:c2:a8:ab:eb
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=rtl8723be 
driverversion=4.15.0-54-generic firmware=N/A ip=192.168.3.116 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:19 ioport:d000(size=256) memory:8120-81203fff
  supervisore@Aula16:~$ 

  Reading on the Realtek site https://www.realtek.com/en/products
  /communications-network-ics/item/rtl8723be I see that the wifi card
  has the wowlan capability, but when I try to enable it I receive

  supervisore@Aula16:~$ sudo iw phy0 wowlan enable magic-packet
  command failed: Operation not supported (-95)

  I really need to enable the wowlan feature on the card, how?

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

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

[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.173.9

---
linux-firmware (1.173.9) bionic; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

  * Bluetooth: hci0: request failed to create LE connection: status 0x0c
(Intel 9260) (LP: #1835449)
- linux-firmware: Update firmware file for Intel Bluetooth, 9260

  * Update firmware in nic-firmware udeb for 5.0 hwe kernel (LP: #1836372)
- Update nic-firmware.lst for 5.0 hwe kernel

 -- Seth Forshee   Fri, 12 Jul 2019 09:55:49
-0500

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

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

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

[Kernel-packages] [Bug 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.173.9

---
linux-firmware (1.173.9) bionic; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

  * Bluetooth: hci0: request failed to create LE connection: status 0x0c
(Intel 9260) (LP: #1835449)
- linux-firmware: Update firmware file for Intel Bluetooth, 9260

  * Update firmware in nic-firmware udeb for 5.0 hwe kernel (LP: #1836372)
- Update nic-firmware.lst for 5.0 hwe kernel

 -- Seth Forshee   Fri, 12 Jul 2019 09:55:49
-0500

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9260)

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID
  devices.

  [Fix]
  Bluetooth FW Build REL0329 or newer is known to have fixed this problem
  on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes
  a firmware backport from upstream commit
  c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix
  conflicts in the WHENCE file.

  [Test Case]
  Verified on hardware platforms with Intel Wireless AC 9260 installed,
  e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel
  and power off the device completely to trigger firmware reload at the
  next boot.

  [Regression Risk]
  Low. Tried following kernels with REL0329 firmware blobs:

* 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.8.0-58-generic: Xenial, even doesn't boot to console
* 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.13.0-45-generic: Xenial
* 4.15.0-54-generic: Xenial, Bionic
* 4.15.0-1043-oem: Xenial, Bionic

  For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't
  work even with current firmware blobs shipped in Xenial's linux-firmware
  REL0186. So overall, these updated blobs are only loaded by hardware
  requires them, and they doesn't bring harm to known working
  configurations.

   Original Bug Description 

  Same problem exactly as encountered with Intel 9560 is also happening
  with Intel 9260.

  Update to linux-firmware 1.173.8 did not fix the problem.

  Everything is working fine when using 4.15 kernel, but not for 4.18+
  5.0+.

  Reference problem:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737

  You-Sheng Yang advised to do this by email and it fixed my issue, so I
  think the 9260 driver would need to be updated in the bionic branch
  (it seems to be updated in newer branches).

  --
  Basically you should try copy the latest firmware (ibt-*) under
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
  , power off the device completely and power on, then have a check on
  bluetooth pairing.
  --

  Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27
  04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  OS: Linux Mint 19.1 Tessa x86_64
  Host: 81JB Lenovo ideapad 730S-13IWL
  Wifi/Bluetooth card is Intel 9260

  @:/etc$ dmesg | egrep -i 'blue|firm'
  [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.379392] [Firmware Bug]: Invalid critical threshold (0)
  [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [6.337749] Bluetooth: Core ver 2.22
  [6.337767] Bluetooth: HCI device and connection manager initialized
  [6.337770] Bluetooth: HCI socket layer initialized
  [6.337773] Bluetooth: L2CAP socket layer initialized
  [6.33] Bluetooth: SCO socket layer initialized
  [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.309938] Bluetooth: BNEP filters: protocol multicast
  [7.309943] Bluetooth: BNEP socket layer initialized
  [   17.197268] Bluetooth: RFCOMM TTY layer initialized
  [   17.197275] Bluetooth: RFCOMM socket layer initialized
  [   17.197284] Bluetooth: RFCOMM ver 1.11
  [  104.453159] Bluetooth: hci0: request failed to create LE connection: 

[Kernel-packages] [Bug 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.157.22

---
linux-firmware (1.157.22) xenial; urgency=medium

  * Bluetooth: hci0: request failed to create LE connection: status 0x0c
(Intel 9260) (LP: #1835449)
- linux-firmware: Update firmware file for Intel Bluetooth, 9260

 -- Seth Forshee   Fri, 12 Jul 2019 07:22:20
-0500

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9260)

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID
  devices.

  [Fix]
  Bluetooth FW Build REL0329 or newer is known to have fixed this problem
  on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes
  a firmware backport from upstream commit
  c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix
  conflicts in the WHENCE file.

  [Test Case]
  Verified on hardware platforms with Intel Wireless AC 9260 installed,
  e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel
  and power off the device completely to trigger firmware reload at the
  next boot.

  [Regression Risk]
  Low. Tried following kernels with REL0329 firmware blobs:

* 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.8.0-58-generic: Xenial, even doesn't boot to console
* 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.13.0-45-generic: Xenial
* 4.15.0-54-generic: Xenial, Bionic
* 4.15.0-1043-oem: Xenial, Bionic

  For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't
  work even with current firmware blobs shipped in Xenial's linux-firmware
  REL0186. So overall, these updated blobs are only loaded by hardware
  requires them, and they doesn't bring harm to known working
  configurations.

   Original Bug Description 

  Same problem exactly as encountered with Intel 9560 is also happening
  with Intel 9260.

  Update to linux-firmware 1.173.8 did not fix the problem.

  Everything is working fine when using 4.15 kernel, but not for 4.18+
  5.0+.

  Reference problem:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737

  You-Sheng Yang advised to do this by email and it fixed my issue, so I
  think the 9260 driver would need to be updated in the bionic branch
  (it seems to be updated in newer branches).

  --
  Basically you should try copy the latest firmware (ibt-*) under
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
  , power off the device completely and power on, then have a check on
  bluetooth pairing.
  --

  Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27
  04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  OS: Linux Mint 19.1 Tessa x86_64
  Host: 81JB Lenovo ideapad 730S-13IWL
  Wifi/Bluetooth card is Intel 9260

  @:/etc$ dmesg | egrep -i 'blue|firm'
  [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.379392] [Firmware Bug]: Invalid critical threshold (0)
  [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [6.337749] Bluetooth: Core ver 2.22
  [6.337767] Bluetooth: HCI device and connection manager initialized
  [6.337770] Bluetooth: HCI socket layer initialized
  [6.337773] Bluetooth: L2CAP socket layer initialized
  [6.33] Bluetooth: SCO socket layer initialized
  [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.309938] Bluetooth: BNEP filters: protocol multicast
  [7.309943] Bluetooth: BNEP socket layer initialized
  [   17.197268] Bluetooth: RFCOMM TTY layer initialized
  [   17.197275] Bluetooth: RFCOMM socket layer initialized
  [   17.197284] Bluetooth: RFCOMM ver 1.11
  [  104.453159] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.509148] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.551340] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.589338] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.623323] Bluetooth: hci0: reque

[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.173.9

---
linux-firmware (1.173.9) bionic; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

  * Bluetooth: hci0: request failed to create LE connection: status 0x0c
(Intel 9260) (LP: #1835449)
- linux-firmware: Update firmware file for Intel Bluetooth, 9260

  * Update firmware in nic-firmware udeb for 5.0 hwe kernel (LP: #1836372)
- Update nic-firmware.lst for 5.0 hwe kernel

 -- Seth Forshee   Fri, 12 Jul 2019 09:55:49
-0500

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

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

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

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

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

[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.178.3

---
linux-firmware (1.178.3) disco; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

 -- Seth Forshee   Fri, 12 Jul 2019 07:43:03
-0500

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

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

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

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

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

[Kernel-packages] [Bug 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.178.3

---
linux-firmware (1.178.3) disco; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

 -- Seth Forshee   Fri, 12 Jul 2019 07:43:03
-0500

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

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1834464

Title:
  Missing bluetooth firmware for Intel Wireless-AC 9462/9560

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

Bug description:
  [Impact]
  Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to
  be enabled.

  [Fix]
  Backport newly released firmware blobs from linux-firmware. This will
  also requires minor change to the WHENCE file to resolve cherry-pick
  conflicts. B/C/D would requires this explicitly and Eoan should be
  rebased onto linux-firmware master branch HEAD as usual.

  [Test Case]
  Verified with hardware platforms with corresponding devices. Completely
  power off and power on to trigger firmware reload, check from dmesg to
  see if Bluetooth firmware has been correctly loaded.

  [Regression Risk]
  Low. This adds new binary firmware blobs that are only loaded by
  targeting hardware.

  == original bug description ==

  On systems with Intel Wireless-AC 9462/9560 cards, following failed-
  to-load-firmware kernel messages found:

    bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi
  failed with error -2

  See also Bug #1833065 for wireless firmware & driver fix.

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

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

[Kernel-packages] [Bug 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.178.3

---
linux-firmware (1.178.3) disco; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

 -- Seth Forshee   Fri, 12 Jul 2019 07:43:03
-0500

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Missing bluetooth firmware for Intel Wireless-AC 9462/9560

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

Bug description:
  [Impact]
  Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to
  be enabled.

  [Fix]
  Backport newly released firmware blobs from linux-firmware. This will
  also requires minor change to the WHENCE file to resolve cherry-pick
  conflicts. B/C/D would requires this explicitly and Eoan should be
  rebased onto linux-firmware master branch HEAD as usual.

  [Test Case]
  Verified with hardware platforms with corresponding devices. Completely
  power off and power on to trigger firmware reload, check from dmesg to
  see if Bluetooth firmware has been correctly loaded.

  [Regression Risk]
  Low. This adds new binary firmware blobs that are only loaded by
  targeting hardware.

  == original bug description ==

  On systems with Intel Wireless-AC 9462/9560 cards, following failed-
  to-load-firmware kernel messages found:

    bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi
  failed with error -2

  See also Bug #1833065 for wireless firmware & driver fix.

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

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

[Kernel-packages] [Bug 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.173.9

---
linux-firmware (1.173.9) bionic; urgency=medium

  * Missing bluetooth firmware for Intel Wireless-AC 9462/9560 (LP: #1834464)
- linux-firmware: Add firmware file for Intel Bluetooth AX201

  * [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
(LP: #1835345)
- linux-firmware: Update firmware file for Intel Bluetooth 22161
- linux-firmware: Update firmware file for Intel Bluetooth 22161

  * Bluetooth: hci0: request failed to create LE connection: status 0x0c
(Intel 9260) (LP: #1835449)
- linux-firmware: Update firmware file for Intel Bluetooth, 9260

  * Update firmware in nic-firmware udeb for 5.0 hwe kernel (LP: #1836372)
- Update nic-firmware.lst for 5.0 hwe kernel

 -- Seth Forshee   Fri, 12 Jul 2019 09:55:49
-0500

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

Title:
  Missing bluetooth firmware for Intel Wireless-AC 9462/9560

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

Bug description:
  [Impact]
  Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to
  be enabled.

  [Fix]
  Backport newly released firmware blobs from linux-firmware. This will
  also requires minor change to the WHENCE file to resolve cherry-pick
  conflicts. B/C/D would requires this explicitly and Eoan should be
  rebased onto linux-firmware master branch HEAD as usual.

  [Test Case]
  Verified with hardware platforms with corresponding devices. Completely
  power off and power on to trigger firmware reload, check from dmesg to
  see if Bluetooth firmware has been correctly loaded.

  [Regression Risk]
  Low. This adds new binary firmware blobs that are only loaded by
  targeting hardware.

  == original bug description ==

  On systems with Intel Wireless-AC 9462/9560 cards, following failed-
  to-load-firmware kernel messages found:

    bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi
  failed with error -2

  See also Bug #1833065 for wireless firmware & driver fix.

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

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

[Kernel-packages] [Bug 1836925] Re: linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

** 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: 1834954
- phase: Promote to Proposed
- phase-changed: Thursday, 18. July 2019 12:17 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 14:04 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1836925

Title:
  linux-ibm-gt: 4.15.0-1028.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux 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: 1834954
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 14:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-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/1836925/+subscriptions

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

[Kernel-packages] [Bug 1836491] Re: Complete lock-up

[Kai-Heng Feng]

Would it be possible to find out the last kernel version that works and
the first kernel version that causes the issue?

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

Title:
  Complete lock-up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This kernel has caused my video system to completely freeze. A hard restart 
is required to recover, but it happens each time. I have reverted to prior 
kernel.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   lmcor  2748 F...m pulseaudio
   /dev/snd/controlC1:  lmcor  2748 F pulseaudio
   /dev/snd/controlC0:  lmcor  2748 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=bf754a96-f70b-4964-bdbb-b7ab12e42018
  InstallationDate: Installed on 2018-09-30 (287 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171127
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=7663b459-8677-4afe-85fb-12424af45024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-52.56~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-52-generic N/A
   linux-backports-modules-4.15.0-52-generic  N/A
   linux-firmware 1.157.21
  Tags:  sylvia
  Uname: Linux 4.15.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3803
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1834954

Title:
  linux: 4.15.0-55.60 -proposed tracker

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

  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1834954/+subscriptions

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker

[Kleber Sacilotto de Souza]

Setting manually the status of 'automated-testing' to 'Fix Released' due
to a wrong 'MISS' status for the network-manager tests caused by the
package update being aborted on the archive.

https://people.canonical.com/~kernel/status/adt-matrix/bionic-linux-
meta.html

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => 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/1834954

Title:
  linux: 4.15.0-55.60 -proposed tracker

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

  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

[Canonical Certification Team]

Kernel deb testing completes, no regressions found. Ready for Updates.
Results here: https://trello.com/c/BRWJSlUb/102-disco-linux-
image-500-21-generic-500-2122

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 5.0.0-21.22 -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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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

  backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Wednesday, 17. July 2019 14:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-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/1834902/+subscriptions

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -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
  
  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Friday, 12. July 2019 17:33 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1834954

Title:
  linux: 4.15.0-55.60 -proposed tracker

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

  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834930 
(linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 
(linux-kvm), bug 1834943 (linux-oracle), bug 1834944 (linux-fips), bug 1836172 
(linux-oem), bug 1836925 (linux-ibm-gt)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -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
  
  backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Wednesday, 17. July 2019 14:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
regression-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1834902

Title:
  linux: 5.0.0-21.22 -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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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

  backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Wednesday, 17. July 2019 14:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-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/1834902/+subscriptions

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

[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -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
  
  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
-   promote-to-proposed: Pending -- packages copied to Proposed signed:queued
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  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/1836880

Title:
  linux: 4.4.0-156.183 -proposed tracker

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

  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Thursday, 18. July 2019 11:55 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** 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
  
  derivatives: bug 1836201 (gke-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834891
- phase: Testing
- phase-changed: Tuesday, 16. July 2019 16:53 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 15:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- Nvidia objects not found -- 
current-driver-5.0.0-1011-gke-d1809-0-amd64
regression-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 in Ubuntu.
https://bugs.launchpad.net/bugs/1836202

Title:
  bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  derivatives: bug 1836201 (gke-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834891
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 15:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- Nvidia objects not found -- 
current-driver-5.0.0-1011-gke-d1809-0-amd64
regression-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/1836202/+subscriptions

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

[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** 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
  
  derivatives: bug 1834885 (azure-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1835438
- phase: Testing
- phase-changed: Wednesday, 10. July 2019 16:18 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 15:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1835436

Title:
  linux-azure: 4.18.0-1025.27~18.04.1 -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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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

  derivatives: bug 1834885 (azure-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1835438
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 15:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836064] Re: glibc needs an update for linux-5.2 kernel headers (alpha)

[Brian Murray]

** Tags removed: rls-ee-incoming

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

Title:
  glibc needs an update for linux-5.2 kernel headers (alpha)

Status in glibc package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in glibc source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Fix Released

Bug description:
  as seen in 
  
https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410

  the c-t-b-ports package ftbfs:

  /bin/bash ../scripts/move-if-change 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h
  touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp
  if test -r 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \
  else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi
  In file included from :1:
  ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" 
redefined [-Werror]
   #define __NR_osf_shmat  209
   
  In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24,
   from ../sysdeps/unix/sysdep.h:20,
   from ../sysdeps/unix/alpha/sysdep.h:19,
   from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29,
   from :1:
  /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the 
location of the previous definition
   #define __NR_osf_shmat __NR_shmat
   
  cc1: all warnings being treated as errors
  Traceback (most recent call last):
File "../scripts/gen-as-const.py", line 120, in 
  main()
File "../scripts/gen-as-const.py", line 116, in main
  consts = glibcextract.compute_c_consts(sym_data, args.cc)
File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in 
compute_c_consts
  subprocess.check_call(cmd, shell=True)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie 
-fno-PIE -std=gnu11 -fgnu89-inline  -pipe -O2 -g -Wall -Wwrite-strings -Wundef 
-Werror -fmerge-all-constants -frounding-math -fno-stack-protector 
-Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 
-mieee -mfp-rounding-mode=d-ftls-model=initial-exec   -U_FORTIFY_SOURCE 
-isystem /<>/glibc-2.29/debian/include  -I../include 
-I/<>/glibc-2.29/build-tree/alpha-libc/csu  
-I/<>/glibc-2.29/build-tree/alpha-libc  
-I../sysdeps/unix/sysv/linux/alpha/alpha  
-I../sysdeps/unix/sysv/linux/alpha/fpu  -I../sysdeps/alpha/fpu  
-I../sysdeps/unix/sysv/linux/alpha  -I../sysdeps/alpha/nptl  
-I../sysdeps/unix/sysv/linux/wordsize-64  -I../sysdeps/ieee754/ldbl-64-128  
-I../sysdeps/ieee754/ldbl-opt  -I../sysdeps/unix/sysv/linux/include 
-I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  
-I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  
-I../sysdeps/unix/alpha  -I../sysdeps/unix  -I../sysdeps/posix  
-I../sysdeps/alpha  -I../sysdeps/wordsize-64  -I../sysdeps/ieee754/ldbl-128  
-I../sysdeps/ieee754/dbl-64/wordsize-64  -I../sysdeps/ieee754/dbl-64  
-I../sysdeps/ieee754/flt-32  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. 
-I../libio -I. -nostdinc -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include
 -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed
 -isystem /<>/glibc-2.29/debian/include  -D_LIBC_REENTRANT 
-include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h 
-DMODULE_NAME=libc -include ../include/libc-symbols.h   
-DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT  
-MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o 
/tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero 
exit status 1.
  make[4]: *** [../Makerules:271: 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1
  make[4]: Leaving directory '/<>/glibc-2.29/csu'
  make[3]: *** [Makefile:275: csu/subdir_lib] Error 2

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

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

[Kernel-packages] [Bug 1836064] Re: glibc needs an update for linux-5.2 kernel headers (alpha)

[Steve Langasek]

** Tags added: rls-ee-notfixing

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

Title:
  glibc needs an update for linux-5.2 kernel headers (alpha)

Status in glibc package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in glibc source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Fix Released

Bug description:
  as seen in 
  
https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410

  the c-t-b-ports package ftbfs:

  /bin/bash ../scripts/move-if-change 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h
  touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp
  if test -r 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \
  else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi
  In file included from :1:
  ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" 
redefined [-Werror]
   #define __NR_osf_shmat  209
   
  In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24,
   from ../sysdeps/unix/sysdep.h:20,
   from ../sysdeps/unix/alpha/sysdep.h:19,
   from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29,
   from :1:
  /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the 
location of the previous definition
   #define __NR_osf_shmat __NR_shmat
   
  cc1: all warnings being treated as errors
  Traceback (most recent call last):
File "../scripts/gen-as-const.py", line 120, in 
  main()
File "../scripts/gen-as-const.py", line 116, in main
  consts = glibcextract.compute_c_consts(sym_data, args.cc)
File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in 
compute_c_consts
  subprocess.check_call(cmd, shell=True)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie 
-fno-PIE -std=gnu11 -fgnu89-inline  -pipe -O2 -g -Wall -Wwrite-strings -Wundef 
-Werror -fmerge-all-constants -frounding-math -fno-stack-protector 
-Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 
-mieee -mfp-rounding-mode=d-ftls-model=initial-exec   -U_FORTIFY_SOURCE 
-isystem /<>/glibc-2.29/debian/include  -I../include 
-I/<>/glibc-2.29/build-tree/alpha-libc/csu  
-I/<>/glibc-2.29/build-tree/alpha-libc  
-I../sysdeps/unix/sysv/linux/alpha/alpha  
-I../sysdeps/unix/sysv/linux/alpha/fpu  -I../sysdeps/alpha/fpu  
-I../sysdeps/unix/sysv/linux/alpha  -I../sysdeps/alpha/nptl  
-I../sysdeps/unix/sysv/linux/wordsize-64  -I../sysdeps/ieee754/ldbl-64-128  
-I../sysdeps/ieee754/ldbl-opt  -I../sysdeps/unix/sysv/linux/include 
-I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  
-I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  
-I../sysdeps/unix/alpha  -I../sysdeps/unix  -I../sysdeps/posix  
-I../sysdeps/alpha  -I../sysdeps/wordsize-64  -I../sysdeps/ieee754/ldbl-128  
-I../sysdeps/ieee754/dbl-64/wordsize-64  -I../sysdeps/ieee754/dbl-64  
-I../sysdeps/ieee754/flt-32  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. 
-I../libio -I. -nostdinc -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include
 -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed
 -isystem /<>/glibc-2.29/debian/include  -D_LIBC_REENTRANT 
-include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h 
-DMODULE_NAME=libc -include ../include/libc-symbols.h   
-DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT  
-MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o 
/tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero 
exit status 1.
  make[4]: *** [../Makerules:271: 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1
  make[4]: Leaving directory '/<>/glibc-2.29/csu'
  make[3]: *** [Makefile:275: csu/subdir_lib] Error 2

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

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

[Kernel-packages] [Bug 1837073] [NEW] linux 5.2.0-8.9 disabled backlight on s390x.

[Gianfranco Costamagna]

Public bug reported:

Looks like ddcci-driver-linux started to fail on s390x with the switch
from kernel 5.0.0-21-generic to 5.2.0-8-generic

http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x


According to changelog and diff:
- [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x

from Seth Forshee.

According to the build log of ddci backlight

rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory
Makefile:227: = WARNING 
Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
Makefile:230: ==
Makefile:227: = WARNING 
Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
Makefile:230: ==
ERROR: "devm_backlight_device_register" 
[/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined!
make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1
make[2]: *** [Makefile:1628: modules] Error 2
make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: Confirmed

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

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

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

Title:
  linux 5.2.0-8.9 disabled backlight on s390x.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Looks like ddcci-driver-linux started to fail on s390x with the switch
  from kernel 5.0.0-21-generic to 5.2.0-8-generic

  http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x


  According to changelog and diff:
  - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x

  from Seth Forshee.

  According to the build log of ddci backlight

  rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or 
directory
  Makefile:227: = WARNING 
  Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
  Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
  Makefile:230: ==
  Makefile:227: = WARNING 
  Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
  Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
  Makefile:230: ==
  ERROR: "devm_backlight_device_register" 
[/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined!
  make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1
  make[2]: *** [Makefile:1628: modules] Error 2
  make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2

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

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

[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.

[Gianfranco Costamagna]

We should
1) re-enable that on s390x

2) make the ddcci-driver-linux package stop providing binaries on s390x
or hint the testsuite in case the user wants to dkms on previous
kernels.


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  linux 5.2.0-8.9 disabled backlight on s390x.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Looks like ddcci-driver-linux started to fail on s390x with the switch
  from kernel 5.0.0-21-generic to 5.2.0-8-generic

  http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x


  According to changelog and diff:
  - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x

  from Seth Forshee.

  According to the build log of ddci backlight

  rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or 
directory
  Makefile:227: = WARNING 
  Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
  Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
  Makefile:230: ==
  Makefile:227: = WARNING 
  Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
  Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
  Makefile:230: ==
  ERROR: "devm_backlight_device_register" 
[/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined!
  make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1
  make[2]: *** [Makefile:1628: modules] Error 2
  make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2

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

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

[Kernel-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Kai-Heng Feng]

Maybe this? https://github.com/systemd/systemd/pull/10008

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/libinput/+bug/1825499/+subscriptions

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

[Kernel-packages] [Bug 1836876] Re: linux-raspi2: 4.4.0-1116.125 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  derivatives: bug 1836875 (pi2-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Testing
  phase-changed: Thursday, 18. July 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1836876

Title:
  linux-raspi2: 4.4.0-1116.125 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  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

  derivatives: bug 1836875 (pi2-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Testing
  phase-changed: Thursday, 18. July 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836801] Re: BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  BCM43602 802.11ac Wireless regression - PCI ID 14e4:43ba

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

Bug description:
  [Description]

  The wifi device BCM43602 802.11ac Wireless (PCI ID 14e4:43ba) running
  with the proposed kernel 4.4.0-155.182-generic will cause kernel
  trace[1]. However the wifi function works properly with the kernel
  4.4.0-154.181

  [Steps to Reproduce]
  1. Install ubuntu xenial, enable the proposed repository, and update the 
system with "sudo apt-get dist-upgrade"
  2. nmcli d wifi rescan
  3. nmcli -t -f SSID,CHAN,FREQ,SIGNAL d wifi list ifname wlp2s0 (if your wifi 
interface is wlp2s0), you will see the available SSIDs in your environment.
  4. nmcli d wifi connect  ifname wlp2s0 name TEST_CON

  [Expected Result]
  The AP is connected

  [Actual Result]
  You will get the message: "Error: Connection activation failed: (5) IP 
configuration could not be reserved (no available address, timeout, etc.)." and 
the kernel trace from /var/log/syslog[1]

  Sometime the system hangs when connecting to a wifi AP.

  [More Information]

  [1] The kernel trace log
  hecking kernel ring buffer for brcmfmac messages:
  kern  :info  : [Tue Jul 16 09:58:34 2019] usbcore: registered new interface 
driver brcmfmac
  kern  :warn  : [Tue Jul 16 09:58:34 2019] brcmfmac :02:00.0: Direct 
firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
  kern  :info  : [Tue Jul 16 09:58:35 2019] brcmfmac :02:00.0 wlp2s0: 
renamed from wlan0
  kern  :warn  : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep 
snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core 
snd_hda_core snd_hwd
  ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul 
dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device
   aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms 
brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc 
btintel
   videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma 
videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_netif_rx+0x73/0xa0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019] Modules linked in: rfcomm bnep 
snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_intel snd_hda_codec i2c_designware_platform i2c_designware_core 
snd_hda_core snd_hwd
  ep snd_pcm dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel snd_seq_midi dell_laptop kvm irqbypass crct10dif_pclmul crc32_pclmul 
dcdbas ghash_clmulni_intel snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device
   aesni_intel snd_timer aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
snd input_leds joydev soundcore serio_raw brcmfmac cdc_ether rtsx_pci_ms 
brcmutil usbnet memstick btusb btrtl uvcvideo btbcm cfg80211 videobuf2_vmalloc 
btintel
   videobuf2_memops r8152 bluetooth mii videobuf2_v4l2 idma64 virt_dma 
videobuf2_core mei_me v4l2_common intel_lpss_pci intel_lpss
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_netif_rx+0x73/0xa0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_msgbuf_process_rx+0x142/0x5f0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_proto_msgbuf_rx_trigger+0x31/0xe0 [brcmfmac]
  kern  :warn  : [Tue Jul 16 10:08:01 2019]  [] 
brcmf_pcie_isr_thread_v2+0x17a/0x1e0 [brcmfmac]

  [Known Affected Platforms]

  Dell XPS 15 9550 (CID 201606-22346)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-155-gene

[Kernel-packages] [Bug 1836878] Re: linux-snapdragon: 4.4.0-1120.126 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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
  
  derivatives: bug 1836877 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Testing
  phase-changed: Thursday, 18. July 2019 13:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1836878

Title:
  linux-snapdragon: 4.4.0-1120.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  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

  derivatives: bug 1836877 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1836880
  phase: Testing
  phase-changed: Thursday, 18. July 2019 13:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1836880] Re: linux: 4.4.0-156.183 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

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

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

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

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

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

** 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
  
  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
- phase: Promote to Proposed
- phase-changed: Thursday, 18. July 2019 11:55 UTC
+ bugs-spammed: true
+ phase: Testing
+ phase-changed: Thursday, 18. July 2019 16:13 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   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 in Ubuntu.
https://bugs.launchpad.net/bugs/1836880

Title:
  linux: 4.4.0-156.183 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: bug 1836879 (trusty/linux-lts-xenial)
  derivatives: bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834915 
(linux-fips), bug 1836874 (pc-kernel), bug 1836876 (linux-raspi2), bug 1836878 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 18. July 2019 16:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

Re: [Kernel-packages] [Bug 1836491] Re: Complete lock-up

[Bruce Smith]

The kernel causing the video freeze is 4.15.0-54.58

I have reverted to 4.15.0.52-56, there have been no video freezes with
this kernel.


On 7/18/19 10:06 AM, Kai-Heng Feng wrote:
> Would it be possible to find out the last kernel version that works and
> the first kernel version that causes the issue?
>

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

Title:
  Complete lock-up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This kernel has caused my video system to completely freeze. A hard restart 
is required to recover, but it happens each time. I have reverted to prior 
kernel.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   lmcor  2748 F...m pulseaudio
   /dev/snd/controlC1:  lmcor  2748 F pulseaudio
   /dev/snd/controlC0:  lmcor  2748 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=bf754a96-f70b-4964-bdbb-b7ab12e42018
  InstallationDate: Installed on 2018-09-30 (287 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171127
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=7663b459-8677-4afe-85fb-12424af45024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-52.56~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-52-generic N/A
   linux-backports-modules-4.15.0-52-generic  N/A
   linux-firmware 1.157.21
  Tags:  sylvia
  Uname: Linux 4.15.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3803
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1834936] Re: linux-gcp: 4.15.0-1037.39 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** 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
  
  backports: bug 1834935 (xenial/linux-gcp)
  derivatives: bug 1834931 (gcp-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
- phase: Testing
- phase-changed: Wednesday, 03. July 2019 22:37 UTC
+ phase: Ready for Testing
+ phase-changed: Thursday, 18. July 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1834936

Title:
  linux-gcp: 4.15.0-1037.39 -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:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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

  backports: bug 1834935 (xenial/linux-gcp)
  derivatives: bug 1834931 (gcp-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Ready for Testing
  phase-changed: Thursday, 18. July 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-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/1834936/+subscriptions

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

[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.

[Seth Forshee]

This driver is not useful for s390 so we should not change the kernel
config just to get it building. An example was posted of how to disable
a dkms build based on whether a required option is enabled the the
kernel config, here:

https://bugs.launchpad.net/ubuntu/+source/acpi-
call/+bug/1830040/comments/8

I think we should try something similar here.

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

** Changed in: ddcci-driver-linux (Ubuntu)
   Importance: Undecided => High

** Changed in: ddcci-driver-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/1837073

Title:
  linux 5.2.0-8.9 disabled backlight on s390x.

Status in ddcci-driver-linux package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Looks like ddcci-driver-linux started to fail on s390x with the switch
  from kernel 5.0.0-21-generic to 5.2.0-8-generic

  http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x


  According to changelog and diff:
  - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x

  from Seth Forshee.

  According to the build log of ddci backlight

  rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or 
directory
  Makefile:227: = WARNING 
  Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
  Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
  Makefile:230: ==
  Makefile:227: = WARNING 
  Makefile:228: 'SUBDIRS' will be removed after Linux 5.3
  Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead
  Makefile:230: ==
  ERROR: "devm_backlight_device_register" 
[/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined!
  make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1
  make[2]: *** [Makefile:1628: modules] Error 2
  make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2

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

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