[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000

[Maurizio Pellegrino]

Exactly same issues here.
I tried live version of Ubuntu 19.04 with Kernel 5.0.0-13-generic and:

- I have no wifi;
- I have no sound;
- Sudo command stuck on terminal.

No one of these issues until Kernel 4.19.

Info:

*-network
description: Wireless interface
product: PRO/Wireless 3945ABG [Golan] Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@:05:00.0
logical name: wlp5s0
version: 02
serial: 00:19:d2:04:51:06
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwl3945 
driverversion=4.15.0-47-generic firmware=15.32.2.9 ip=192.168.1.77 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
resources: irq:25 memory:d210-d2100fff

*-multimedia
 description: Audio device
 product: NM10/ICH7 Family High Definition Audio Controller
 vendor: Intel Corporation
 physical id: 1b
 bus info: pci@:00:1b.0
 version: 02
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:26 memory:d240-d2403fff

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

Title:
  Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at
  

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

Bug description:
  With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, 
typing sudo doesn't work.
  kern.log attached, include a boot with kernel 5 and one with 4.19 (which 
works ok)

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

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

[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -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: 1822817
  phase: Signoff
  phase-changed: Tuesday, 16. April 2019 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1042.46~14.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-signing-to-proposed series:
  Invalid
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:
  In Progress
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 Trusty:
  New

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: 1822817
  phase: Signoff
  phase-changed: Tuesday, 16. April 2019 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

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

Title:
  umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4

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

Bug description:
  This umip test failed on T-3.13 and T-4.4
  On X-4.4 this was skipped:
  SKIP umip (qemu-system-x86_64: CPU feature umip not found)

  So it looks like a qemu issue to me.

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu 
qemu64,+umip
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/umip.flat -smp 
1 -cpu qemu64,+umip # -initrd /tmp/tmp.WBWyPcleSg
  CPU feature umip not found
  enabling apic
  UMIP=0, CPL=0
  PASS: no exception from smsw
  PASS: no exception from sgdt
  PASS: no exception from sidt
  PASS: no exception from sldt
  PASS: no exception from str
  UMIP=0, CPL=3
  PASS: no exception from smsw
  PASS: no exception from sgdt
  PASS: no exception from sidt
  PASS: no exception from sldt
  PASS: no exception from str
  PASS: exception from mov %cr0, %eax
  UMIP not available
  SUMMARY: 11 tests

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:10:13 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[You-Sheng Yang]

This is not a kernel bug. `lsusb` from usbutils package
(bionic/cosmic/disco) only read name strings from usb.ids [1] files.
Upstream has merged a PR [2] to fallback to kernel sysfs attributes, and
with that the names will be correctly shown.


[1]: http://www.linux-usb.org/usb.ids
[2]: https://github.com/gregkh/usbutils/pull/81

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

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

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

** No longer affects: linux (Ubuntu)

** Summary changed:

- Goodix GF3208 (fingerprint reader) not being recognised  by kernel/system
+ Goodix GF3208 (fingerprint reader) not being recognised  by lsusb(usbutils)

** Also affects: usbutils
   Importance: Undecided
   Status: New

** No longer affects: usbutils

** Project changed: linux => usbutils

** Tags added: cosmic disco

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

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  lsusb(usbutils)

Status in usbutils:
  New
Status in usbutils package in Ubuntu:
  Confirmed

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

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

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

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

  Thanks in advance,
  Haz

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

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

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

[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker

[Po-Hsu Lin]

4.15.0-1042.46~14.04.1 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3 on Standard_B1ms and Standard_F1s
  monotonic_time - tsc failed on Standard_D2_v3
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) port80 (bug 1748105) 
umip (1821905) failed on Standard_D16s_v3, Standard_D2_v3, Standard_D2s_v3, 
Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2
  ubuntu_ltp - test disabled on azure
  ubuntu_ltp_syscalls - fallocate05, fdatasync03, fsetxattr01, fremovexattr01, 
fremovexattr02, fgetxattr01, fsync01, fsync04, lremovexattr01, msync04, 
preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01, statx04, 
sync_file_range02, syncfs01, sync03 (bug 1785198) quotactl01 (bug 1790028) 
statx05 (bug 1798524) inotify08 (bug 1775784) openat03 (bug 1798027) 
fanotify09-2 (bug 1804594)
  ubuntu_lxc - lxc test failed on Azure T-4.15 (bug 1813878)
  ubunut_qrt_apparmor - timed out on Standard-B1ms, Standard-F1s
  ubuntu_unionmount_overlayfs_suite - Rename empty dir and rename back failed 
(bug 1727290)

Skipped / blacklisted:
  * ubuntu_fan_smoke_test
  * ubuntu_kernel_selftests
  * ubuntu_lttng_smoke_test
  * ubuntu_nbd_smoke_test
  * ubuntu_sysdig_smoke_test
  * ubuntu_zfs_smoke_test


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-azure: 4.15.0-1042.46~14.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-signing-to-proposed series:
  Invalid
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:
  In Progress
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 Trusty:
  New

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: 1822817
  phase: Signoff
  phase-changed: Tuesday, 16. April 2019 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1821905] Re: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4

[Po-Hsu Lin]

Found on Azure Trusty 4.15 as well.

** Package changed: linux-signed-lts-xenial (Ubuntu) => linux (Ubuntu)

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

Title:
  umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4

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

Bug description:
  This umip test failed on T-3.13 and T-4.4
  On X-4.4 this was skipped:
  SKIP umip (qemu-system-x86_64: CPU feature umip not found)

  So it looks like a qemu issue to me.

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu 
qemu64,+umip
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/umip.flat -smp 
1 -cpu qemu64,+umip # -initrd /tmp/tmp.WBWyPcleSg
  CPU feature umip not found
  enabling apic
  UMIP=0, CPL=0
  PASS: no exception from smsw
  PASS: no exception from sgdt
  PASS: no exception from sidt
  PASS: no exception from sldt
  PASS: no exception from str
  UMIP=0, CPL=3
  PASS: no exception from smsw
  PASS: no exception from sgdt
  PASS: no exception from sidt
  PASS: no exception from sldt
  PASS: no exception from str
  PASS: exception from mov %cr0, %eax
  UMIP not available
  SUMMARY: 11 tests

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:10:13 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1821905] [NEW] umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This umip test failed on T-3.13 and T-4.4
On X-4.4 this was skipped:
SKIP umip (qemu-system-x86_64: CPU feature umip not found)

So it looks like a qemu issue to me.

root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu 
qemu64,+umip
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/umip.flat -smp 1 -cpu 
qemu64,+umip # -initrd /tmp/tmp.WBWyPcleSg
CPU feature umip not found
enabling apic
UMIP=0, CPL=0
PASS: no exception from smsw
PASS: no exception from sgdt
PASS: no exception from sidt
PASS: no exception from sldt
PASS: no exception from str
UMIP=0, CPL=3
PASS: no exception from smsw
PASS: no exception from sgdt
PASS: no exception from sidt
PASS: no exception from sldt
PASS: no exception from str
PASS: exception from mov %cr0, %eax
UMIP not available
SUMMARY: 11 tests

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
Uname: Linux 4.4.0-143-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Wed Mar 27 11:10:13 2019
SourcePackage: linux-signed-lts-xenial
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug trusty uec-images
-- 
umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4
https://bugs.launchpad.net/bugs/1821905
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

[Launchpad Bug Tracker]

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

Status in The Ubuntu Power Consumption Project:
  Expired
Status in bluez package in Ubuntu:
  Expired

Bug description:
  When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At
  this point you have to press any key to reconnect the device and let
  bluetoothd to return to work normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep 17 19:02:40 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2016-08-06 (406 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: GIGABYTE GB-BXBT-2807
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBAYAP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GB-BXBT-2807
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:85:DE:FD:2F:BC  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN ISCAN 
RX bytes:528225 acl:32183 sco:0 events:1134 errors:0
TX bytes:33849 acl:338 sco:0 commands:388 errors:1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1717796/+subscriptions

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

[Kernel-packages] [Bug 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

[Launchpad Bug Tracker]

[Expired for The Ubuntu Power Consumption Project because there has been
no activity for 60 days.]

** Changed in: ubuntu-power-consumption
   Status: Incomplete => Expired

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

Title:
  Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle

Status in The Ubuntu Power Consumption Project:
  Expired
Status in bluez package in Ubuntu:
  Expired

Bug description:
  When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At
  this point you have to press any key to reconnect the device and let
  bluetoothd to return to work normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep 17 19:02:40 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2016-08-06 (406 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: GIGABYTE GB-BXBT-2807
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MZBAYAP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GB-BXBT-2807
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: DC:85:DE:FD:2F:BC  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN ISCAN 
RX bytes:528225 acl:32183 sco:0 events:1134 errors:0
TX bytes:33849 acl:338 sco:0 commands:388 errors:1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1717796/+subscriptions

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

[Kernel-packages] [Bug 1815857] Re: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132

[Launchpad Bug Tracker]

[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132

Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  I'm not 100% sure what this firmware blob is actually used for, as the
  card is mostly functional without it and I'm not confident the broken
  bits aren't due to an incomplete driver, but it requests it for
  CA0132-based PCIe addin cards (Sound Blaster Recon3D, Z series, X
  AE-5).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 22:49:48 2019
  Dependencies:
   
  InstallationDate: Installed on 2018-09-12 (155 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

[Po-Hsu Lin]

** Package changed: linux-aws (Ubuntu) => linux (Ubuntu)

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

Title:
  vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

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

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.QldMaGLdve
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 5 unexpected failures

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

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

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -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: 1822834
- phase: Testing
- phase-changed: Monday, 15. April 2019 02:08 UTC
+ phase: Signoff
+ phase-changed: Friday, 19. April 2019 03:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-raspi2: 4.4.0-1107.115 -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 promote-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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: 1822834
  phase: Signoff
  phase-changed: Friday, 19. April 2019 03:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1822796] Re: linux: 4.18.0-18.19 -proposed tracker

[Po-Hsu Lin]

4.18.0-18.19 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kernel_selftests - rtnetlink.sh in net (bug 1812978) psock_snd in net 
(bug 1812618)
  ubuntu_kvm_unit_tests - apic-split timeouted (bug 1821390) apic timeouted 
(bug 1748103) svm (bug 1821903)
  ubuntu_ltp - failed to fork child on some tests
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 
1819116)
  xfstests - failed to build on C (bug 1802486)

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_bpf - Failed sockmap unexpected timeout on ARM64 (bug 1805806)
  ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) 
rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618)
  ubuntu_kvm_unit_tests - gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot 
ARM64 (bug 1802492)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 
1819116)
  xfstests - failed to build on C (bug 1802486)

47 / 48 tests were run, missing: xfstests
Issue to note in i386:
  ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578)
  ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988)
  ubuntu_kernel_selftests - rtnetlink.sh in net (bug 1812978) psock_snd in net 
(bug 1812618) Kprobe event string type argument in ftrace (bug 1812645)
  ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056)
  ubuntu_kvm_unit_tests - all 29 test failed on i386 (bug 1822235)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 
1819116)
  ubuntu_lttng_smoke_test - lttng-smoke test failed on i386 4.18 kernel (bug 
1802495)

Issue to note in ppc64le (P8):
  ubuntu_bpf - test_map failed on PowerPC (bug 1802474)
  ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988)
  ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) psock_snd 
in net (bug 1812618) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 
1812796) ebb in powerpc (bug 1812805)
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - fallocate05 (bug 1783880) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  xfstests - failed to build on C (bug 1802486)

48 / 49 tests were run, missing: xfstests
Issue to note in ppc64le (P9):
  hwclock - hwclock test failed on Power9 system with Bionic kernel (bug 
1775858)
  ubuntu_bpf - test_map failed on PowerPC (bug 1802474)
  ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988)
  ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) psock_snd 
in net (bug 1812618) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 
1812796) ebb in powerpc (bug 1812805)
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - fallocate05 (bug 1783880) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)

Test case ubuntu_ramfs_stress does not exist in the database, please check
41 / 48 tests were run, missing: ubuntu_boot, ubuntu_bpf, ubuntu_bpf_jit, 
ubuntu_btrfs_kernel_fixes, ubuntu_cts_kernel, ubuntu_stress_smoke_test, 
ubuntu_zfs_fstest, ubuntu_zfs_xfs_generic
Issue to note in s390x:
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341) 
sync_file_range02 (bug 1819116)

46 / 48 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes
Issue to note in s390x (Ubuntu on LPAR):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) TRACE_syscall 
in ftrace (bug 1812824)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 
1819116)
  ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is 
defined (bug 1788574)

46 / 48 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes
Issue to note in s390x (zVM):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) TRACE_syscall 
in ftrace (bug 1812824)
  ubuntu_kvm_unit_tests - skey failed (bug 1778705)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - Container "reboot" is defined (bug 1788574)

Note: No xfstests for P9 as it does not have a scratch drive
Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860)
Note: s390x KVM test result incomplete due to infrastructure migration


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is 

[Kernel-packages] [Bug 1822796] Re: linux: 4.18.0-18.19 -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 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822793 (linux-gcp), bug 1822794 
(linux-kvm), bug 1824771 (linux-aws), bug 1824841 (linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing 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/1822796

Title:
  linux: 4.18.0-18.19 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  New

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 1822795 (bionic/linux-hwe)
  derivatives: bug 1822786 (linux-raspi2), bug 1822793 (linux-gcp), bug 1822794 
(linux-kvm), bug 1824771 (linux-aws), bug 1824841 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 09:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -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: 1822820
- phase: Testing
- phase-changed: Monday, 15. April 2019 02:04 UTC
+ phase: Signoff
+ phase-changed: Friday, 19. April 2019 03:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1034.36 -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 promote-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1822820
  phase: Signoff
  phase-changed: Friday, 19. April 2019 03:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.15.0-1034.36/raspi2-4.15-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-raspi2: 4.15.0-1034.36 -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 promote-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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: 1822820
  phase: Testing
  phase-changed: Monday, 15. April 2019 02:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1107.115/raspi2-4.4-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-raspi2: 4.4.0-1107.115 -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 promote-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Monday, 15. April 2019 02:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1035.40

---
linux-oem (4.15.0-1035.40) bionic; urgency=medium

  * linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)

  * [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.

  * r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend

  * Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+

  * i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  [ Ubuntu: 4.15.0-47.50 ]

  * linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
  * C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
  * arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
  * Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
  * CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
  * CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
  * amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
  * tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
  * CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
  * raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
  adjustments are in progress
  * [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
  * CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
  paths
- bpf: add various test cases to selftests
  * CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
  * BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
  * squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
  * efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
  * Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
  * ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
  * Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
  * CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
  * CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
  * CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in 
card.c
  * CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
  * 

[Kernel-packages] [Bug 1817676] Re: r8169 doesn't get woken up by ethernet cable plugging, no PME generated

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1035.40

---
linux-oem (4.15.0-1035.40) bionic; urgency=medium

  * linux-oem: 4.15.0-1035.40 -proposed tracker (LP: #1819692)

  * [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.

  * r8169 doesn't get woken up by ethernet cable plugging, no PME generated
(LP: #1817676)
- Revert "PCI/PME: Implement runtime PM callbacks"
- PCI: pciehp: Disable Data Link Layer State Changed event on suspend

  * Fix I219 doesn't get woken up after plugging ethernet cable (LP: #1817058)
- e1000e: Disable runtime PM on CNP+

  * i915: Backport watermark fixes for gen9+ (LP: #1817848)
- drm/i915: Backport gen9+ watermark fixes from 5.0

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  [ Ubuntu: 4.15.0-47.50 ]

  * linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
  * C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
  * arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
  * Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
  * CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
  * CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
  * amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
  * tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
  * CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
  * raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
  adjustments are in progress
  * [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
  * CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
  paths
- bpf: add various test cases to selftests
  * CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
  * BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
  * squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
  * efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
  * Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
  * ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
  * Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
  * CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
  * CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
  * CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in 
card.c
  * CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
  * 

[Kernel-packages] [Bug 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-fips: 4.15.0-1005.6 -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:
  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:
  In Progress
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: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing 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/1824592

Title:
  linux-fips: 4.15.0-1005.6 -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:
  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:
  In Progress
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: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

[Mike]

1. I understand that it is done by command "git bisect reset"
2. If I understand You well I am already on first regression commit (blank 
screen issue) becouse I can't boot on 4.10-rc2+3 but on 4.9.0+-2 it was 
possible.

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

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

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

[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display

[Nicolas Devillers]

Hello,

It works fine with the proposed kernel 4.15.0-48-generic taken at:

http://ppa.launchpad.net/canonical-kernel-
team/proposed/ubuntu/pool/main/l/linux/

Please note that I updated to the latest Lenovo Provided Bios (1.23)
since then.

** Description changed:

  === SRU Justification ===
  [Impact]
- 4.15.0-46 breaks once worked external display over docking.
+ 4.15.0-46 breaks once working external display over docking.
  
  [Fix]
  Revert the commit that causes regression.
-  
+ 
  [Test]
  User confirms reverting the commit solves the regression.
  
  [Regression Potential]
  Low. Docking can works without this commit on Bionic kernel.
  
  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.
  
  === Original Bug Report ===
  
  Laptop is running Ubuntu 18.04.2 LTS.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  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
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare 
sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET37W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5000AFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5000AFR
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Crash from :i915 module with 4.15.0-46-generic using multi-display

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  4.15.0-46 breaks once working external display over docking.

  [Fix]
  Revert the commit that causes regression.

  [Test]
  User confirms reverting the commit solves the regression.

  [Regression Potential]
  Low. Docking can works without this commit on Bionic kernel.

  While previously working using 4.15.0-45-generic, booting my thinkpad
  T480 on a dock with additional screen connected and "kernel
  4.15.0-46-generic" lead to a crash of the system.

  === Original Bug Report ===

  Laptop is running Ubuntu 18.04.2 LTS.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   user   3449 F...m pulseaudio
   /dev/snd/controlC1:  user   3449 F pulseaudio
   /dev/snd/pcmC0D0p:   user   3449 F...m pulseaudio
   /dev/snd/controlC0:  user   3449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7
  InstallationDate: Installed on 2018-06-28 (256 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: LENOVO 20L5000AFR
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)

[Kleber Sacilotto de Souza]

Thank you, Satheesh.

Marking bug as verified.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during
  guest boot with > 256G of memory (kernel/kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==

  Rebooting a PowerPC VM with > 256G of memory results in a guest crash.

  == Fix ==

  Backport commit 46dec40fb741 ("KVM: PPC: Book3S HV: Don't truncate
  HPTE index in xlate function").

  == Regression Potential ==

  Low. Fix is trivial.

  == Test Case ==

  Create a PowerPC VM with > 256G of memory and reboot it repeatedly.

  == Original description ==

  == Comment: #0 - Satheesh Rajendran  - 2019-02-28 
04:38:22 ==
  ---Problem Description---
  Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory 
(kernel/kvm)

  Contact Information = sathe...@in.ibm.com

  ---uname output---
  Host Kernel: 4.15.0-1016-ibm-gt

  ii  qemu-system-ppc1:2.11+dfsg-
  1ubuntu7.8-1ibm3   ppc64el  QEMU
  full system emulation binaries (ppc)

  ii  libvirt-bin4.0.0-1ubuntu8.6
  ppc64el  programs for the libvirt library

  Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream)

  Machine Type = power9 ppc64le

  ---Steps to Reproduce---
   1. Boot a power8 compat guest with memory >256G
  virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml 
sosreport attached)
  Guest crashes while booting

  2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name 
guest=avocado-vt-vm1,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
 -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid 
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device 
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
 -device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
 -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
  2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100)
  2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3
  2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 : 
OBJECT_UNREF: obj=0x76d594111710
  2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus 
requested (256) exceeds the recommended cpus supported by KVM (128)
  2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of 
hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM 
(128)
  2019-02-28 10:37:18.060+: shutting down, reason=crashed
  2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from 
pid 14056 (/usr/sbin/libvirtd)

  *Additional Instructions for sathe...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Satheesh Rajendran  - 2019-02-28 
04:51:45 ==
  Possible Upstream fix: 

[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Norbert]

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

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions

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

[Kernel-packages] [Bug 1825429] [NEW] linux: -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

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 1825430 (bionic/linux-hwe-edge)

-- swm properties --

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lrm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.04.15-2

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lrm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team 

[Kernel-packages] [Bug 1824819] Re: linux: 5.0.0-13.14 -proposed tracker

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  linux: 5.0.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-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-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

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

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

  backports: bug 1824889 (bionic/linux-hwe-edge), bug 1825324 
(bionic/linux-oem-osp1)
  derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug 1824835 
(linux-gcp), bug 1824836 (linux-kvm)

  -- swm properties --
  phase: Testing
  phase-changed: Tuesday, 16. April 2019 09:29 UTC

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

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

[Kernel-packages] [Bug 1824559] Re: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)

[Hugo]

Hi!
Similar problem with my old HP netbook (fresh ubuntu 18.04.02 install)

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

Title:
  Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling
  frequency)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I have an issue with a lenovo yoga mouse.
  This mouse has 2 working mode either bluetooth or with a provided usb dongle.
  USB dongle works fine, but bluetooth don't.
  Cursor is slow and laggy.
  "evhz" (https://gitlab.com/iankelling/evhz) reports 22Hz in bluetooth mouse 
while USB mode and other mouse reports 125Hz.
  Polling speed is too slow.

  I tried different howto suggesting to change usbhid mousepoll value => does 
not help.
  The mouse seems handled by btusb module, not usbhid (modprobe -r usbhid 
killed my other mouse, but not the lenovo, while modprobe -r btusb killed the 
lenovo).

  I tried 2 laptops (XPS9370 with 18.04, kernel 4.18 and kernek 5.07 and
  an older dell Precision M6400 16.04 kernel 4.15).

  Bluetooth pairing works well, either with gnome bluetooth interface or
  with "bluetoothctl"

  Both laptops reports ~20-22Hz polling speed with evhz (and same laggy
  behavior)

  I also tried 2 bluetooth interface on the XPS13 9370 : the integrated
  bluetooth and a Sabrent USB Bluetooth 4.0 (to connect with the
  Sabrent, I have switched off integrated bluetooth with rfkill).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 12 18:05:16 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-10 (337 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.7-050007-generic 
root=UUID=d36c5071-0243-427d-8fe1-7416c3b775f1 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (40 days ago)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:8B:33:C6  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:12041 acl:294 sco:0 events:363 errors:0
TX bytes:8633 acl:76 sco:0 commands:171 errors:0

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

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

[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142

[Steve Langasek]

Hello fossfreedom, or anyone else affected,

Accepted dkms into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: dkms (Ubuntu Disco)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  No wireless networks displayed for broadcom BCM43142

Status in dkms package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Invalid
Status in dkms source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  The dkms version available in disco regressed in behavior in
  comparison to earlier series, causing `dkms uninstall` removing the
  module from the built tree instead of only uninstalling it. Per the
  dkms manpage, an uninstall operation should leave the module in the
  'built' state, while currently it ends up only in the 'added' state.

  This breaks our current shim-signed logic, since on postinst we're
  uninstalling every dkms module, checking if we uninstalled it
  correctly by making sure it's in the 'built' state and then signing it
  if everything is ok. And this is now broken.

  This seemed to have been introduced unintentionally as the manpage still 
notes for `dkms uninstall`:
  "Uninstalls an installed module/module-version combo from the kernel/arch 
passed in the -k option, or the current kernel if the -k option was not passed 
upon. After uninstall completion, the driver will be left in the built state.
  To completely remove a driver, the remove action should be utilized."

  The bug has been made visible with the bcmwl-kernel-source driver,
  which, if installed before shim-signed, will then become uninstalled
  and not reinstalled again (because of the failed status check before
  signing).

  [Test Case]

  An easy way of checking if the uninstall logic has been reverted:

   1. On a disco system, install the dkms and bcmwl-kernel-source packages 
(-proposed disabled).
   2. Check the version of the module installed `dkms status`.
   3. Once the installation completes, uninstall the bcmwl dkms module from the 
system:
   `dkms uninstall bcmwl/`
   4. Checks that the status is not reported as 'built' (should be something 
like 'added' only):
   `dkms status bcmwl`
   5. Enable disco-proposed and upgrade dkms.
   6. Re-install the bcmwl-kernel-source package.
   7. Once again uninstall the bcmwl dkms module:
   `dkms uninstall bcmwl/`
   8. Check the status and notice that it is now reported as 'built':
   `dkms status bcmwl`

  Another way would be checking on a secureboot-enabled system that has
  Broadcom wireless installing the -proposed dkms, then bcmwl-kernel-
  source and finally shim-signed (reinstalling if necessary). This
  operation should result in the broadcom dkms module still being
  installed and active. But this test should be counted as an optional
  'additional test'.

  [Regression Potential]

  Since this does change the dkms uninstall behavior, there is always
  some risk involved. One of the potential regressions could be related
  to kernel uninstallation, as we are reverting parts of the kernel
  prerm scripts along with the revert - but the risk should be low as
  we're actually reverting to the state we had in all series prior to
  disco. In overall the uninstall command of dkms might have regressed
  its behavior in case some other place started assuming the removals of
  modules from the built directory, but seeing the disco diff it's
  highly improbable.

  [Original Description]

  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that 

[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

[Manoj Iyer]

Also should have mentioned the kernel was also upgraded from -proposed
on bionic.

ubuntu@bobone:~$ uname -a 
Linux bobone 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:26:19 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@bobone:~$

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  console-setup.service
  

[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

[Manoj Iyer]

ubuntu@bobone:~$ uname -a
Linux bobone 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:40:40 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@bobone:~$ dmesg | grep nouveau | grep error
[3.020472] nouveau: probe of 0004:04:00.0 failed with error -12
[3.020667] nouveau: probe of 0004:05:00.0 failed with error -12
[3.021693] nouveau: probe of 0035:03:00.0 failed with error -12
[3.022595] nouveau: probe of 0035:04:00.0 failed with error -12
ubuntu@bobone:~$ find /lib/firmware/nvidia/gv100/ -name sw_nonctx.bin
find: ‘/lib/firmware/nvidia/gv100/’: No such file or directory
ubuntu@bobone:~$ apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.173.3
  Candidate: 1.173.3
  Version table:
 *** 1.173.3 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el 
Packages
500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el 
Packages
100 /var/lib/dpkg/status
 1.173 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages
ubuntu@bobone:~$ 


== install linux-firmware from proposed ==
The nouveau driver does not seems to identify the Nvidia chipset in the 4.15 
kernel. But it seems to load the firmware from linux-firmware, and load the 
driver. 

ubuntu@bobone:~$ apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.173.5
  Candidate: 1.173.5
  Version table:
 *** 1.173.5 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main ppc64el 
Packages
100 /var/lib/dpkg/status
 1.173.3 500
500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el 
Packages
500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el 
Packages
 1.173 500
500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages
ubuntu@bobone:~$

ubuntu@bobone:~$ find /lib/firmware/nvidia/gv100/ -name sw_nonctx.bin
/lib/firmware/nvidia/gv100/gr/sw_nonctx.bin
ubuntu@bobone:~$

ubuntu@bobone:~$ tree /lib/firmware/nvidia/gv100/
/lib/firmware/nvidia/gv100/
├── acr
│   ├── bl.bin
│   ├── ucode_load.bin
│   ├── ucode_unload.bin
│   └── unload_bl.bin
├── gr
│   ├── fecs_bl.bin
│   ├── fecs_data.bin
│   ├── fecs_inst.bin
│   ├── fecs_sig.bin
│   ├── gpccs_bl.bin
│   ├── gpccs_data.bin
│   ├── gpccs_inst.bin
│   ├── gpccs_sig.bin
│   ├── sw_bundle_init.bin
│   ├── sw_ctx.bin
│   ├── sw_method_init.bin
│   └── sw_nonctx.bin
├── nvdec
│   └── scrubber.bin
└── sec2
├── desc.bin
├── image.bin
└── sig.bin

4 directories, 20 files
ubuntu@bobone:~$ 

ubuntu@bobone:~$ dmesg | grep nouveau | grep error
[  157.554971] nouveau: probe of 0004:04:00.0 failed with error -12
[  157.555041] nouveau: probe of 0004:05:00.0 failed with error -12
[  157.555957] nouveau: probe of 0035:03:00.0 failed with error -12
[  157.556078] nouveau: probe of 0035:04:00.0 failed with error -12
ubuntu@bobone:~$

[  157.554928] nouveau 0004:04:00.0: unknown chipset (14a1)
[  157.554994] nouveau 0004:05:00.0: unknown chipset (14a1)
[  157.555880] nouveau 0035:03:00.0: unknown chipset (14a1)
[  157.556002] nouveau 0035:04:00.0: unknown chipset (14a1)

ubuntu@bobone:~$ lsmod | grep nouveau
nouveau  2150398  0
i2c_algo_bit8831  2 ast,nouveau
ttm   247484  2 ast,nouveau
drm_kms_helper209562  2 ast,nouveau
drm   503197  5 drm_kms_helper,ast,ttm,nouveau
ubuntu@bobone:~$

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le 

[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance

[Marcelo Cerri]

Hi, Joe.

Can you confirm the patch is also necessary for 4.15?

I backported the commit to xenial/linux-azure and it just required a bit
of fixing due to context differences. I also built a test kernel if you
want to test it:

https://kernel.ubuntu.com/~mhcerri/azure/xenial-linux-
azure-4.15.0-1042.46+lp1819689/

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

Title:
  [linux-azure] Commit To Improve NVMe Performance

Status in linux-azure package in Ubuntu:
  New

Bug description:
  In bug 1818138,  the config option CONFIG_NO_HZ_FULL was requested to
  be enabled in the linux-azure kernels(currently 4.15 and 4.18) in
  order to increase NVME disks performance.

  To achieve the peak IOPs we are seeing in testing, the following commit is 
also needed:
  7ac257b862f2c (“blk-mq: remove the request_list usage”)

  This commit cleans up unused code in block-mq (mq uses pre-allocated
  tags to allocate request, not request_list as it's used only in legacy
  queue).  The commit saves a bunch of rcu locks on I/O queuing path,
  which increases the achievable IOPs seen in testing.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

[Ubuntu Foundations Team Bug Bot]

The attachment "nvidia-background-workaround.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

-- 

[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [linux-azure] Commit To Improve NVMe Performance

Status in linux-azure package in Ubuntu:
  New

Bug description:
  In bug 1818138,  the config option CONFIG_NO_HZ_FULL was requested to
  be enabled in the linux-azure kernels(currently 4.15 and 4.18) in
  order to increase NVME disks performance.

  To achieve the peak IOPs we are seeing in testing, the following commit is 
also needed:
  7ac257b862f2c (“blk-mq: remove the request_list usage”)

  This commit cleans up unused code in block-mq (mq uses pre-allocated
  tags to allocate request, not request_list as it's used only in legacy
  queue).  The commit saves a bunch of rcu locks on I/O queuing path,
  which increases the achievable IOPs seen in testing.

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

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

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

[Roland Dreier]

I will try the upstream kernel, although it will be a few days before I
can confidently report if the issue is not present.

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

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET45W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JGS01000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1825420] [NEW] package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Norbert]

Public bug reported:

Steps to reproduce:
1. Have Ubuntu 18.10 installed
2. Install all updates to it
3. Switch to Main server
4. Launch update-manager
5. Confirm upgrading to 19.04
6. Wait for upgrade process to finish

Expected results:
* upgrade process ended without errors

Actual results:
* upgrade process ended with warning message:

Could not install 'linux-image-5.0.0-13-generic'
The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

triggers looping, abandoned

Workaround:

  Run recommended `dpkg --configure -a` before actual reboot.

System info: running VirtualBox guest with virtualbox-guest-x11
(6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mate   1542 F pulseaudio
Date: Thu Apr 18 22:56:56 2019
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2019-02-17 (60 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
RfKill:
 
SourcePackage: linux
StagingDrivers: vboxvideo
Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package disco staging

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox 

[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance

[Marcelo Cerri]

** Patch added: "0001-blk-mq-remove-the-request_list-usage_xenial.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+attachment/5256828/+files/0001-blk-mq-remove-the-request_list-usage_xenial.patch

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

Title:
  [linux-azure] Commit To Improve NVMe Performance

Status in linux-azure package in Ubuntu:
  New

Bug description:
  In bug 1818138,  the config option CONFIG_NO_HZ_FULL was requested to
  be enabled in the linux-azure kernels(currently 4.15 and 4.18) in
  order to increase NVME disks performance.

  To achieve the peak IOPs we are seeing in testing, the following commit is 
also needed:
  7ac257b862f2c (“blk-mq: remove the request_list usage”)

  This commit cleans up unused code in block-mq (mq uses pre-allocated
  tags to allocate request, not request_list as it's used only in legacy
  queue).  The commit saves a bunch of rcu locks on I/O queuing path,
  which increases the achievable IOPs seen in testing.

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

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

[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-azure: 4.15.0-1042.46 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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 Xenial:
  New

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 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1042.46 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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 Xenial:
  New

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 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption

[Michael Reed]

An additional patch has been identified that will be needed to solve
this issue.

https://github.com/torvalds/linux/commit/3c677d206210f53a4be972211066c0f1cd47fe12
#diff-083bf3d2f128b616e730b7f9f8fc65c4

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

Title:
  amd_iommu possible data corruption

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

Bug description:
  [Impact]
  If a device has an exclusion range specified in the IVRS table, this region 
needs to be reserved in the iova-domain of that device. This hasn't happened 
until now and can cause data corruption on data transfered with these devices.
  
  Treat exclusion ranges as reserved regions in the iommu-core to fix the 
problem.

  This is a clean cherry pick from mainline of
  8aafaaf2212192012f5bae305bb31cdf7681d777

  
  [Test Case]

  
  [Fixes]
  Cherry pick the following from Mainline
  fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range 
in iova-domain

  [Regression Risk]
  Only affects the amd_iommu driver:
  drivers/iommu/amd_iommu*

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

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

[Kernel-packages] [Bug 1799019] Re: Linux crashed so severly that I have to reinstall.

[Robert Pearson]

No since the kernel I reported does not work. After reinstalling Ubuntu
MATE 14.10, I am using kernel 4.18.0-generic. This version has its own
set of bugs (i.e. file and directory owner are improperly reported as
root my command line ls -l and Caja. I know this is a lie since I am not
logged in a root and have no trouble creating, deleting and modifying
files.

Why would I shut down my system since Oct 21, 2018 just waiting for some
response to a severe bug?

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

Title:
  Linux crashed so severly that I have to reinstall.

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  First Google Chrome and Chromium crashed closing all their windows.
  Then most, but not all, of the VisualWorks windows diappeared.
  (Unfortunately the System window closed so I could not exit properly).
  Then the list of open windows at the bottom of the screen disappeared,
  as did the menu bar at the top. With no menu to shutdown, I had to
  turn power off.

  When I tried to reboot I got the Ubuntu symbol and the progress dots
  underneath. After more than an hour, I got a command line to log in.
  (Not a terminal window - Ubuntu never started.)

  I was able to log in but could do nothing since this was a system
  without MATE or any window GUI.

  Every time I try to reboot, I get the save progress dots for over an
  hour and then the terminal mode login prompt.

  I had to boot from the distribution DVD to make this report before re-
  installing the system.

  Please fix your documentation on reporting system crashes. What is
  "apport" and how do I run it?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: MATE
  Date: Sun Oct 21 02:13:33 2018
  LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in

[Rico Heartstrings]

Here is the output of 'cat:
/sys/module/mt76x0u/parameters/disable_usb_sg'

cat: /sys/module/mt76x0u/parameters/disable_usb_sg: No such file or
directory


It seems the only directory where the module is located is 
/lib/modules/x.xx.x-xx-lowlatency/kernel/drivers/net/wireless/mediatek/mt76/...

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

Title:
  Ubuntu freezes when AC 430 WiFi Dongle is plugged in

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu crashes after a short time after plugging in the WiFi stick
  "AC430". The kernel fails to load the driver and the following message
  appears repeatedly:

  [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32
  ...

  Tested with Kernel 4.19 and 5.0 (5.0.2)
  Tested with the following distributions:
  Ubuntu Cosmic Cuttlefish 18.10
  Ubuntu Studio 18.10
  Ubuntu Disco Dingo 19.04

  40-usb_modeswitch.rules was already modified to load the driver, otherwise 
the system chooses Driver=option.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-03-31 (13 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.2-050002-lowlatency x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare 
scanner sudo tape vboxusers video
  _MarkForUpload: True

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  mdadm, mkfs, other io commands hang, stuck task, bad rip

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  1. disco
  2. # apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
   *** 5.0.0.13.14 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3. installation completes sucessfully
  4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the kernel throws an 
oops and bad rip value.

  [  967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds.
  [  967.811787]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.815500] mdadm   D0 12213  12207 0x
  [  967.815503] Call Trace:
  [  967.815509]  __schedule+0x2d0/0x840
  [  967.815511]  ? __switch_to_asm+0x40/0x70
  [  967.815512]  ? __switch_to_asm+0x34/0x70
  [  967.815514]  schedule+0x2c/0x70
  [  967.815516]  schedule_preempt_disabled+0xe/0x10
  [  967.815518]  __mutex_lock.isra.10+0x2e4/0x4c0
  [  967.815522]  ? exact_lock+0x11/0x20
  [  967.815524]  __mutex_lock_slowpath+0x13/0x20
  [  967.815528]  mutex_lock+0x2c/0x30
  [  967.815530]  __blkdev_get+0x7b/0x550
  [  967.815532]  ? bd_acquire+0xd0/0xd0
  [  967.815533]  blkdev_get+0x10c/0x330
  [  967.815535]  ? bd_acquire+0xd0/0xd0
  [  967.815537]  blkdev_open+0x92/0x100
  [  967.815539]  do_dentry_open+0x143/0x3a0
  [  967.815540]  vfs_open+0x2d/0x30
  [  967.815542]  path_openat+0x2d4/0x16d0
  [  967.815547]  ? put_device+0x17/0x20
  [  967.815552]  ? scsi_device_put+0x2b/0x30
  [  967.815553]  do_filp_open+0x93/0x100
  [  967.81]  ? strncpy_from_user+0x56/0x1b0
  [  967.815558]  ? __alloc_fd+0x46/0x140
  [  967.815560]  do_sys_open+0x177/0x280
  [  967.815561]  ? _cond_resched+0x19/0x30
  [  967.815563]  __x64_sys_openat+0x20/0x30
  [  967.815566]  do_syscall_64+0x5a/0x110
  [  967.815567]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.815568] RIP: 0033:0x7faa36406cce
  [  967.815572] Code: Bad RIP value.
  [  967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 
0101
  [  967.815574] RAX: ffda RBX: 4000 RCX: 
7faa36406cce
  [  967.815575] RDX: 4000 RSI: 564df70257b0 RDI: 
ff9c
  [  967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: 

  [  967.815576] R10:  R11: 0246 R12: 
7ffedb664240
  [  967.815577] R13:  R14: 0001 R15: 
564df7023e00

  [  967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds.
  [  967.803509]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.810235] mkfs.btrfs  D0  3767   1866 0x
  [  967.810239] Call Trace:
  [  967.810251]  __schedule+0x2d0/0x840
  [  967.810254]  ? __switch_to_asm+0x34/0x70
  [  967.810256]  ? __switch_to_asm+0x40/0x70
  [  967.810258]  schedule+0x2c/0x70
  [  967.810260]  schedule_timeout+0x258/0x360
  [  967.810277]  wait_for_completion+0xb7/0x140
  [  967.810281]  ? wake_up_q+0x80/0x80
  [  967.810293]  __floppy_read_block_0+0x138/0x190 [floppy]
  [  967.810298]  ? floppy_cmos_show+0x30/0x30 [floppy]
  [  967.810302]  floppy_revalidate+0xf8/0x230 [floppy]
  [  967.810307]  check_disk_change+0x62/0x70
  [  967.810309]  floppy_open+0x2ae/0x380 [floppy]
  [  967.810311]  __blkdev_get+0xe5/0x550
  [  967.810313]  ? bd_acquire+0xd0/0xd0
  [  967.810315]  blkdev_get+0x10c/0x330
  [  967.810316]  ? bd_acquire+0xd0/0xd0
  [  967.810318]  blkdev_open+0x92/0x100
  [  967.810321]  do_dentry_open+0x143/0x3a0
  [  967.810323]  vfs_open+0x2d/0x30
  [  967.810326]  path_openat+0x2d4/0x16d0
  [  967.810328]  ? filename_lookup.part.60+0xe0/0x170
  [  967.810332]  ? strncpy_from_user+0x56/0x1b0
  [  967.810333]  do_filp_open+0x93/0x100
  [  967.810353]  ? strncpy_from_user+0x56/0x1b0
  [  967.810358]  ? __alloc_fd+0x46/0x140
  [  967.810360]  do_sys_open+0x177/0x280
  [  967.810362]  ? _cond_resched+0x19/0x30
  [  967.810364]  __x64_sys_openat+0x20/0x30
  [  967.810368]  do_syscall_64+0x5a/0x110
  [  967.810369]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.810372] RIP: 0033:0x7f46b99374db
  [  967.810377] Code: Bad RIP value.
  [  967.810378] RSP: 002b:7ffc9e849d70 EFLAGS: 0246 ORIG_RAX: 
0101
  [  967.810380] RAX: ffda RBX: 556674552080 RCX: 
7f46b99374db
  [  

[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip

[Ryan Harper]

root@ubuntu:~# lspci -v -nn
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
Flags: fast devsel

00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton 
II] [8086:7000]
Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
Flags: medium devsel

00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010] (prog-if 80 [ISA Compatibility mode-only 
controller, supports bus mastering])
Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
Flags: bus master, medium devsel, latency 0
[virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 03f0 (type 3, non-prefetchable)
[virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 0370 (type 3, non-prefetchable)
I/O ports at c080 [size=16]
Kernel driver in use: ata_piix
Kernel modules: pata_acpi

00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] 
(rev 03)
Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
Flags: medium devsel, IRQ 9
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4

00:02.0 VGA compatible controller [0300]: Device [1234:] (rev 02) (prog-if 
00 [VGA controller])
Subsystem: Red Hat, Inc. Device [1af4:1100]
Flags: fast devsel
Memory at fd00 (32-bit, prefetchable) [size=16M]
Memory at feb9 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 000c [disabled] [size=128K]
Kernel driver in use: bochs-drm
Kernel modules: bochs_drm

00:03.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio SCSI [1af4:1004]
Subsystem: Red Hat, Inc. Virtio SCSI [1af4:0008]
Physical Slot: 3
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c000 [size=64]
Memory at feb91000 (32-bit, non-prefetchable) [size=4K]
Memory at fe00 (64-bit, prefetchable) [size=16K]
Capabilities: [98] MSI-X: Enable+ Count=4 Masked-
Capabilities: [84] Vendor Specific Information: VirtIO: 
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Kernel driver in use: virtio-pci

00:04.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG [1af4:1005]
Subsystem: Red Hat, Inc. Virtio RNG [1af4:0004]
Physical Slot: 4
Flags: bus master, fast devsel, latency 0, IRQ 10
I/O ports at c040 [size=32]
Memory at fe004000 (64-bit, prefetchable) [size=16K]
Capabilities: [84] Vendor Specific Information: VirtIO: 
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Kernel driver in use: virtio-pci

00:05.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device 
[1af4:1000]
Subsystem: Red Hat, Inc. Virtio network device [1af4:0001]
Physical Slot: 5
Flags: bus master, fast devsel, latency 0, IRQ 10
I/O ports at c060 [size=32]
Memory at feb92000 (32-bit, non-prefetchable) [size=4K]
Memory at fe008000 (64-bit, prefetchable) [size=16K]
Expansion ROM at feb0 [disabled] [size=512K]
Capabilities: [98] MSI-X: Enable+ Count=3 Masked-
Capabilities: [84] Vendor Specific Information: VirtIO: 
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Kernel driver in use: virtio-pci

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

Title:
  mdadm, mkfs, other io commands hang, stuck task, bad rip

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  1. disco
  2. # apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
   *** 5.0.0.13.14 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3. installation completes sucessfully
  4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the 

[Kernel-packages] [Bug 1825413] [NEW] mdadm, mkfs, other io commands hang, stuck task, bad rip

[Ryan Harper]

Public bug reported:


1. disco
2. # apt-cache policy linux-image-virtual
linux-image-virtual:
  Installed: 5.0.0.13.14
  Candidate: 5.0.0.13.14
  Version table:
 *** 5.0.0.13.14 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
3. installation completes sucessfully
4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the kernel throws an 
oops and bad rip value.

[  967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds.
[  967.811787]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
[  967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.815500] mdadm   D0 12213  12207 0x
[  967.815503] Call Trace:
[  967.815509]  __schedule+0x2d0/0x840
[  967.815511]  ? __switch_to_asm+0x40/0x70
[  967.815512]  ? __switch_to_asm+0x34/0x70
[  967.815514]  schedule+0x2c/0x70
[  967.815516]  schedule_preempt_disabled+0xe/0x10
[  967.815518]  __mutex_lock.isra.10+0x2e4/0x4c0
[  967.815522]  ? exact_lock+0x11/0x20
[  967.815524]  __mutex_lock_slowpath+0x13/0x20
[  967.815528]  mutex_lock+0x2c/0x30
[  967.815530]  __blkdev_get+0x7b/0x550
[  967.815532]  ? bd_acquire+0xd0/0xd0
[  967.815533]  blkdev_get+0x10c/0x330
[  967.815535]  ? bd_acquire+0xd0/0xd0
[  967.815537]  blkdev_open+0x92/0x100
[  967.815539]  do_dentry_open+0x143/0x3a0
[  967.815540]  vfs_open+0x2d/0x30
[  967.815542]  path_openat+0x2d4/0x16d0
[  967.815547]  ? put_device+0x17/0x20
[  967.815552]  ? scsi_device_put+0x2b/0x30
[  967.815553]  do_filp_open+0x93/0x100
[  967.81]  ? strncpy_from_user+0x56/0x1b0
[  967.815558]  ? __alloc_fd+0x46/0x140
[  967.815560]  do_sys_open+0x177/0x280
[  967.815561]  ? _cond_resched+0x19/0x30
[  967.815563]  __x64_sys_openat+0x20/0x30
[  967.815566]  do_syscall_64+0x5a/0x110
[  967.815567]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  967.815568] RIP: 0033:0x7faa36406cce
[  967.815572] Code: Bad RIP value.
[  967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 
0101
[  967.815574] RAX: ffda RBX: 4000 RCX: 7faa36406cce
[  967.815575] RDX: 4000 RSI: 564df70257b0 RDI: ff9c
[  967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: 
[  967.815576] R10:  R11: 0246 R12: 7ffedb664240
[  967.815577] R13:  R14: 0001 R15: 564df7023e00

[  967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds.
[  967.803509]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
[  967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  967.810235] mkfs.btrfs  D0  3767   1866 0x
[  967.810239] Call Trace:
[  967.810251]  __schedule+0x2d0/0x840
[  967.810254]  ? __switch_to_asm+0x34/0x70
[  967.810256]  ? __switch_to_asm+0x40/0x70
[  967.810258]  schedule+0x2c/0x70
[  967.810260]  schedule_timeout+0x258/0x360
[  967.810277]  wait_for_completion+0xb7/0x140
[  967.810281]  ? wake_up_q+0x80/0x80
[  967.810293]  __floppy_read_block_0+0x138/0x190 [floppy]
[  967.810298]  ? floppy_cmos_show+0x30/0x30 [floppy]
[  967.810302]  floppy_revalidate+0xf8/0x230 [floppy]
[  967.810307]  check_disk_change+0x62/0x70
[  967.810309]  floppy_open+0x2ae/0x380 [floppy]
[  967.810311]  __blkdev_get+0xe5/0x550
[  967.810313]  ? bd_acquire+0xd0/0xd0
[  967.810315]  blkdev_get+0x10c/0x330
[  967.810316]  ? bd_acquire+0xd0/0xd0
[  967.810318]  blkdev_open+0x92/0x100
[  967.810321]  do_dentry_open+0x143/0x3a0
[  967.810323]  vfs_open+0x2d/0x30
[  967.810326]  path_openat+0x2d4/0x16d0
[  967.810328]  ? filename_lookup.part.60+0xe0/0x170
[  967.810332]  ? strncpy_from_user+0x56/0x1b0
[  967.810333]  do_filp_open+0x93/0x100
[  967.810353]  ? strncpy_from_user+0x56/0x1b0
[  967.810358]  ? __alloc_fd+0x46/0x140
[  967.810360]  do_sys_open+0x177/0x280
[  967.810362]  ? _cond_resched+0x19/0x30
[  967.810364]  __x64_sys_openat+0x20/0x30
[  967.810368]  do_syscall_64+0x5a/0x110
[  967.810369]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  967.810372] RIP: 0033:0x7f46b99374db
[  967.810377] Code: Bad RIP value.
[  967.810378] RSP: 002b:7ffc9e849d70 EFLAGS: 0246 ORIG_RAX: 
0101
[  967.810380] RAX: ffda RBX: 556674552080 RCX: 7f46b99374db
[  967.810381] RDX: 0008 RSI: 556674552100 RDI: ff9c
[  967.810382] RBP: 55667454a270 R08: 556674552120 R09: 4000
[  967.810382] R10:  R11: 0246 R12: 5cb8c394
[  967.810383] R13: 7f46b3c4 R14: dcb8c394 R15: 7f46b9988425

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-virtual 5.0.0.13.14
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair

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

[Kai-Heng Feng]

Please test this kernel:
https://people.canonical.com/~khfeng/lp1824981/

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

Bug description:
  Ubuntu 18.04.2 LTS
  Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM

  top - 12:39:53 up  3:41,  4 users,  load average: 66.19, 64.06, 76.90
  Tasks: 1076 total,   1 running, 675 sleeping,  12 stopped,   1 zombie
  %Cpu(s): 28.2 us,  0.3 sy,  0.0 ni, 71.5 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 
st
  KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache
  KiB Swap:   999420 total,   999420 free,0 used. 33477683+avail Mem


  We've seen the following bug many times since we introduced new
  machines running Ubuntu 18. Wasn't an issue older machines running
  Ubuntu 16. Three different machines are affected, so it's rather not a
  hardware issue.

  
  | detected buffer overflow in strcat
  | [ cut here ]
  | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052!
  | invalid opcode:  [#1] SMP PTI
  | Modules linked in: [...]
  | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018
  | RIP: 0010:fortify_panic+0x13/0x22
  |  [...]
  | Call Trace:
  |  smb21_set_oplock_level+0x147/0x1a0 [cifs]
  |  smb3_set_oplock_level+0x22/0x90 [cifs]
  |  smb2_set_fid+0x76/0xb0 [cifs]
  |  cifs_new_fileinfo+0x259/0x390 [cifs]
  |  ? smb2_get_lease_key+0x40/0x40 [cifs]
  |  ? cifs_new_fileinfo+0x259/0x390 [cifs]
  |  cifs_open+0x3db/0x8d0 [cifs]
  |  [...]

  (Full dmesg output attached)

  After hitting this bug there are many cifs related dmesg entries,
  processes lock up and eventually the systems freezes.

  
  The share is mounted using:
  //server/share  /mnt/server/ cifs 
defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks

  Currently we're testing the cifs mount options "cache=none" as the bug
  seems to be oplock related.

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 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15

[Sean Feole]

Affects , 4.15.0-1036.38~16.04.1 linux-aws-hwe

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

Title:
  ubuntu_nbd_smoke_test failed with I/O error on X-4.15

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

Bug description:
  Kernel: 4.15.0-45.48~16.04.1

  creating backing nbd image /tmp/nbd_image.img

  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-25789
  Date:  Thu Jan 31 14:42:42 UTC 2019
  Host:  onibi
  Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 
UTC 2019
  Machine:   onibi x86_64 x86_64
  CPUs online:   4
  CPUs total:4
  Page size: 4096
  Pages avail:   1351388
  Pages total:   2038431
  Free space:
  Filesystem  Size  Used Avail Use% Mounted on
  udev3.9G 0  3.9G   0% /dev
  tmpfs   797M   17M  780M   3% /run
  /dev/sda1   917G  9.1G  861G   2% /
  tmpfs   3.9G  4.0K  3.9G   1% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
  tmpfs   797M 0  797M   0% /run/user/1000
  tmpfs   100K 0  100K   0% /var/lib/lxd/shmounts
  tmpfs   100K 0  100K   0% /var/lib/lxd/devlxd
  cgmfs   100K 0  100K   0% /run/cgmanager/fs
  


  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting client with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  checking ext4 on /dev/nbd0
  fsck from util-linux 2.27.1
  /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks

  mount:
  /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered)
  mounted on /dev/nbd0

  free:
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/nbd0 122835  1550112111   2% /mnt/nbd-test-25789

  creating large file /mnt/nbd-test-25789/largefile
  -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile

  free:
  Filesystem 1K-blocks   Used Available Use% Mounted on
  /dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-25789

  removing file /mnt/nbd-test-25789/largefile
  unmounting /mnt/nbd-test-25789
  stopping client
  disconnect, sock, done
  Found kernel warning, IO error and/or call trace
  echo
  [ 4593.254552] creating backing nbd image /tmp/nbd_image.img
  [ 4595.506134] NBD device /dev/nbd0 created
  [ 4595.557990] found nbd export
  [ 4596.604855] starting client with NBD device /dev/nbd0
  [ 4596.606795] creating ext4 on /dev/nbd0
  [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  [ 4597.390241] checking ext4 on /dev/nbd0
  [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
  [ 4597.460552] mounted on /dev/nbd0
  [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile
  [ 4599.056704] removing file /mnt/nbd-test-25789/largefile
  [ 4599.276298] unmounting /mnt/nbd-test-25789
  [ 4600.319460] stopping client
  [ 4600.320083] block nbd0: NBD_DISCONNECT
  [ 4600.320127] block nbd0: shutting down sockets
  [ 4600.320267] nbd0: detected capacity change from 0 to 134217728
  [ 4600.320306] print_req_error: 7 callbacks suppressed
  [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.358279] ldm_validate_partition_table(): Disk read failed.
  [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.408826] Dev nbd0: unable to read RDB block 0
  [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24
  [ 4600.431433] Buffer I/O error on dev nbd0, logical block 3, async page 

[Kernel-packages] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.4.0-1081.91 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-aws: 4.4.0-1081.91 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 (armhf and aarch64)

[Paweł Jarosz]

** Summary changed:

- CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)
+ CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 (armhf and aarch64)

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 (armhf and aarch64)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
  for arch armhf and aarch64?

  Related kernel config options:

  CONFIG_ARCH_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP_HOST
  CONFIG_EMAC_ROCKCHIP
  CONFIG_DWMAC_ROCKCHIP
  CONFIG_ROCKCHIP_PHY
  CONFIG_SPI_ROCKCHIP
  CONFIG_PINCTRL_ROCKCHIP
  CONFIG_ROCKCHIP_IODOMAIN
  CONFIG_ROCKCHIP_THERMAL
  CONFIG_VIDEO_ROCKCHIP_RGA
  CONFIG_DRM_ROCKCHIP
  CONFIG_ROCKCHIP_ANALOGIX_DP
  CONFIG_ROCKCHIP_CDN_DP
  CONFIG_ROCKCHIP_DW_HDMI
  CONFIG_ROCKCHIP_DW_MIPI_DSI
  CONFIG_ROCKCHIP_INNO_HDMI
  CONFIG_ROCKCHIP_LVDS
  CONFIG_ROCKCHIP_RGB
  CONFIG_SND_SOC_ROCKCHIP
  CONFIG_SND_SOC_ROCKCHIP_I2S
  CONFIG_SND_SOC_ROCKCHIP_PDM
  CONFIG_SND_SOC_ROCKCHIP_SPDIF
  CONFIG_SND_SOC_ROCKCHIP_MAX98090
  CONFIG_SND_SOC_ROCKCHIP_RT5645
  CONFIG_MMC_DW_ROCKCHIP
  CONFIG_ROCKCHIP_TIMER
  CONFIG_ROCKCHIP_MBOX
  CONFIG_ROCKCHIP_IOMMU
  CONFIG_ROCKCHIP_GRF
  CONFIG_ROCKCHIP_PM_DOMAINS
  CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI
  CONFIG_ROCKCHIP_SARADC
  CONFIG_PWM_ROCKCHIP
  CONFIG_PHY_ROCKCHIP_DP
  CONFIG_PHY_ROCKCHIP_EMMC
  CONFIG_PHY_ROCKCHIP_INNO_HDMI
  CONFIG_PHY_ROCKCHIP_INNO_USB2
  CONFIG_PHY_ROCKCHIP_PCIE
  CONFIG_PHY_ROCKCHIP_TYPEC
  CONFIG_PHY_ROCKCHIP_USB
  CONFIG_ROCKCHIP_EFUSE
  CONFIG_CRYPTO_DEV_ROCKCHIP

  Cheers,
  Paweł Jarosz

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

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

[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

[Manoj Iyer]

ubuntu@bobone:~$ uname -a 
Linux bobone 4.18.0-17-generic #18-Ubuntu SMP Wed Mar 13 14:30:03 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux

ubuntu@bobone:~$ dmesg | grep nouveau | grep error
ubuntu@bobone:~$  

ubuntu@bobone:~$ find  /lib/firmware/nvidia/gv100/ -name sw_nonctx.bin
/lib/firmware/nvidia/gv100/gr/sw_nonctx.bin
ubuntu@bobone:~$ 

ubuntu@bobone:~$ tree /lib/firmware/nvidia/gv100/
/lib/firmware/nvidia/gv100/
├── acr
│   ├── bl.bin
│   ├── ucode_load.bin
│   ├── ucode_unload.bin
│   └── unload_bl.bin
├── gr
│   ├── fecs_bl.bin
│   ├── fecs_data.bin
│   ├── fecs_inst.bin
│   ├── fecs_sig.bin
│   ├── gpccs_bl.bin
│   ├── gpccs_data.bin
│   ├── gpccs_inst.bin
│   ├── gpccs_sig.bin
│   ├── sw_bundle_init.bin
│   ├── sw_ctx.bin
│   ├── sw_method_init.bin
│   └── sw_nonctx.bin
├── nvdec
│   └── scrubber.bin
└── sec2
├── desc.bin
├── image.bin
└── sig.bin

4 directories, 20 files
ubuntu@bobone:~$

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [  

[Kernel-packages] [Bug 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)

[Paweł Jarosz]

I'm not able to add any logs since rockchip support is not enabled in
ubuntu 18.04 armhf and aarch64 kernels.

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
  for arch armhf and aarch64?

  Related kernel config options:

  CONFIG_ARCH_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP_HOST
  CONFIG_EMAC_ROCKCHIP
  CONFIG_DWMAC_ROCKCHIP
  CONFIG_ROCKCHIP_PHY
  CONFIG_SPI_ROCKCHIP
  CONFIG_PINCTRL_ROCKCHIP
  CONFIG_ROCKCHIP_IODOMAIN
  CONFIG_ROCKCHIP_THERMAL
  CONFIG_VIDEO_ROCKCHIP_RGA
  CONFIG_DRM_ROCKCHIP
  CONFIG_ROCKCHIP_ANALOGIX_DP
  CONFIG_ROCKCHIP_CDN_DP
  CONFIG_ROCKCHIP_DW_HDMI
  CONFIG_ROCKCHIP_DW_MIPI_DSI
  CONFIG_ROCKCHIP_INNO_HDMI
  CONFIG_ROCKCHIP_LVDS
  CONFIG_ROCKCHIP_RGB
  CONFIG_SND_SOC_ROCKCHIP
  CONFIG_SND_SOC_ROCKCHIP_I2S
  CONFIG_SND_SOC_ROCKCHIP_PDM
  CONFIG_SND_SOC_ROCKCHIP_SPDIF
  CONFIG_SND_SOC_ROCKCHIP_MAX98090
  CONFIG_SND_SOC_ROCKCHIP_RT5645
  CONFIG_MMC_DW_ROCKCHIP
  CONFIG_ROCKCHIP_TIMER
  CONFIG_ROCKCHIP_MBOX
  CONFIG_ROCKCHIP_IOMMU
  CONFIG_ROCKCHIP_GRF
  CONFIG_ROCKCHIP_PM_DOMAINS
  CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI
  CONFIG_ROCKCHIP_SARADC
  CONFIG_PWM_ROCKCHIP
  CONFIG_PHY_ROCKCHIP_DP
  CONFIG_PHY_ROCKCHIP_EMMC
  CONFIG_PHY_ROCKCHIP_INNO_HDMI
  CONFIG_PHY_ROCKCHIP_INNO_USB2
  CONFIG_PHY_ROCKCHIP_PCIE
  CONFIG_PHY_ROCKCHIP_TYPEC
  CONFIG_PHY_ROCKCHIP_USB
  CONFIG_ROCKCHIP_EFUSE
  CONFIG_CRYPTO_DEV_ROCKCHIP

  Cheers,
  Paweł Jarosz

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

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

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

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
  for arch armhf and aarch64?

  Related kernel config options:

  CONFIG_ARCH_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP_HOST
  CONFIG_EMAC_ROCKCHIP
  CONFIG_DWMAC_ROCKCHIP
  CONFIG_ROCKCHIP_PHY
  CONFIG_SPI_ROCKCHIP
  CONFIG_PINCTRL_ROCKCHIP
  CONFIG_ROCKCHIP_IODOMAIN
  CONFIG_ROCKCHIP_THERMAL
  CONFIG_VIDEO_ROCKCHIP_RGA
  CONFIG_DRM_ROCKCHIP
  CONFIG_ROCKCHIP_ANALOGIX_DP
  CONFIG_ROCKCHIP_CDN_DP
  CONFIG_ROCKCHIP_DW_HDMI
  CONFIG_ROCKCHIP_DW_MIPI_DSI
  CONFIG_ROCKCHIP_INNO_HDMI
  CONFIG_ROCKCHIP_LVDS
  CONFIG_ROCKCHIP_RGB
  CONFIG_SND_SOC_ROCKCHIP
  CONFIG_SND_SOC_ROCKCHIP_I2S
  CONFIG_SND_SOC_ROCKCHIP_PDM
  CONFIG_SND_SOC_ROCKCHIP_SPDIF
  CONFIG_SND_SOC_ROCKCHIP_MAX98090
  CONFIG_SND_SOC_ROCKCHIP_RT5645
  CONFIG_MMC_DW_ROCKCHIP
  CONFIG_ROCKCHIP_TIMER
  CONFIG_ROCKCHIP_MBOX
  CONFIG_ROCKCHIP_IOMMU
  CONFIG_ROCKCHIP_GRF
  CONFIG_ROCKCHIP_PM_DOMAINS
  CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI
  CONFIG_ROCKCHIP_SARADC
  CONFIG_PWM_ROCKCHIP
  CONFIG_PHY_ROCKCHIP_DP
  CONFIG_PHY_ROCKCHIP_EMMC
  CONFIG_PHY_ROCKCHIP_INNO_HDMI
  CONFIG_PHY_ROCKCHIP_INNO_USB2
  CONFIG_PHY_ROCKCHIP_PCIE
  CONFIG_PHY_ROCKCHIP_TYPEC
  CONFIG_PHY_ROCKCHIP_USB
  CONFIG_ROCKCHIP_EFUSE
  CONFIG_CRYPTO_DEV_ROCKCHIP

  Cheers,
  Paweł Jarosz

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

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

[Kernel-packages] [Bug 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)

[Paweł Jarosz]

** Summary changed:

- Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf and 
aarch64) kernel config?
+ CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)

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

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set on ubuntu 18.04 (armhf and aarch64)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
  for arch armhf and aarch64?

  Related kernel config options:

  CONFIG_ARCH_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP_HOST
  CONFIG_EMAC_ROCKCHIP
  CONFIG_DWMAC_ROCKCHIP
  CONFIG_ROCKCHIP_PHY
  CONFIG_SPI_ROCKCHIP
  CONFIG_PINCTRL_ROCKCHIP
  CONFIG_ROCKCHIP_IODOMAIN
  CONFIG_ROCKCHIP_THERMAL
  CONFIG_VIDEO_ROCKCHIP_RGA
  CONFIG_DRM_ROCKCHIP
  CONFIG_ROCKCHIP_ANALOGIX_DP
  CONFIG_ROCKCHIP_CDN_DP
  CONFIG_ROCKCHIP_DW_HDMI
  CONFIG_ROCKCHIP_DW_MIPI_DSI
  CONFIG_ROCKCHIP_INNO_HDMI
  CONFIG_ROCKCHIP_LVDS
  CONFIG_ROCKCHIP_RGB
  CONFIG_SND_SOC_ROCKCHIP
  CONFIG_SND_SOC_ROCKCHIP_I2S
  CONFIG_SND_SOC_ROCKCHIP_PDM
  CONFIG_SND_SOC_ROCKCHIP_SPDIF
  CONFIG_SND_SOC_ROCKCHIP_MAX98090
  CONFIG_SND_SOC_ROCKCHIP_RT5645
  CONFIG_MMC_DW_ROCKCHIP
  CONFIG_ROCKCHIP_TIMER
  CONFIG_ROCKCHIP_MBOX
  CONFIG_ROCKCHIP_IOMMU
  CONFIG_ROCKCHIP_GRF
  CONFIG_ROCKCHIP_PM_DOMAINS
  CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI
  CONFIG_ROCKCHIP_SARADC
  CONFIG_PWM_ROCKCHIP
  CONFIG_PHY_ROCKCHIP_DP
  CONFIG_PHY_ROCKCHIP_EMMC
  CONFIG_PHY_ROCKCHIP_INNO_HDMI
  CONFIG_PHY_ROCKCHIP_INNO_USB2
  CONFIG_PHY_ROCKCHIP_PCIE
  CONFIG_PHY_ROCKCHIP_TYPEC
  CONFIG_PHY_ROCKCHIP_USB
  CONFIG_ROCKCHIP_EFUSE
  CONFIG_CRYPTO_DEV_ROCKCHIP

  Cheers,
  Paweł Jarosz

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

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

[Kernel-packages] [Bug 1751268]

[Jani-nikula]

drm-tip works, nothing in dmesg to indicate failure. Pretty much the
only way to get progress is to get a bisect result.

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

Title:
  bionic desktop does not boot with external monitor attached -
  [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A
  stuck / vblank wait timed out on crtc 1

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

Bug description:
  Ubuntu Desktop Bionic up to date

  System doesn't boot with an external monitor attached.

  There is this message in the journal (full journal attached for this
  boot)

  fbcon: inteldrmfb (fb0) is primary device
  [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck
  vblank wait timed out on crtc 1
  [ cut here ]
  WARNING: CPU: 3 PID: 201 at 
/build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 
drm_wait_one_vblank+0x19b/0x1b0 [drm]
  Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb 
hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video
  CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U  
4.13.0-32-generic #35-Ubuntu
  Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013
  Workqueue: events_unbound async_run_entry_fn
  task: 9760d81cae80 task.stack: b01dc1fb8000
  RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm]
  RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282
  RAX: 001f RBX: 9760d708 RCX: 
  RDX:  RSI: 0002 RDI: 0246
  RBP: b01dc1fbb828 R08: 001f R09: 0002af84
  R10: b01dc1fbb7c8 R11: 041b R12: 0001
  R13: 0170 R14: 0001 R15: 
  FS:  () GS:9760eef8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0
  Call Trace:
   ? wait_woken+0x80/0x80
   ironlake_crtc_enable+0x477/0xc00 [i915]
   ? gen6_write8+0x190/0x190 [i915]
   intel_update_crtc+0x4b/0xe0 [i915]
   intel_update_crtcs+0x5b/0x80 [i915]
   intel_atomic_commit_tail+0x254/0xf90 [i915]
   ? __schedule+0x293/0x880
   intel_atomic_commit+0x3d5/0x490 [i915]
   ? drm_atomic_check_only+0x37b/0x540 [drm]
   drm_atomic_commit+0x4b/0x50 [drm]
   restore_fbdev_mode+0x15e/0x270 [drm_kms_helper]
   drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper]
   drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
   intel_fbdev_set_par+0x1a/0x70 [i915]
   fbcon_init+0x484/0x650
   visual_init+0xd6/0x130
   do_bind_con_driver+0x1fc/0x410
   do_take_over_console+0x82/0x1a0
   do_fbcon_takeover+0x5c/0xb0
   fbcon_event_notify+0x587/0x780
   notifier_call_chain+0x4a/0x70
   blocking_notifier_call_chain+0x43/0x60
   fb_notifier_call_chain+0x1b/0x20
   register_framebuffer+0x24d/0x360
   drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper]
   intel_fbdev_initial_config+0x18/0x30 [i915]
   async_run_entry_fn+0x36/0x150
   process_one_work+0x1e7/0x410
   worker_thread+0x4b/0x420
   kthread+0x125/0x140
   ? process_one_work+0x410/0x410
   ? kthread_create_on_node+0x70/0x70
   ret_from_fork+0x1f/0x30
  Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 
0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 
0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 
  ---[ end trace a1db7ccd0b5e4dfc ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  j-lallement   3671 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3671 F pulseaudio
   /dev/snd/controlC1:  j-lallement   3671 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 13:58:39 2018
  InstallationDate: Installed on 2013-09-03 (1633 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

[Kai-Heng Feng]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc5 kernel [0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed”, and attach dmesg.

Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc5/

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

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Testing
- phase-changed: Monday, 08. April 2019 15:06 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 17:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

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: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 17:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -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: 1822834
  phase: Testing
  phase-changed: Thursday, 18. April 2019 16:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   verification-testing: Pending -- Ready

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

Title:
  linux-aws: 4.4.0-1042.45 -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:
  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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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: 1822834
  phase: Testing
  phase-changed: Thursday, 18. April 2019 16:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga
  2nd gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
  docking station.  Initial connection to the dock works great, but
  after a few plug/unplug and suspend/resume cycles, the system gets in
  a state where a reboot is needed to make the dock work.  The
  displayport connection still works so my external monitor gets the
  right display, but the thunderbolt / PCIe connection does not and so
  the USB and network ports in the dock aren't usable.  I assume it is
  connected to the kernel messages like

  [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
  [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

  [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
  [37270.096820] pci :09:00.0: enabling Extended Tags
  [37270.096975] pci :09:00.0: supports D1 D2
  [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
  [37270.097187] pcieport :07:01.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
  [37270.108705] pci :0a:00.0: enabling Extended Tags
  [37270.108865] pci :0a:00.0: supports D1 D2
  [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
  [37270.109066] pcieport :07:02.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
  [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
  [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
  [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
  [37270.109499] pci :0b:00.0: supports D1
  [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
  [37270.109686] pcieport :07:04.0: ASPM: current common clock 
configuration is broken, reconfiguring
  [37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
  [37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
  [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 
0b
  [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under 
[bus 07-0b] (conflicts with (null) [bus 07-0b])
  [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
  [37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
  [37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
  [37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roland 1690 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:40:22 2019
  InstallationDate: Installed on 2019-03-29 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20JGS01000
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET45W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JGS01000
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1825395] [NEW] thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen

[Roland Dreier]

Public bug reported:

I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt
docking station.  Initial connection to the dock works great, but after
a few plug/unplug and suspend/resume cycles, the system gets in a state
where a reboot is needed to make the dock work.  The displayport
connection still works so my external monitor gets the right display,
but the thunderbolt / PCIe connection does not and so the USB and
network ports in the dock aren't usable.  I assume it is connected to
the kernel messages like

[37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630
[37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock

[37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400
[37270.096820] pci :09:00.0: enabling Extended Tags
[37270.096975] pci :09:00.0: supports D1 D2
[37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited 
by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
[37270.097187] pcieport :07:01.0: ASPM: current common clock configuration 
is broken, reconfiguring
[37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400
[37270.108705] pci :0a:00.0: enabling Extended Tags
[37270.108865] pci :0a:00.0: supports D1 D2
[37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[37270.109066] pcieport :07:02.0: ASPM: current common clock configuration 
is broken, reconfiguring
[37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330
[37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit]
[37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit]
[37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit]
[37270.109499] pci :0b:00.0: supports D1
[37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold
[37270.109686] pcieport :07:04.0: ASPM: current common clock configuration 
is broken, reconfiguring
[37270.109724] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
[37270.109738] pci :09:00.0: devices behind bridge are unusable because 
[bus 0a] cannot be assigned for them
[37270.109766] pci :0a:00.0: devices behind bridge are unusable because 
[bus 0b] cannot be assigned for them
[37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b
[37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 
07-0b] (conflicts with (null) [bus 07-0b])
[37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70]
[37270.109843] pcieport :07:04.0:   bridge window [mem 
0xd400-0xe9ff]
[37270.109848] pcieport :07:04.0:   bridge window [mem 
0x9000-0xb9ff 64bit pref]
[37270.109849] pcieport :07:04.0: devices behind bridge are unusable 
because [bus 3d-70] cannot be assigned for them

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  roland 1690 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 09:40:22 2019
InstallationDate: Installed on 2019-03-29 (20 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
MachineType: LENOVO 20JGS01000
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1NET45W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20JGS01000
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET45W(1.32):bd03/11/2019:svnLENOVO:pn20JGS01000:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JGS01000:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga 2nd
dmi.product.name: 20JGS01000
dmi.product.sku: LENOVO_MT_20JG_BU_Think_FM_ThinkPad X1 Yoga 2nd
dmi.product.version: ThinkPad X1 Yoga 2nd
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -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/security-signoff
   Status: New => In Progress

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
- phase: Promote to Proposed
- phase-changed: Thursday, 18. April 2019 12:09 UTC
+ phase: Testing
+ phase-changed: Thursday, 18. April 2019 16: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
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Pending -- Ready

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

Title:
  linux-aws: 4.4.0-1042.45 -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:
  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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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: 1822834
  phase: Testing
  phase-changed: Thursday, 18. April 2019 16:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Pending -- Ready

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Pablo Palácios]

I've got the same using archlinux latest kernel with a dell computer, i7
and an pcie network card as well. I've found this thread on redhat
bugzilla very helpful:

https://bugzilla.redhat.com/show_bug.cgi?id=681017

I was able to solve my problem by explicitly disabling aspm in my bios.
>From factory it was set to auto which perhaps could result in "device
has no support for aspm but let's enabled aspm anyway" behavior making
kernel confused.

** Bug watch added: Red Hat Bugzilla #681017
   https://bugzilla.redhat.com/show_bug.cgi?id=681017

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

Title:
  AER: Corrected error received: id=00e0

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

Bug description:
  WORKAROUND: add pci=noaer to your kernel command line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-oracle: 4.15.0-1011.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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  New

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 1822811 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 08:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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 1822811 (xenial/linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 08:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1011.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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  New

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 1822811 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 08:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824841] Re: linux-azure: 4.18.0-1016.16 -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 1824839 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
- phase: Testing
- phase-changed: Wednesday, 17. April 2019 08:27 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 16:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1016.16 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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 Cosmic:
  New

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 1824839 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 16:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

[Jeremy Soller]

I was able to work around this with the attached patch. Apply by adding
the file to debian/patches and its name to the end of
debian/patches/series

** Patch added: "nvidia-background-workaround.patch"
   
https://bugs.launchpad.net/gnome-shell/+bug/1809407/+attachment/5256741/+files/nvidia-background-workaround.patch

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective

[Jeremy]

To clarify, I am running Ubuntu 4.15.0-47.50-generic 4.15.18 at my
office

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

Title:
  Super + p does not work as expected, it's defective

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have 3 monitors (2 landscape and 1 portrait), I normally need to
  change between my monitors due to my setup. If I want to play a game,
  I typically switch to a single monitor (Built-in) then I can switch
  back to Join and everything goes back to normal. That is what I would
  expect but that is NOT what happens.

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

  The first two options work correctly, but the 3rd and 4th options do
  not.

  
  External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.

  
  I am using:
  - Ubuntu 4.15.0-47.50-generic 4.15.18
  - GeForce GTX 1080/PCIe/SSE2
  - I have attached: lspci-vnvn.log

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  With nvidia-driver-418 from: ppa:graphics-drivers/ppa

  $ apt-cache policy nvidia-driver-418
  nvidia-driver-418:
Installed: 418.56-0ubuntu0~gpu18.04.1
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   *** 418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status


  I am not sure if this is actually necessary because I don't think this
  has to do with the graphics card.

  I am not sure what other information you will need for this report. I can 
provide more data upon request.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (298 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1651199] Re: 16.04 - Kernel panic on docker server

[Bug Watch Updater]

** Changed in: linux
   Status: New => 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/1651199

Title:
  16.04 - Kernel panic on docker server

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [31016.057405] BUG: unable to handle kernel paging request at 82c4801e6bda
  [31016.061249] IP: [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] PGD 0 
  [31016.061380] Oops: 0010 [#1] SMP 
  [31016.061380] Modules linked in: binfmt_misc xt_REDIRECT nf_nat_redirect 
veth xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo xt_addrtype iptable_filter xt_conntrack br_netfilter bridge stp llc 
overlay xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables isofs ppdev serio_raw 
parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd ixgbevf psmouse floppy
  [31016.061380] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-53-generic 
#74-Ubuntu
  [31016.061380] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
  [31016.061380] task: 880406496040 ti: 8804064e task.ti: 
8804064e
  [31016.061380] RIP: 0010:[]  [] 
__xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] RSP: 0018:88040fc43f78  EFLAGS: 00010082
  [31016.061380] RAX:  RBX: 88040fc4b840 RCX: 
0001
  [31016.061380] RDX: fffe RSI: 000123a0 RDI: 
88040fc43f30
  [31016.061380] RBP: 88040fc43f90 R08: f24a R09: 
0001
  [31016.061380] R10: 0001 R11:  R12: 
0001
  [31016.061380] R13: 0003 R14:  R15: 
8804064e
  [31016.178419] FS:  () GS:88040fc4() 
knlGS:
  [31016.178419] CS:  0010 DS:  ES:  CR0: 80050033
  [31016.178419] CR2: 82c4801e6bda CR3: 000204f2f000 CR4: 
001406e0
  [31016.178419] DR0:  DR1:  DR2: 

  [31016.178419] DR3:  DR6: fffe0ff0 DR7: 
0400
  [31016.178419] Stack:
  [31016.178419]   0003  
88040fc43fa8
  [31016.178419]  814d6bc0 81f36a00 8804064e3e90 
81837f32
  [31016.178419]  8804064e3de8   8804064e  

  [31016.178419] Call Trace:
  [31016.178419]   
  [31016.178419]  [] xen_evtchn_do_upcall+0x30/0x40
  [31016.178419]  [] xen_hvm_callback_vector+0x82/0x90
  [31016.178419]   
  [31016.178419]  [] ? native_safe_halt+0x6/0x10
  [31016.178419]  [] default_idle+0x1e/0xe0
  [31016.239315]  [] arch_cpu_idle+0xf/0x20
  [31016.239899]  [] default_idle_call+0x2a/0x40
  [31016.239899]  [] cpu_startup_entry+0x2f1/0x350
  [31016.239899]  [] start_secondary+0x154/0x190
  [31016.239899] Code: 01 00 00 00 65 44 8b 2d dc 56 b3 7e c6 03 00 44 89 e0 65 
0f c1 05 2e d8 b3 7e 85 c0 75 35 48 8b 05 63 ce d0 00 44 89 ef ff 50 50 <9c> 58 
0f 1f 44 00 00 f6 c4 02 75 23 65 8b 05 0a d8 b3 7e 65 c7 
  [31016.239899] RIP  [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.239899]  RSP 
  [31016.239899] CR2: 82c4801e6bda
  [31016.239899] ---[ end trace 5b3e8ea32013e327 ]---
  [31016.239899] Kernel panic - not syncing: Fatal exception in interrupt
  [31016.239899] Kernel Offset: disabled

  
  We believe this appeared in the last 1-2mo of releases, since this started 
happening after we did a `apt-get upgrade` on our machines after a bit of a 
pause. These are EC2 m4.xlarge servers running Ubuntu 16.04.1. They are 
Kubernetes minions, so I assume docker is likely the trigger.

  Unfortunately there aren't really any interesting logs in journalctl
  from the previous boot prior to the panic.

  Let me know what I can do to debug further.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 19 15:56 seq
   crw-rw 1 root audio 116, 33 Dec 19 15:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: 

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

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

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

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

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

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

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

Title:
  fib related test in net from ubuntu_kernel_selftests failed on C-KVM

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

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -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: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

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: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

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

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

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

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

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

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

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

Title:
  RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-kvm source package in Cosmic:
  Invalid

Bug description:
  This test failed because of the unsuccessful attempt to add a dummy device 
with ip link command:
  # devdummy="test-dummy0"
  # ip link add name "$devdummy" type dummy
  RTNETLINK answers: Operation not supported

  
   selftests: rtnetlink.sh
   
   RTNETLINK answers: Operation not supported
   Cannot find device "test-dummy0"
   FAIL: cannot add dummy interface
   not ok 1..10 selftests: rtnetlink.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:21:02 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -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 1822833 (trusty/linux-lts-xenial), bug 1824775 
(trusty/linux-aws)
  derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 
(linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Thursday, 04. April 2019 18:05 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 16:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

Title:
  linux: 4.4.0-146.172 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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 1822833 (trusty/linux-lts-xenial), bug 1824775 
(trusty/linux-aws)
  derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 
(linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 16:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

[Jeremy Soller]

There is an upstream bug related to GNOME 3.32 here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1084
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
   Importance: Unknown
   Status: Unknown

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

-- 

[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/oem/4.15.0-1036.41/oem-4.15-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

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: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-146.172
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-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/1822834

Title:
  linux: 4.4.0-146.172 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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 1822833 (trusty/linux-lts-xenial), bug 1824775 
(trusty/linux-aws)
  derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 
(linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1824839] Re: linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-azure: 4.18.0-1016.16~18.04.1 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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:
  New

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 1824838 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824839] Re: linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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 1824838 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1016.16~18.04.1 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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:
  New

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 1824838 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1037.39 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1812194] Re: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

[Kleber Sacilotto de Souza]

Also found in cosmic/linux-azure:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-cosmic/cosmic/amd64/l/linux-
azure/20190416_185145_846ae@/log.gz

I'll nominate this bug against cosmic/linux.

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

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

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

** Changed in: linux-kvm (Ubuntu Cosmic)
   Status: New => Invalid

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

Title:
  RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-kvm source package in Cosmic:
  Invalid

Bug description:
  This test failed because of the unsuccessful attempt to add a dummy device 
with ip link command:
  # devdummy="test-dummy0"
  # ip link add name "$devdummy" type dummy
  RTNETLINK answers: Operation not supported

  
   selftests: rtnetlink.sh
   
   RTNETLINK answers: Operation not supported
   Cannot find device "test-dummy0"
   FAIL: cannot add dummy interface
   not ok 1..10 selftests: rtnetlink.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:21:02 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed on C-KVM

[Kleber Sacilotto de Souza]

Also found in cosmic/linux-azure:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-cosmic/cosmic/amd64/l/linux-
azure/20190416_185145_846ae@/log.gz

I'll nominate this bug against cosmic/linux.

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

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

Title:
  fib related test in net from ubuntu_kernel_selftests failed on C-KVM

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

Bug description:
  These tests:
  * fib_tests.sh
  * fib-onlink-tests.sh
  * fib_rule_tests.sh

  All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not
  supported:

  
   selftests: net: fib_tests.sh
  
   Single path route test
   RTNETLINK answers: Operation not supported
   not ok 1..11 selftests: net: fib_tests.sh [FAIL]

   selftests: net: fib-onlink-tests.sh
  
  
   Configuring interfaces
   RTNETLINK answers: Operation not supported
   not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL]

   selftests: net: fib_rule_tests.sh
   
   RTNETLINK answers: Operation not supported
   not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL]


  (works on generic Cosmic kernel)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
  ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
  Uname: Linux 4.18.0-1006-kvm x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  Date: Mon Jan 21 08:00:22 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.15.0-1037.39 -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:
  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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824886] Re: Battery level stuck at 100% and Estimating...

[Mike Kapushin]

Version 4.15 works well. Now I have installed Debian 9 with a kernel 4.9
on this device, it works well.

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

Title:
  Battery level stuck at 100% and Estimating...

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Battery applet does not display battery charge. Always shows 100%.

  ASUS 1215T-RED008S.
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Установлен: 1:3.28.2-0ubuntu0.18.04.2
Кандидат:   1:3.28.2-0ubuntu0.18.04.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 00:48:18 2019
  InstallationDate: Installed on 2019-04-10 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -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: 1822834
  phase: Promote to Proposed
  phase-changed: Thursday, 18. April 2019 12:09 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-aws: 4.4.0-1042.45 -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:
  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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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: 1822834
  phase: Promote to Proposed
  phase-changed: Thursday, 18. April 2019 12:09 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

[Tyler Hicks]

Hello - Talat, could you please try the workaround that I mentioned in
comment #4? It should be all you need to get back to the old threshold
values.

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

Title:
  [cosmic] ipoib ping with large message size failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We see that ping over ipoib interface stuck with large packets, this is a new 
degradation, this test pass on Ubuntu 18.04.
  After investigating the issue, we see that commit [1] introduce the issue, 
and it is not an upstream commit, it is canonical commit.
  Could you please check with the canonical kernel team why they revert that 
commit? 
  To reproduce the bug, please use ConnectX-3 devices with ipoib connection 
with 2044 MTU (default) and run command [2].
  Is there open Launchpad on it?
   
  [1]
  commit 77a24c313d21e3765b04d90521e9228a9bb6e332
  Author: Tyler Hicks 
  Date:   Fri Aug 3 21:53:15 2018 +
   
  Revert "net: increase fragment memory usage limits"
   
  This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It
  made denial of service attacks on the IP fragment handling easier to
  carry out.
   
  CVE-2018-5391
   
  Signed-off-by: Tyler Hicks 
  Signed-off-by: Stefan Bader 
   
  [2]
  ping 13.194.22.1 -I 13.194.23.1 -s 65507

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

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

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

[Dzh]

Same issue with Dell G5 5587

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 27c6:5381  
Bus 001 Device 003: ID 0c45:6718 Microdia 
Bus 001 Device 005: ID 8087:0aaa Intel Corp. 
Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

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

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

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

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

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

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

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

  Thanks in advance,
  Haz

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

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

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

[Kernel-packages] [Bug 1802306] Re: Network connectivity lost after a few minutes on Intel Corporation Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36

[Pirouette Cacahuète]

Okay, after a few minutes under Disco, I'm still experiencing strange
delays on WiFi on my home router, Netgear R7000, very very similar to
the latencies on Mozilla's network. Revering to v34 firmware seems to
workaround the issue.

> [6.367375] iwlwifi :3d:00.0: loaded firmware version 36.9f0a2d68.0 
> op_mode iwlmvm
> [6.406151] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 
> 8265, REV=0x230

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

Title:
  Network connectivity lost after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36

Status in linux package in Ubuntu:
  Expired

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -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: 1822834
  phase: Promote to Proposed
  phase-changed: Thursday, 18. April 2019 12:09 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages copies requested

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

Title:
  linux-aws: 4.4.0-1042.45 -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:
  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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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: 1822834
  phase: Promote to Proposed
  phase-changed: Thursday, 18. April 2019 12:09 UTC
  reason:
promote-to-proposed: Ongoing -- packages copies requested

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

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

[Kernel-packages] [Bug 1802168] Re: Unable to get right-click working on ThinkPad T480s

[Pirouette Cacahuète]

Just upgraded to Disco, it seems okay, not checked if it's really fixed
or just a workaround in place.

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

Title:
  Unable to get right-click working on ThinkPad T480s

Status in libinput:
  Fix Released
Status in Linux:
  Unknown
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated to Ubuntu 18.10, I've been fighting some weird behavior of the
  touchpad. Now, right-click does not work, whatever solution I try
  within gnome-tweaks, whether relying on multi-finger tapping or not.

  Found a very very close report from RedHat, on the same model of laptop, 
around kernel 4.18, with a fix: 
https://bugzilla.redhat.com/show_bug.cgi?id=1628715
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2195 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1802306] Re: Network connectivity lost after a few minutes on Intel Corporation Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36

[Pirouette Cacahuète]

None of the kernel upgrade for Cosmic would improve the situation. I've
upgraded to Disco and keeping an eye on this.

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

Title:
  Network connectivity lost after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36

Status in linux package in Ubuntu:
  Expired

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813883] Re: reuseport_bpf in net from kernel_selftests failed to build on X-4.15

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Bionic)
   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/1813883

Title:
  reuseport_bpf in net from kernel_selftests failed to build on X-4.15

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

Bug description:
  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ 
reuseport_bpf.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf
  ../lib.mk:109: recipe for target 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf'
 failed
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  Makefile:72: recipe for target 'all' failed
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  stderr:
  reuseport_bpf.c: In function ‘attach_ebpf’:
  reuseport_bpf.c:126:33: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first 
use in this function)
  if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd,
  ^
  reuseport_bpf.c:126:33: note: each undeclared identifier is reported only 
once for each function it appears in
  reuseport_bpf.c: In function ‘attach_cbpf’:
  reuseport_bpf.c:148:33: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first 
use in this function)
  if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , sizeof(p)))
  ^
  reuseport_bpf.c: In function ‘test_filter_no_reuseport’:
  reuseport_bpf.c:378:34: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first 
use in this function)
  if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd,
  ^
  reuseport_bpf.c:383:34: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first 
use in this function)
  if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, ,
  ^
  make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf]
 Error 1
  make: *** [all] Error 2

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

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

[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -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 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Testing
- phase-changed: Friday, 05. April 2019 17:08 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1042.46 -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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow 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 Xenial:
  New

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 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 14:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker

[Łukasz Zemczak]

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

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

Title:
  linux-aws: 4.4.0-1042.45 -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:
  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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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: 1822834
  phase: Promote to Proposed
  phase-changed: Thursday, 18. April 2019 12:09 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective

[Jeremy]

I also checked this on my office workstation which has a similar setup
but different GFX card. The exact issue happens there. I think this is
how this works in general in Ubuntu.

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

Title:
  Super + p does not work as expected, it's defective

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have 3 monitors (2 landscape and 1 portrait), I normally need to
  change between my monitors due to my setup. If I want to play a game,
  I typically switch to a single monitor (Built-in) then I can switch
  back to Join and everything goes back to normal. That is what I would
  expect but that is NOT what happens.

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

  The first two options work correctly, but the 3rd and 4th options do
  not.

  
  External and Built-in do the exact same thing: they simply shift my monitors 
around, lose all settings (reset everything). So all 3 monitors are still in 
use but settings are cleared (orientation, resolution, and frequency are 
reset). I have to then open up the settings to change it all back. When I go 
back to Join, I would expect the settings to return to normal. They do not. 
Super + P simply wipes out monitor settings in my case.

  
  I am using:
  - Ubuntu 4.15.0-47.50-generic 4.15.18
  - GeForce GTX 1080/PCIe/SSE2
  - I have attached: lspci-vnvn.log

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  
  With nvidia-driver-418 from: ppa:graphics-drivers/ppa

  $ apt-cache policy nvidia-driver-418
  nvidia-driver-418:
Installed: 418.56-0ubuntu0~gpu18.04.1
Candidate: 418.56-0ubuntu0~gpu18.04.1
Version table:
   *** 418.56-0ubuntu0~gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status


  I am not sure if this is actually necessary because I don't think this
  has to do with the graphics card.

  I am not sure what other information you will need for this report. I can 
provide more data upon request.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC1:  jpsimkins   3108 F pulseaudio
   /dev/snd/controlC0:  jpsimkins   3108 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-22 (298 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD5H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1801574] Re: [cosmic] ipoib ping with large message size failed

[Jeff Lane]

Hi Tyler, do you have any update for this bug?

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

Title:
  [cosmic] ipoib ping with large message size failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We see that ping over ipoib interface stuck with large packets, this is a new 
degradation, this test pass on Ubuntu 18.04.
  After investigating the issue, we see that commit [1] introduce the issue, 
and it is not an upstream commit, it is canonical commit.
  Could you please check with the canonical kernel team why they revert that 
commit? 
  To reproduce the bug, please use ConnectX-3 devices with ipoib connection 
with 2044 MTU (default) and run command [2].
  Is there open Launchpad on it?
   
  [1]
  commit 77a24c313d21e3765b04d90521e9228a9bb6e332
  Author: Tyler Hicks 
  Date:   Fri Aug 3 21:53:15 2018 +
   
  Revert "net: increase fragment memory usage limits"
   
  This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It
  made denial of service attacks on the IP fragment handling easier to
  carry out.
   
  CVE-2018-5391
   
  Signed-off-by: Tyler Hicks 
  Signed-off-by: Stefan Bader 
   
  [2]
  ping 13.194.22.1 -I 13.194.23.1 -s 65507

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

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

[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)

[Derk Willem te Bokkel]

Fine tuning:  only one extra mount is necessary .. then plymouth
finishes very quickly .. and xorg/lightdm  start normally!

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (boot timing issues implicated)

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

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+subscriptions

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

[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822812
- phase: Testing
- phase-changed: Tuesday, 09. April 2019 13:13 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1011.13~16.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-signing-to-proposed series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

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: 1822812
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update

[Seth Forshee]

https://lists.ubuntu.com/archives/kernel-team/2019-April/100221.html

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

** Also affects: linux (Ubuntu Disco)
   Importance: High
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

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

Title:
  [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel
  update

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

Bug description:
  [SRU Justification]

  Impact: The virtualbox package was updated in disco just prior to
  release, with numerous bug fixes. It is standard practice during
  development to sync our in-kernel source with the latest version of
  the virtualbox-guest-dkms package, however this upload was done so
  late in the release that there was not time to update the source in
  our kernel tree.

  Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1.

  Regression Potential: This is a sync from the dkms package in the
  disco-release pocket, thus the code has presumably been tested against
  the Ubuntu Disco kernel. However, this is a very large pile of
  changes, and contains more than just bug fixes, so regressions are
  possible.

  Test Case: Boot a kernel with the updated driver in virtualbox and
  confirm that the guest drier functionality works as expected.

  ---

  * the changes are already in disco (vbox-guest-dkms), and they are fixes for 
the kernel 5.0.
  They might seem a lot of changes, but they are needed, and probably some of 
them are even CVE fixes...

  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

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