date:20190410

You have been subscribed to a public bug:

It looks like there are some dependency issue for the ARM64 meta
package.

# apt-get install --yes linux-generic-hwe-18.04-edge
 Reading package lists...
 Building dependency tree...
 Reading state information...
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 
5.0.0.8.66) but it is not going to be installed
 E: Unable to correct problems, you have held broken packages.

More check on this:
# apt-get install linux-image-generic-hwe-18.04-edge
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but 
it is not installable
E: Unable to correct problems, you have held broken packages.


It works well with PowerPC / AMD64 / i386, just not ARM64

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

-- 
Unable to install linux-generic-hwe-18.04-edge on ARM64 in -proposed
https://bugs.launchpad.net/bugs/1824081
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 1824081] Re: Unable to install linux-generic-hwe-18.04-edge on ARM64 in -proposed

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

** Description changed:

  It looks like there are some dependency issue for the ARM64 meta
  package.
  
  # apt-get install --yes linux-generic-hwe-18.04-edge
-  Reading package lists...
-  Building dependency tree...
-  Reading state information...
-  Some packages could not be installed. This may mean that you have 
-  requested an impossible situation or if you are using the unstable 
-  distribution that some required packages have not yet been created
-  or been moved out of Incoming. 
-  The following information may help to resolve the situation: 
-  
-  The following packages have unmet dependencies:
-   linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge 
(= 5.0.0.8.66) but it is not going to be installed
-  E: Unable to correct problems, you have held broken packages.
+  Reading package lists...
+  Building dependency tree...
+  Reading state information...
+  Some packages could not be installed. This may mean that you have
+  requested an impossible situation or if you are using the unstable
+  distribution that some required packages have not yet been created
+  or been moved out of Incoming.
+  The following information may help to resolve the situation:
+ 
+  The following packages have unmet dependencies:
+   linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge 
(= 5.0.0.8.66) but it is not going to be installed
+  E: Unable to correct problems, you have held broken packages.
+ 
+ More check on this:
+ # apt-get install linux-image-generic-hwe-18.04-edge
+ Reading package lists... Done
+ Building dependency tree   
+ Reading state information... Done
+ Some packages could not be installed. This may mean that you have
+ requested an impossible situation or if you are using the unstable
+ distribution that some required packages have not yet been created
+ or been moved out of Incoming.
+ The following information may help to resolve the situation:
+ 
+ The following packages have unmet dependencies:
+  linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic 
but it is not installable
+ E: Unable to correct problems, you have held broken packages.
  
  
  It works well with PowerPC / AMD64 / i386, just not ARM64

** Package changed: linux-meta-hwe-edge (Ubuntu) => linux (Ubuntu)

** Description changed:

- It looks like there are some dependency issue for the ARM64 meta
- package.
+ linux-image-5.0.0-8-generic is not available for ARM64.
  
  # apt-get install --yes linux-generic-hwe-18.04-edge
   Reading package lists...
   Building dependency tree...
   Reading state information...
   Some packages could not be installed. This may mean that you have
   requested an impossible situation or if you are using the unstable
   distribution that some required packages have not yet been created
   or been moved out of Incoming.
   The following information may help to resolve the situation:
  
   The following packages have unmet dependencies:
    linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge 
(= 5.0.0.8.66) but it is not going to be installed
   E: Unable to correct problems, you have held broken packages.
  
  More check on this:
  # apt-get install linux-image-generic-hwe-18.04-edge
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
-  linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic 
but it is not installable
+  linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic 
but it is not installable
  E: Unable to correct problems, you have held broken packages.
  
- 
  It works well with PowerPC / AMD64 / i386, just not ARM64

** This bug has been marked a duplicate of bug 1823994
   arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed

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

Title:
  Unable to install linux-generic-hwe-18.04-edge on ARM64 in -proposed

Status in linux package in Ubuntu:
  New

Bug description:
  linux-image-5.0.0-8-generic is not available for ARM64.

  # apt-get install --yes linux-generic-hwe-18.04-edge
   Reading package lists...
   Building dependency tree...
   Reading state information...
   Some packages could not be installed. This may mean that you have
   requested an impossible situation or if you are using the unstable
   distribution that some required packages have not yet

[Kernel-packages] [Bug 1824038] Re: Network adapter doesn't work after returning from suspend

Ok, please raise the issue to the maintainer and mailing list:
hkallwe...@gmail.com
net...@vger.kernel.org
linux-ker...@vger.kernel.org

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

Title:
  Network adapter doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic
  #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter
  does not resume after suspend. Wifi not available.

  References to a fix for r8169 driver found. Tried the following fixes:
  1. sudo service network-manager restart. This did not work.
  2. Script in /lib/systemd/system-sleep/r8169-refresh as described in 
https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend
 This did not work.
  3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 
fixes in version 4.21, but this is not available on the ubuntu mainline kernels 
https://kernel.ubuntu.com/~kernel-ppa/mainline/

  
  Possibly related to bug #1752772
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.17-042017-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1812845] Re: 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes triggers system hang on i386

Test 3b080b2564287be91605bfd1d5ee985696e61d3c and
5fbc7c59fd22c5a6531b40b0759624b680a95e52 and have passed on X-i386 (node
pepe)

** Attachment added: "X-i386.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812845/+attachment/5254620/+files/X-i386.log

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

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

Title:
  3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
  triggers system hang on i386

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * Parity page in btrfs raid56 is incorrectly unmapped, allowing to
  easily trigger a reference counter bug on i386 causing a kernel panic

   * The fix unmaps the right rbio pages and adds the proper kunmap()
  call for the parity page

  [Test Case]

   * create a raid5 btrfs filesystem:
     # mkfs.btrfs -m raid5 -d raid5 /dev/sdb /dev/sdc /dev/sdd /dev/sde

   * mount it:
     # mount /dev/sdb /mnt

   * run btrfs scrub in a loop:
     # while :; do btrfs scrub start -BR /mnt; done

  [Fix]

   *
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3897b6f0a859288c22fb793fad11ec2327e60fcd

  kunmap(p_page) was completely left out, so we never
  did an unmap for the p_page and the loop unmapping the rbio page was
  iterating over the wrong number of stripes: unmapping should be done
  with nr_data instead of rbio->real_stripes.

  [Regression Potential]

   * This is an upstream fix, tested on the affected platform. The bug
  is affecting only btrfs raid5/6 users on architectures where kunamp()
  is not a no-op (like i386). It is also a very small patch, so backport
  changes are minimal.

  [Original bug report]

  This issue was not spotted on AMD64

  Reproduce rate: 100%

  The following command is the key to trigger this:
  btrfs scrub start -BR $MNT

  Steps:
  # (Install necessary packages)
  # git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  # TMP=/tmp/tmp MNT=/tmp/mnt
  # mkdir -p $TMP; mkdir -p $MNT
  # cd autotest-client-tests/ubuntu_btrfs_kernel_fixes
  # TMP=/tmp/tmp MNT=/tmp/mnt ./3b080b2564287be91605bfd1d5ee985696e61d3c.sh

  Trace:
   [  494.357824] [ cut here ]
   [  494.357828] kernel BUG at 
/build/linux-bnzN1b/linux-4.15.0/mm/highmem.c:350!
   [  494.365079] invalid opcode:  [#1] SMP
   [  494.369205] Modules linked in: cfg80211 intel_powerclamp ipmi_ssif 
gpio_ich coretemp kvm_intel kvm ipmi_si irqbypass input_leds joydev dcdbas 
intel_cstate ipmi_devintf sch_fq_codel shpchp i7core_edac lpc_ich 
ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ttm drm_kms_helper hid_generic syscopyarea sysfillrect usbhid 
sysimgblt mpt3sas fb_sys_fops drm hid raid_class bnx2 scsi_transport_sas 
pata_acpi wmi
   [  494.430188] CPU: 2 PID: 2093 Comm: kworker/u16:1 Not tainted 
4.15.0-43-generic #46-Ubuntu
   [  494.438618] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 
09/18/2012
   [  494.446494] Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper 
[btrfs]
   [  494.453657] EIP: kunmap_high+0xaa/0xb0
   [  494.457571] EFLAGS: 00010246 CPU: 2
   [  494.461229] EAX: 0115 EBX: f000 ECX: 0001 EDX: 
   [  494.467840] ESI: 0004 EDI: 0004 EBP: f4883e44 ESP: f4883e40
   [  494.474264]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
   [  494.479931] CR0: 80050033 CR2: 005885e0 CR3: 0fe16000 CR4: 06f0
   [  494.486353] Call Trace:
   [  494.488967]  kunmap+0x3e/0x50
   [  494.492140]  finish_parity_scrub+0x24d/0x570 [btrfs]
   [  494.497226]  ? update_load_avg+0x64f/0x830
   [  494.501528]  validate_rbio_for_parity_scrub+0xc2/0xd0 [btrfs]
   [  494.507527]  raid56_parity_scrub_end_io+0x53/0x70 [btrfs]
   [  494.513058]  bio_endio+0xb9/0x110
   [  494.516574]  ? end_workqueue_fn+0x2c/0x40 [btrfs]
   [  494.521435]  end_workqueue_fn+0x33/0x40 [btrfs]
   [  494.526139]  normal_work_helper+0x7d/0x2f0 [btrfs]
   [  494.531087]  btrfs_endio_raid56_helper+0x10/0x20 [btrfs]
   [  494.536621]  process_one_work+0x1b9/0x3d0
   [  494.540799]  worker_thread+0x37/0x420
   [  494.544628]  kthread+0xf0/0x110
   [  494.547931]  ? process_one_work+0x3d0/0x3d0
   [  494.552282]  ? kthread_create_worker_on_cpu+0x20/0x20
   [  494.5

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw

OK I think I've figured it out; the cloud images use the -virtual
kernel, which does not install linux-modules-extra-*.

If I install the -generic kernel or just the extra modules and reboot,
then iptables commands start working again.

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

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

** Summary changed:

- disco: unable to enable ufw
+ disco: unable to enable ufw under -virtual kernel

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

Title:
  disco: unable to enable ufw under -virtual kernel

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

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1740231] Re: Add support for Realtek WiFi device [10ec:c821]

2019-04-10 Thread ihsan

thank you

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

Title:
  Add support for Realtek WiFi device [10ec:c821]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

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

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

[Kernel-packages] [Bug 1824038] Re: Network adapter doesn't work after returning from suspend

2019-04-10 Thread Gordon Dracup

Can you tell me how I would do that. I added the first name to the
subscription list, but I can't do it with the second two.

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

Title:
  Network adapter doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic
  #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter
  does not resume after suspend. Wifi not available.

  References to a fix for r8169 driver found. Tried the following fixes:
  1. sudo service network-manager restart. This did not work.
  2. Script in /lib/systemd/system-sleep/r8169-refresh as described in 
https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend
 This did not work.
  3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 
fixes in version 4.21, but this is not available on the ubuntu mainline kernels 
https://kernel.ubuntu.com/~kernel-ppa/mainline/

  
  Possibly related to bug #1752772
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.17-042017-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

--- Comment From p...@au1.ibm.com 2019-04-10 04:10 EDT---
(In reply to comment #66)
> Stefan NACK'ed the series. For some unknown reason that email did make it
> into the archive so here is ist content:
>
> > Since commit fb1522e099f0 ("KVM: update to new mmu_notifier semantic
> > v2", 2017-08-31), the MMU notifier code in KVM no longer calls the
> > kvm_unmap_hva callback.  This removes the PPC implementations of
> > kvm_unmap_hva().
>
> This is not really the way SRUs should be done. We cannot remove support for
> interfaces after release. Also the amount of change as a requisite should be
> kept as minimal as possible. This just feels like too many changes without a
> strong argument on why this must be done that way.
>
> -Stefan

Well it was just removing dead code, but whatever.

The series should be fine without that patch.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

This might have some implications for fan usage on cloud instances as I
see some fan-* rules post switch to generic kernel.

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

Title:
  disco: unable to enable ufw under -virtual kernel

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

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

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

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

apport-collect 1823862

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

Title:
  disco: unable to enable ufw under -virtual kernel

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

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

Dropping ufw from the test case - just running sudo iptables-save
against the virtual kernel produces no output.

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

Title:
  disco: unable to enable ufw under -virtual kernel

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

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

Diff between two identical instances, one with -generic and one with
-virtual.

iptables* commands working find with -generic.

** Attachment added: "kernel-diff.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+attachment/5254621/+files/kernel-diff.txt

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

Title:
  disco: unable to enable ufw under -virtual kernel

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

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1824101] [NEW] [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

You have been subscribed to a public bug:

If commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568 (RDMA) is applied, 
the corresponding SMC patch also have to be applied.


Problem Description:
RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr 

Symptom: 
An SMC-R connection cannot be established. The GID value transferred in the 
confirm_link message is empty (i.e. binary zero).

Problem:
A change in the RDMA subsystem requires to update the way  to retrieve the GID 
of an RDMA device.

Upstream-ID:   b4c296f9c96420b8e7e92466ea5960f10ee20aae
Component  :  kernel

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-176721 severity-high 
targetmilestone-inin---
-- 
[Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr
https://bugs.launchpad.net/bugs/1824101
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 1824101] [NEW] [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

Public bug reported:

If commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568 (RDMA) is applied, 
the corresponding SMC patch also have to be applied.


Problem Description:
RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr 

Symptom: 
An SMC-R connection cannot be established. The GID value transferred in the 
confirm_link message is empty (i.e. binary zero).

Problem:
A change in the RDMA subsystem requires to update the way  to retrieve the GID 
of an RDMA device.

Upstream-ID:   b4c296f9c96420b8e7e92466ea5960f10ee20aae
Component  :  kernel

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-176721 severity-high 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-176721 severity-high
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: 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/1824101

Title:
  [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

Status in linux package in Ubuntu:
  New

Bug description:
  If commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568 (RDMA) is applied, 
  the corresponding SMC patch also have to be applied.

  
  Problem Description:
  RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr 

  Symptom: 
  An SMC-R connection cannot be established. The GID value transferred in the 
confirm_link message is empty (i.e. binary zero).

  Problem:
  A change in the RDMA subsystem requires to update the way  to retrieve the 
GID of an RDMA device.

  Upstream-ID:   b4c296f9c96420b8e7e92466ea5960f10ee20aae
  Component  :  kernel

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

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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)
  
  -- 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:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-candidate: 'Pending -- snap pc-kernel not in expected 
channel(s):
- amd64:latest/candidate i386:latest/candidate'
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/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:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-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 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 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)

  -- 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:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
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/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 1730331] Re: ath10k_pci: firmware crashed!

2019-04-10 Thread Steph Gosling

I have had some success (3 suspends now and not a crash) by using a
newer version of the firmware from upstream, specifically this version:
https://github.com/kvalo/ath10k-
firmware/blob/master/QCA6174/hw3.0/4.4.1.c2/firmware-6.bin_RM.4.4.1.c2-00057-QCARMSWP-1

Download that, and replace the file
/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin with it then rebuild
your initrd (update-initramfs -uk all) and reboot. Obviously that is not
going to survive an upgrade of linux-firmware when it comes, but that
version works for me, at least.

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

Title:
  ath10k_pci: firmware crashed!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware package in Fedora:
  Unknown

Bug description:
  ...
  Nov  4 18:35:50 akane kernel: [   10.216896] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   10.216908] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   10.217641] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   10.228600] kvm: Nested Virtualization 
enabled
  Nov  4 18:35:50 akane kernel: [   10.228611] kvm: Nested Paging enabled
  Nov  4 18:35:50 akane kernel: [   10.258913] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   10.263535] MCE: In-kernel MCE decoding 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271401] EDAC amd64: Node 0: DRAM ECC 
enabled.
  Nov  4 18:35:50 akane kernel: [   10.271416] EDAC amd64: F16h_M30h detected 
(node 0).
  Nov  4 18:35:50 akane kernel: [   10.271491] EDAC MC: DCT0 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271494] EDAC amd64: MC: 0:  4096MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271523] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271526] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271528] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271530] EDAC MC: DCT1 chip selects:
  Nov  4 18:35:50 akane kernel: [   10.271532] EDAC amd64: MC: 0: 0MB 1:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271534] EDAC amd64: MC: 2: 0MB 3:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271537] EDAC amd64: MC: 4: 0MB 5:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271539] EDAC amd64: MC: 6: 0MB 7:
 0MB
  Nov  4 18:35:50 akane kernel: [   10.271541] EDAC amd64: using x4 syndromes.
  Nov  4 18:35:50 akane kernel: [   10.271542] EDAC amd64: MCT channel count: 1
  Nov  4 18:35:50 akane kernel: [   10.271829] EDAC MC0: Giving out device to 
module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT)
  Nov  4 18:35:50 akane kernel: [   10.271892] EDAC PCI0: Giving out device to 
module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED)
  Nov  4 18:35:50 akane kernel: [   10.271894] AMD64 EDAC driver v3.5.0
  Nov  4 18:35:50 akane kernel: [   10.532131] EXT4-fs (sdc1): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
  Nov  4 18:35:50 akane kernel: [   10.575859] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
  Nov  4 18:35:50 akane kernel: [   11.397803] ath10k_pci :04:00.0: 
firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa)
  Nov  4 18:35:50 akane kernel: [   11.407389] ath10k_pci :04:00.0: qca988x 
hw2.0 target 0x4100016c chip_id 0x043222ff sub :
  Nov  4 18:35:50 akane kernel: [   11.407395] ath10k_pci :04:00.0: kconfig 
debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
  Nov  4 18:35:50 akane kernel: [   11.408085] ath10k_pci :04:00.0: 
firmware ver 10.2.4.70.63-2 api 5 features 
no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
  Nov  4 18:35:50 akane kernel: [   11.408148] ath10k_pci :04:00.0: 
board_file api 1 bmi_id N/A crc32 bebc7c08
  Nov  4 18:35:50 akane kernel: [   11.408156] ath10k_pci :04:00.0: htt-ver 
0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
  Nov  4 18:35:50 akane kernel: [   11.410197] ath10k_pci :04:00.0: 
firmware register dump:
  Nov  4 18:35:50 akane kernel: [   11.416213] ath10k_pci :04:00.0: [00]: 
0x4100016C 0x15B3 0x009BFF84 0x00955B31
  Nov  4 18:35:50 akane kernel: [   11.424559] ath10k_pci :04:00.0: [04]: 
0x009BFF84 0x00060130 0x0013 0x
  Nov  4 18:35:50 akane kernel: [   11.432767] ath10k_pci :04:00.0: [08]: 
0x009C8EA4 0x7170 0x0001 0x00435300
  Nov  4 18:35:50 akane kernel: [   11.441059] ath10k_pci :04:00.0: [12]: 
0x0009 0x 0x00958360 0x0095836B
  Nov  4 18:35:50 akane kernel: [   11.4493

[Kernel-packages] [Bug 1824038] Re: Network adapter doesn't work after returning from suspend

Since Heiner Kallweit has an Launchpad account, let's wait for his
reply.

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

Title:
  Network adapter doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic
  #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter
  does not resume after suspend. Wifi not available.

  References to a fix for r8169 driver found. Tried the following fixes:
  1. sudo service network-manager restart. This did not work.
  2. Script in /lib/systemd/system-sleep/r8169-refresh as described in 
https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend
 This did not work.
  3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 
fixes in version 4.21, but this is not available on the ubuntu mainline kernels 
https://kernel.ubuntu.com/~kernel-ppa/mainline/

  
  Possibly related to bug #1752772
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.17-042017-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1824101] Re: [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

2019-04-10 Thread Frank Heimes

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

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

Bug description:
  If commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568 (RDMA) is applied, 
  the corresponding SMC patch also have to be applied.

  
  Problem Description:
  RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr 

  Symptom: 
  An SMC-R connection cannot be established. The GID value transferred in the 
confirm_link message is empty (i.e. binary zero).

  Problem:
  A change in the RDMA subsystem requires to update the way  to retrieve the 
GID of an RDMA device.

  Upstream-ID:   b4c296f9c96420b8e7e92466ea5960f10ee20aae
  Component  :  kernel

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

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

[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

2019-04-10 Thread You-Sheng Yang

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
   Status: In Progress

** Also affects: linux-firmware (Ubuntu Disco)
   Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
   Status: New

** No longer affects: linux (Ubuntu Disco)

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

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

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

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

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

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

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  In Progress
Status in linux-firmware source package in Disco:
  In Progress

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

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

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

[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays

2019-04-10 Thread Georgi Boiko

Updating to 5.0.x does not fix it; it disables the nvidia driver because
that kernel version is not supported in non-bleeding edge drivers yet.
If you update to 5.0.x you will end up with nouveau/intel, depending on
your blacklisting setup.

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

Title:
TB16 dock freezes X on hotplug when used with external displays

Status in Dell Sputnik:
Fix Released
Status in linux package in Ubuntu:
Fix Released

Bug description:
Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux
REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released
12/15/2017. If it can be of any help, I can get this tested on an XPS
9560 (GTX 1050) too.

Steps to reproduce:

1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI
cables are used, but I doubt that it matters.
2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME.
3. Select nVidia GPU in PRIME settings, reboot if needed.
4. Either boot with the dock connected or connect it after booting into user
session.
5. Set up monitors if necessary. At this point everything should be working
fine.
6. Disconnect the dock, give it a moment to adjust to the new window layout
etc.
7. Re-connect the dock. Within a few seconds laptop screen should freeze and
external monitors should remain blank, as if not connected.
8. Disconnect the dock. Within a few seconds laptop screen should unfreeze.
There is a small chance that it won't if you repeat this procedure multiple
times.

Errors in dmesg indicate that i915 driver is somehow involved:

[ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF B idle bit
[ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF C idle bit

The kernel logs are flooded with these between steps 7 and 8 above.

This behaviour does not occur when Intel GPU is selected in PRIME
settings or when nouveau is used. However, nouveau performance leaves
a lot to be desired, particularly with 3D acceleration in Windows 10
VMs.

I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make
any difference.

Other reports that may be related:

https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a
-docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes-
hangs-the-whole-machine/ - same error messages

https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw&sh=40bf8189
- "Connecting and disconnecting the TB16 sometimes freeze the laptop."

https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466
- "Hot-plugging the screen does not work."
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gboiko 2491 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c
InstallationDate: Installed on 2017-10-01 (149 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp.
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic
root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0
biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-36-generic N/A
linux-backports-modules-4.13.0-36-generic N/A
linux-firmware 1.170
Tags: xenial
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.7.0:bd12/15/

[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake

Please follow [1] and see if it helps:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/comments/25

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

Title:
  Wifi + bluetooth adapters are gone after sleep/wake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the only fix I found was to power down and power back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uri2238 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 11:15:43 2019
  HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5
  InstallationDate: Installed on 2018-01-13 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1824103] [NEW] The vioce which recored by Internal microphone gets noisy

2019-04-10 Thread Gabriel Zhi Chen

Public bug reported:

Test machine: ThinkPad X1 Carbon
Image: Ubuntu Disco 19.04
CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
BIOS: N23ET55W (1.30 )

Steps:
1. Install image 19.04
2. Login as default user
3. Open a terminal and type "$ arecord test.wav"
4. Say something and let laptop recorded your words
5. Cancel the record, please press 'Ctrl + C'
6. Please type "$ aplay test.wav" in terminal
7. Verify the quality of the voice.

Expected result:
The voice played smoothly.

Actual result:
The voice is noisy and fuzz.

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


** Tags: ce-qa-concern disco hwe-audio

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1824103/+attachment/5254627/+files/alsa-info.txt

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

Title:
  The vioce which recored by Internal microphone gets noisy

Status in linux package in Ubuntu:
  New

Bug description:
  Test machine: ThinkPad X1 Carbon
  Image: Ubuntu Disco 19.04
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
  BIOS: N23ET55W (1.30 )

  Steps:
  1. Install image 19.04
  2. Login as default user
  3. Open a terminal and type "$ arecord test.wav"
  4. Say something and let laptop recorded your words
  5. Cancel the record, please press 'Ctrl + C'
  6. Please type "$ aplay test.wav" in terminal
  7. Verify the quality of the voice.

  Expected result:
  The voice played smoothly.

  Actual result:
  The voice is noisy and fuzz.

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

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

[Kernel-packages] [Bug 1824103] Re: The vioce which recored by Internal microphone gets noisy

2019-04-10 Thread Gabriel Zhi Chen

** Attachment added: "dmidecode.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824103/+attachment/5254629/+files/dmidecode.log

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

Title:
  The vioce which recored by Internal microphone gets noisy

Status in linux package in Ubuntu:
  New

Bug description:
  Test machine: ThinkPad X1 Carbon
  Image: Ubuntu Disco 19.04
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
  BIOS: N23ET55W (1.30 )

  Steps:
  1. Install image 19.04
  2. Login as default user
  3. Open a terminal and type "$ arecord test.wav"
  4. Say something and let laptop recorded your words
  5. Cancel the record, please press 'Ctrl + C'
  6. Please type "$ aplay test.wav" in terminal
  7. Verify the quality of the voice.

  Expected result:
  The voice played smoothly.

  Actual result:
  The voice is noisy and fuzz.

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

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

[Kernel-packages] [Bug 1824103] Re: The vioce which recored by Internal microphone gets noisy

2019-04-10 Thread Gabriel Zhi Chen

** Attachment added: "acpidump.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824103/+attachment/5254628/+files/acpidump.log

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

Title:
  The vioce which recored by Internal microphone gets noisy

Status in linux package in Ubuntu:
  New

Bug description:
  Test machine: ThinkPad X1 Carbon
  Image: Ubuntu Disco 19.04
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
  BIOS: N23ET55W (1.30 )

  Steps:
  1. Install image 19.04
  2. Login as default user
  3. Open a terminal and type "$ arecord test.wav"
  4. Say something and let laptop recorded your words
  5. Cancel the record, please press 'Ctrl + C'
  6. Please type "$ aplay test.wav" in terminal
  7. Verify the quality of the voice.

  Expected result:
  The voice played smoothly.

  Actual result:
  The voice is noisy and fuzz.

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

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

Please follow [1] and see if it helps:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/comments/25

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

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

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

** Patch added: "0001-disable-BLE-advertisment.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988/+attachment/5254630/+files/0001-disable-BLE-advertisment.patch

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

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

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

** Patch added: "0002-d3delay.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988/+attachment/5254631/+files/0002-d3delay.patch

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

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

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

For those who don't use Ubuntu, here are changes that _may_ help the situation:
1) Commit d7a6c0ce8d26412903c7981503bad9e1cc7c45d2 ("USB: Consolidate LPM 
checks to avoid enabling LPM twice").
This can fix this error:
[ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin
[ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)

2) 0001-disable-BLE-advertisment.patch
This patch can avoid this:
[25782.016682] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
[25782.016691] dpm_run_callback(): pci_pm_suspend+0x0/0x130 returns -16
[25782.016694] PM: Device :00:14.0 failed to suspend async: error -16
[25782.920799] PM: Some devices failed to suspend, or early wake event detected
[25782.922906] usb usb1-port7: status 0103 change 0004

3) 0002-d3delay.patch
Just a random attempt to see if it helps.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

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

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

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

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

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

Title:
  linux-aws: 4.4.0-1041.44 -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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: Ready for Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 01:09 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1790801] Re: Ubuntu 18.04 touchppad does not work smoothly in Lenono Thinkpad

Does this still happen to your system?

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

Title:
  Ubuntu 18.04 touchppad does not work smoothly in Lenono Thinkpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hallo,
  The touchpad is not working after installing Ubuntu 18.04.1 LTS in Lenovo 
Thinkpad laptop. After a lot of googling and trying around, I managed to make 
it work in the sense that i could move cursor here and there, but still it has 
numbers of problems. Here is the list of problems it still has:
  1. The scrolling does not work at all, it never worked.

  2. It is dead after each restart and I have to provide this commands to make 
it work, so that the cursor could move. 
sudo modprobe -rv psmouse
sudo modprobe -v psmouse proto=imps

  3. The typing of the keyboard does not work smoothly, which make me really 
difficult to work. For example: I ended up typing this
  ''he list Here is the pr to repoty I want thatoblem of t''
when I want to type:
  'Here is the list of problems that I want to report'

  4. The left and right touch is really hard.

  Here is the information on my touchpad
  1. pooja@pooja-thinkpad-x1:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech Optical USB Mouse  id=9[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Synaptics TouchPad id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=11   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=13   [slave  
keyboard (3)]

  2. pooja@pooja-thinkpad-x1:~$ xinput list 12
  PS/2 Synaptics TouchPad   id=12   [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 12. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right"
Button state:
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Scroll
  Range: -1.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 15.00
  flags: 0x0
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: 15.00
  flags: 0x0

  3. pooja@pooja-thinkpad-x1:~$ sudo xinput set-prop 12 "libinput Natural 
Scrolling Enabled Default" 1
  [sudo] password for pooja: 
  X Error of failed request:  BadAccess (attempt to access private resource 
denied)
Major opcode of failed request:  131 (XInputExtension)
Minor opcode of failed request:  57 ()
Serial number of failed request:  20
Current serial number in output stream:  21

  4. I realized that before my touchpad was differently written as now.
  pooja@pooja-ThinkPad-X1-Carbon-6th:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech Optical USB Mouse

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

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

apport-collect 1824103

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

Title:
  The vioce which recored by Internal microphone gets noisy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Test machine: ThinkPad X1 Carbon
  Image: Ubuntu Disco 19.04
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
  BIOS: N23ET55W (1.30 )

  Steps:
  1. Install image 19.04
  2. Login as default user
  3. Open a terminal and type "$ arecord test.wav"
  4. Say something and let laptop recorded your words
  5. Cancel the record, please press 'Ctrl + C'
  6. Please type "$ aplay test.wav" in terminal
  7. Verify the quality of the voice.

  Expected result:
  The voice played smoothly.

  Actual result:
  The voice is noisy and fuzz.

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

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

[Kernel-packages] [Bug 1821597] Re: USB suspend / resume with docking station and laptop lid closed

Possible to update the BIOS to its latest version (A25)?

Changelog for A18 says:
- Improved USB access stability.

So it may help.

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

Title:
  USB suspend / resume with docking station and laptop lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The components:
  - Dell Precision M4800 laptop
  - Dell docking station, with USB keyboard attached

  Ubuntu 16.04 installed

  Test case A) Booting in Docking Station with laptop lid closed:
  ===
  Boot will proceed through unlocking disk encryption. When graphical user 
interface starts, screen will go black and start spewing `unable to enumerate 
USB device on port` messages

  Test case B) In docking station, close lid and resume:
  =
  (Boot sequence done with laptop lid open)
  If laptop lid is closed before resuming from suspend, screen will soon go 
black and start spewing `unable to enumerate USB device on port` messages

  Test case C) Suspend without docking station (this one works):
  ==
  1. Boot to laptop without docking station attached
  2. Suspend
  3. Attach to docking station with lid closed
  4. Resume

  C) is currently the only case where everything works properly.
  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eja4634 F pulseaudio
   /dev/snd/controlC0:  eja4634 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2014-09-24 (1644 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision M4800
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic 
root=/dev/mapper/vgcrypt-lvcryptoroot ro 
cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt
 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-143-generic N/A
   linux-backports-modules-4.4.0-143-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-143-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2017-02-08 (775 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0FVDR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

** 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: Ready for Promote to Proposed
- phase-changed: Wednesday, 10. April 2019 01:09 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 09:39 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review 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/1822832

Title:
  linux-aws: 4.4.0-1041.44 -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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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: Wednesday, 10. April 2019 09:39 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/1822832/+subscriptions

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

[Kernel-packages] [Bug 1822826] Re: linux-kvm: 4.4.0-1044.50 -proposed tracker

4.4.0-1044.50 - kvm
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 
1763323)
  ubuntu_kernel_selftests - psock_tpacket in net failed (bug 1812176) test_bpf 
in net (bug 1812189) test_user_copy return code in user (bug 1812352)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx 
(bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) port80 (bug 1748105) 
vmx_apic_passthrough_thread (bug 1822309) smptest, smptest3, eventinj, 
kvmclock_test, pcid failed
  ubuntu_ltp_syscalls - tested failed for nfs-kernel-server issue (bug 1821275)
  ubuntu_lxc - python3 API failed (bug 1764618)
  ubuntu_qrt_kernel_security - SCHED_STACK_END_CHECK should be enabled (bug 
1812159)
  ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535)


** 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 subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1822826

Title:
  linux-kvm: 4.4.0-1044.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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, 05. April 2019 11:38 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/1822826/+subscriptions

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

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

--- Comment From heinz-werner_se...@de.ibm.com 2019-04-10 05:45 EDT---
Requires Firmware update on top - this effort is ongoing and will be tracked by 
a seperate LP-Bugziila

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

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

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

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

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

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

[Kernel-packages] [Bug 1824101] Re: [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

2019-04-10 Thread Frank Heimes

I just looked up these two commits in the disco master tree and found that both 
commits are already tagged with 4.19 - hence they are in disco's latest kernel 
5.0:
$ git show bf399c2cadfa66d399d01d5a92a7bb0a112f1568 | head -n 6
commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568
Author: Parav Pandit 
Date:   Tue Jun 5 08:40:17 2018 +0300

IB/core: Introduce GID attribute get, put and hold APIs

$ git describe --tags --contains bf399c2cadfa66d399d01d5a92a7bb0a112f1568
v4.19~309^2~312
$ git show b4c296f9c96420b8e7e92466ea5960f10ee20aae | head -n 6
commit b4c296f9c96420b8e7e92466ea5960f10ee20aae
Author: Jason Gunthorpe 
Date:   Fri Aug 17 16:45:51 2018 -0600

RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

$ git describe --tags --contains b4c296f9c96420b8e7e92466ea5960f10ee20aae
v4.19~309^2~2
fheimes@T570:~/ubuntu-disco/disco$
Hence closing the ticket as Fix Released.

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

** Changed in: ubuntu-z-systems
   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/1824101

Title:
  [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

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

Bug description:
  If commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568 (RDMA) is applied, 
  the corresponding SMC patch also have to be applied.

  
  Problem Description:
  RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr 

  Symptom: 
  An SMC-R connection cannot be established. The GID value transferred in the 
confirm_link message is empty (i.e. binary zero).

  Problem:
  A change in the RDMA subsystem requires to update the way  to retrieve the 
GID of an RDMA device.

  Upstream-ID:   b4c296f9c96420b8e7e92466ea5960f10ee20aae
  Component  :  kernel

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

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

[Kernel-packages] [Bug 1822826] Re: linux-kvm: 4.4.0-1044.50 -proposed tracker

** 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: Signoff
  phase-changed: Friday, 05. April 2019 11:38 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1822826

Title:
  linux-kvm: 4.4.0-1044.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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, 05. April 2019 11:38 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/1822826/+subscriptions

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

[Kernel-packages] [Bug 1646805] Re: MAC address needs to be unique and unchanged during entire netboot process

2019-04-10 Thread Frank Heimes

FW part is tracked in LP 1824117

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

Title:
  MAC address needs to be unique and unchanged during entire netboot
  process

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

Bug description:
  Currently the MAC address is not solely used to id the machine or system.
  It is at the moment used to id the interface that the MAC represents.
  (At a very early state in the process the MAC address is missing or only 
available from inside the partition.)

  The minimum PXE boot requirements need to be satisfied in general.
  The boot loader is part of the firmware and not loaded from the server.
  So that means the firmware needs to provide the MAC address.
  But the MAC address is not available at that time, so it's not available 
upfront.

  MaaS is using the same MAC address for the initial DHCP request as for the 
network boot.
  Hence an initially known MAC address is required that needs to be static and 
doesn't change (on subsequent boots for that instance).

  There might be an IBM internal ticket already open for this - please
  check.

  Furthermore the firmware needs to requests files like this:
  pxelinux.cfg/01-88-99-aa-bb-cc-dd
  pxelinux.cfg/default
  And BOOTIF support is required:
  See 'petitboot doesn't handle ipappend in pxelinux.cfg'
  https://bugs.launchpad.net/tasty-taco/+bug/1322307
  for reference.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.

2019-04-10 Thread Luca Mastromatteo

Hi, in debian testing this does not happen, neither in debian unstable
or other distros with the same gnome-shell package version

I confirm it's a regression from 18.10 to 19.04

In 18.10 it works fine

-- 
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] After resume the unlock screen is a black background with
  pixel garbage. Bitmap garbage flashes on the screen when interacting
  with anything.

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/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions

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

[Kernel-packages] [Bug 1822870] tarball of patches to fix dd 2.3 spectre issues

--- Comment on attachment From mranw...@us.ibm.com 2019-04-10 06:26 
EDT---


This is the set of patches listed above plus:
2b57ecd0208f KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()

That one is needed for qemu.  There aren't any earlier patches that are
needed.

I tested this out:
mranweil@ltc-wspoon5:~$ dmesg |grep count-cache-flush
[0.00] count-cache-flush: hardware assisted flush sequence enabled
mranweil@ltc-wspoon5:~$ grep -H . 
/sys/devices/system/cpu/vulnerabilities/spectre_v2
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Software count 
cache flush (hardware acceleratd)
mranweil@ltc-wspoon5:~$ 

6:mon> di $_switch 20
c000db00  7c0802a6  mflrr0
c000db04  f8010010  std r0,16(r1)
c000db08  f821fe31  stdur1,-464(r1)
c000db0c  f9c100e0  std r14,224(r1)
c000db10  f9e100e8  std r15,232(r1)
c000db14  fa0100f0  std r16,240(r1)
c000db18  fa2100f8  std r17,248(r1)
c000db1c  fa410100  std r18,256(r1)
c000db20  fa610108  std r19,264(r1)
c000db24  fa810110  std r20,272(r1)
c000db28  faa10118  std r21,280(r1)
c000db2c  fac10120  std r22,288(r1)
c000db30  fae10128  std r23,296(r1)
c000db34  fb010130  std r24,304(r1)
c000db38  fb210138  std r25,312(r1)
c000db3c  fb410140  std r26,320(r1)
c000db40  fb610148  std r27,328(r1)
c000db44  fb810150  std r28,336(r1)
c000db48  fba10158  std r29,344(r1)
c000db4c  fbc10160  std r30,352(r1)
c000db50  fbe10168  std r31,360(r1)
c000db54  f8010170  std r0,368(r1)
c000db58  7ee00026  mfcrr23
c000db5c  fae101a0  std r23,416(r1)
c000db60  f823  std r1,0(r3)
c000db64  4bffdb1d  bl  c000b680# 
flush_count_cache+0x0/0x2480
c000db68  3cc06000  lis r6,24576
c000db6c  7d40322c  dcbt0,r6,10
c000db70  38c4f4d0  addir6,r4,-2864
c000db74  f8cd0260  std r6,608(r13)
c000db78  e904  ld  r8,0(r4)
c000db7c  4864  b   c000dbe0# 
_switch+0xe0/0x180
6:mon> di $flush_count_cache 4d
c000b680  7d2802a6  mflrr9
c000b684  4805  bl  c000b688# 
flush_count_cache+0x8/0x2480
 ...
c000b784  481c  b   c000b7a0# 
flush_count_cache+0x120/0x2480
c000b788  6000  nop
 ...
c000b7a0  7d2803a6  mtlrr9
c000b7a4  39207fff  li  r9,32767
c000b7a8  7d2903a6  mtctr   r9
c000b7ac  4c400420  bcctr-  2,lt
c000b7b0  4e800020  blr
6:mon>

** Attachment added: "tarball of patches to fix dd 2.3 spectre issues"
   
https://bugs.launchpad.net/bugs/1822870/+attachment/5254646/+files/bionic-dd23spectre-20.tgz

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-04-10 Thread Thees Flatow

Suffering from weak rtl8723be wifi signal and new to proposed updates.

What I have done:

1. Make sure there are no more updates from non-propopsed sources (main, 
universe).
2. Enable proposed updates in GUI (this updates package list automatically).
3. back to command-line (just to feel safe): $ sudo apt-get update
4. $ sudo apt-get install linux-image-generic/bionic-proposed
5. $ sudo reboot

Weak signal! :-(

$ uname -a
Linux a12 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
$ dpkg -l | grep linux-image
ii  linux-image-4.15.0-20-generic 4.15.0-20.21  
  amd64Signed kernel image generic
ii  linux-image-4.15.0-47-generic 4.15.0-47.50  
  amd64Signed kernel image generic
ii  linux-image-4.15.0-48-generic 4.15.0-48.51  
  amd64Signed kernel image generic
ii  linux-image-generic   4.15.0.48.50  
  amd64Generic Linux kernel image


With ant_sel=2 I do get strong signal, though.  But as that requires manual 
intervention ...

I cannot confirm this bug being solved with kernel in proposed updates.

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

2019-04-10 Thread Bug Watch Updater

** Changed in: dkms (Debian)
   Status: New => Fix Released

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Artful:
  New
Status in dkms package in Debian:
  Fix Released

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-04-10 Thread Thees Flatow

Just to avoid confusion:

I have enabled selective installation of packages from bionic-proposed
as discussed in .  I.e.
there's a step missing:

2.5. Add file `/etc/apt/preferences.d/proposed-updates` with contents

Package: *
Pin: release a=bionic-proposed
Pin-Priority: 400

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1824038] Re: Network adapter doesn't work after returning from suspend

2019-04-10 Thread Heiner Kallweit

This sounds more like a platform issue (especially as WiFi seems to be affected 
too). Few months ago we had something similiar and it turned out to be a 
problem with Intel PCI bridge code.
The only way I see for now is to find a working version and then bisect.

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

Title:
  Network adapter doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic
  #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter
  does not resume after suspend. Wifi not available.

  References to a fix for r8169 driver found. Tried the following fixes:
  1. sudo service network-manager restart. This did not work.
  2. Script in /lib/systemd/system-sleep/r8169-refresh as described in 
https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend
 This did not work.
  3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 
fixes in version 4.21, but this is not available on the ubuntu mainline kernels 
https://kernel.ubuntu.com/~kernel-ppa/mainline/

  
  Possibly related to bug #1752772
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.17-042017-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

--- Comment From heinz-werner_se...@de.ibm.com 2019-04-10 07:27 EDT---
IBM bugzilla status -> closed, not a 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/1824101

Title:
  [Ubuntu] RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr

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

Bug description:
  If commit bf399c2cadfa66d399d01d5a92a7bb0a112f1568 (RDMA) is applied, 
  the corresponding SMC patch also have to be applied.

  
  Problem Description:
  RDMA/smc: Replace ib_query_gid with rdma_get_gid_attr 

  Symptom: 
  An SMC-R connection cannot be established. The GID value transferred in the 
confirm_link message is empty (i.e. binary zero).

  Problem:
  A change in the RDMA subsystem requires to update the way  to retrieve the 
GID of an RDMA device.

  Upstream-ID:   b4c296f9c96420b8e7e92466ea5960f10ee20aae
  Component  :  kernel

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

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

[Kernel-packages] [Bug 1824136] [NEW] ubuntu_k8s_unit_tests failed with GCP

Public bug reported:

There are 4 failures found on Cosmic GCP (n1-highcpu-16)

* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
* k8s.io/kubernetes/pkg/master
* k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy [build 
failed]


Steps to reproduce:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_k8s_unit_tests/control

Error messages:

* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler

 --- FAIL: TestUpdateNodeWithMultiplePods (2.56s)
 taint_manager_test.go:486: Starting testcase "Pods with different toleration 
times are evicted appropriately"
 taint_manager_test.go:512: Sleeping for 499.999448ms
 taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. 
 taint_manager_test.go:538: Found not-delete action with verb list. Ignoring. 
 taint_manager_test.go:512: Sleeping for 594.563805ms
 taint_manager_test.go:532: Failed to deleted pod pod2 after 0
 taint_manager_test.go:486: Starting testcase "Evict all pods not matching all 
taints instantly"
 taint_manager_test.go:512: Sleeping for 499.999844ms
 taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
 taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. 
 taint_manager_test.go:521: Found not-delete action with verb list. Ignoring. 
 taint_manager_test.go:538: Found not-delete action with verb list. Ignoring. 
 FAIL
 FAIL   k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler35.544s

* k8s.io/kubernetes/pkg/master
 2019-03-21 16:02:16.793715 I | integration: launching 2444030890339279063 
(unix://localhost:24440308903392790630)
 2019-03-21 16:02:16.798460 I | etcdserver: name = 2444030890339279063
 2019-03-21 16:02:16.798550 I | etcdserver: data dir = /tmp/etcd396328703
 2019-03-21 16:02:16.798566 I | etcdserver: member dir = 
/tmp/etcd396328703/member
 2019-03-21 16:02:16.798576 I | etcdserver: heartbeat = 10ms
 2019-03-21 16:02:16.798585 I | etcdserver: election = 100ms
 2019-03-21 16:02:16.798594 I | etcdserver: snapshot count = 0
 2019-03-21 16:02:16.798635 I | etcdserver: advertise client URLs = 
unix://127.0.0.1:2100211086
 2019-03-21 16:02:16.798657 I | etcdserver: initial advertise peer URLs = 
unix://127.0.0.1:2100111086
 2019-03-21 16:02:16.798676 I | etcdserver: initial cluster = 
2444030890339279063=unix://127.0.0.1:2100111086
 2019-03-21 16:02:16.804030 I | etcdserver: starting member d951fd13cdcf6e11 in 
cluster b8d26aa038f828d
 2019-03-21 16:02:16.804137 I | raft: d951fd13cdcf6e11 became follower at term 0
 2019-03-21 16:02:16.804164 I | raft: newRaft d951fd13cdcf6e11 [peers: [], 
term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
 2019-03-21 16:02:16.804206 I | raft: d951fd13cdcf6e11 became follower at term 1
 2019-03-21 16:02:16.818807 W | auth: simple token is not cryptographically 
signed
 2019-03-21 16:02:16.822703 I | etcdserver: set snapshot count to default 10
 2019-03-21 16:02:16.822805 I | etcdserver: starting server... [version: 
3.2.13, cluster version: to_be_decided]
 2019-03-21 16:02:16.823182 I | integration: launched 2444030890339279063 
(unix://localhost:24440308903392790630)
 2019-03-21 16:02:16.825229 I | etcdserver/membership: added member 
d951fd13cdcf6e11 [unix://127.0.0.1:2100111086] to cluster b8d26aa038f828d
 2019-03-21 16:02:16.885057 I | raft: d951fd13cdcf6e11 is starting a new 
election at term 1
 2019-03-21 16:02:16.885151 I | raft: d951fd13cdcf6e11 became candidate at term 
2 
 2019-03-21 16:02:16.885168 I | raft: d951fd13cdcf6e11 received MsgVoteResp 
from d951fd13cdcf6e11 at term 2
 2019-03-21 16:02:16.885180 I | raft: d951fd13cdcf6e11 became leader at term 2
 2019-03-21 16:02:16.885187 I | raft: raft.node: d951fd13cdcf6e11 elected 
leader d951fd13cdcf6e11 at term 2
 2019-03-21 16:02:16.885759 I | etcdserver: setting up the initial cluster 
version to 3.2
 2019-03-21 16:02:16.886707 N | etcdserver/membership: set the initial cluster 
version to 3.2
 2019-03-21 16:02:16.886797 I | etcdserver/api: enabled capabilities for 
version 3.2
 2019-03-21 16:02:16.886857 I | etcdserver: published {Name:2444030890339279063 
ClientURLs:[unix://127.0.0.1:2100211086]} to cluster b8d26aa038f828d
 [restful] 2019/03/21 16:02:17 log.go:33: [restful/swagger] listing is 
available at http://192.168.10.4:443/swaggerapi
 [restful] 2019/03/21 16:02:17 log.go:33: [restful/swagger] 
http://192.168.10.4:443/swaggerui/ is mapped to folder /swagger-ui/
 panic: test timed out after 2m0s


Please find the attachment for the complete test log.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1008-gcp 4.18.0-1008.9
ProcVersionSignature: Ubuntu 4.18.0-1008.

[Kernel-packages] [Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker

2019-04-10 Thread Marcelo Cerri

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

** This bug has been marked a duplicate of bug 1824039
   linux-fips: 4.15.0-1004.5 -proposed tracker

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1819716
  phase: Holding before Release
  phase-changed: Friday, 05. April 2019 01:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag 
present

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

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

[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-04-10 Thread Heribert Heckhoff

Well, I have to stand corrected !

Thanks to the hints in #92/#93 I was able to have the proposed kernel
installed.

I have removed the test kernel as of #75 as a prerequisite first !!

I have as well used the apt command as opposed to the Software Updater
UI.

Linux heri-hp-pc 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

heri@heri-hp-pc:~$ dpkg -l | grep linux-image | grep 4.15
ii  linux-image-4.15.0-32-generic   4.15.0-32.35
 amd64Signed kernel image generic
rc  linux-image-4.15.0-34-generic   4.15.0-34.37
 amd64Signed kernel image generic
ii  linux-image-4.15.0-48-generic   4.15.0-48.51
 amd64Signed kernel image generic
ii  linux-image-generic 4.15.0.48.50
 amd64Generic Linux kernel image

I have the hunch that the Software Updater UI got confused, because test
kernel as of #75 was an **unsigned** kernel, as opposed to the kernel
from proposed, which is a **signed** kernel.

Anyhow, I consider the problem as resolved, as the proposed kernel works
as good as 4.15.0-32, which only showed a reasonable WIFI signal with
ant_sel=2.

So changing tag to verification-done-bionic.


** Tags removed: verification-failed-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/1788997

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-candidate: 'Pending -- snap pc-kernel not in expected 
channel(s):
- amd64:18/candidate armhf:18/candidate i386:18/candidate'
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/1822820

Title:
  linux: 4.15.0-48.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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-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 package in Ubuntu:
  Invalid
Status in linux 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 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822981 (linux), bug 1823254 
(linux), bug 1823755 (linux-gke), bug 1824039 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
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/1822820/+subscriptions

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

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

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

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

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

** Description changed:

  This bug 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 1822807 (xenial/linux-gcp)
  
  -- swm properties --
  kernel-stable-master-bug: 1822820
- phase: Packaging
- phase-changed: Monday, 08. April 2019 16:07 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 12:06 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Holding -- builds not complete

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 1822807 (xenial/linux-gcp)

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 12:06 UTC
  reason:
promote-to-proposed: Holding -- builds not complete

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1822808
- phase: Holding before Packaging
- phase-changed: Tuesday, 02. April 2019 15:05 UTC
+ phase: Ready for Packaging
+ phase-changed: Wednesday, 10. April 2019 12:12 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified

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

Title:
  linux-gcp:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1822808
  phase: Ready for Packaging
  phase-changed: Wednesday, 10. April 2019 12:12 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

** 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: 1821724
  phase: Holding before Release
  phase-changed: Thursday, 04. April 2019 03:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag 
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/1820326

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1821724
  phase: Holding before Release
  phase-changed: Thursday, 04. April 2019 03:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-04-10 Thread 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1799988

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

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

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

** Description changed:

- Launching a recent daily image of disco on azure results in a VM in
- which the hv-kvp-daemon.service fails to start:
+ SRU Justification
+ 
+ Impact: The KVP daemon fails to start on first boot due to being started
+ before the hv_kvp device appears.
+ 
+ Fix: Update the hv-kvp-daemon service file to start the daemon after
+ device node appears.
+ 
+ Regression Potential: The changes are only to the hv-kvp-daemon service
+ file and adding a udev rule, so the worst case regression would be that
+ the service does not start. In testing the service did start as
+ expected.
+ 
+ Test Case: See comment #15.
+ 
+ ---
+ 
+ 
+ Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:
  
  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
-Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
-Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
-  Main PID: 219 (code=exited, status=1/FAILURE)
+    Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
+    Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
+  Main PID: 219 (code=exited, status=1/FAILURE)
  
  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.
  
- 
  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313
  
  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
- --- 
+ ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-1011-azure N/A
-  linux-backports-modules-4.18.0-1011-azure  N/A
-  linux-firmware N/A
+  linux-restricted-modules-4.18.0-1011-azure N/A
+  linux-backports-modules-4.18.0-1011-azure  N/A
+  linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon

[Kernel-packages] [Bug 1776563]

2019-04-10 Thread erikjohansson

With bios/UEFI 1.13 and kernel 5.0.7 things seems to work.
I got touchpad working by installing https://github.com/Syniurge/i2c-amd-mp2 
(master works, the wip-v16 doesn't work and screwed up a lot of things when i 
tried it so don't try that version).

git clone https://github.com/Syniurge/i2c-amd-mp2.git master
mv master i2c-amd-mp2
cd i2c-amd-mp2
LANG=C sudo ./dkms-install.sh

First i booted with pci=noacpi and with that touchpad wasn't working with bios 
1.13 that uses advanced touchpad, it did work with earlier bios that had basic 
option for touchpad.
Removing pci=acpi and instead using:
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
did the trick for me.

I sometimes needs to toogle wifi after suspend, i haven't tried hibernate.
My laptop is an A315-41 non G but it think the G only means that it also has a 
dedicated graphicscard.
I haven't tried it out much yet but at least things seems to work now.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1776563]

2019-04-10 Thread erikjohansson

I forgot to add that some distributions may include i2c-amd-mp2 built in to the 
kernel and that may be an older non working version.
If that's the case then you need to rebuild the kernel without the patched 
i2c-amd-mp2 support and then you can add i2c-amd-mp2 as i posted in previous 
post.
I compiled an non patched vanilla kernel with a custom .conf and then added 
i2c-amd-mp2 support.
It do work with an non patched vanilla kernel, some distributions patches the 
kernel so much that i may be the reason that things doesn't work.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1823221] Re: linux-gcp: 5.0.0-1002.2 -proposed tracker

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 5.0.0-1002.2 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux-gcp: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  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 --
  kernel-stable-master-bug: 1823936
  phase: Holding before Packaging
  phase-changed: Thursday, 04. April 2019 19:39 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

2019-04-10 Thread Stefan Bader

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1822808
  phase: Ready for Packaging
  phase-changed: Wednesday, 10. April 2019 12:12 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

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

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** 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 --
  kernel-stable-master-bug: 1822808
- phase: Ready for Packaging
- phase-changed: Wednesday, 10. April 2019 12:12 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 10. April 2019 13:11 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1822808
  phase: Packaging
  phase-changed: Wednesday, 10. April 2019 13:11 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1823221] Re: linux-gcp: 5.0.0-1002.2 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1823936
- phase: Holding before Packaging
- phase-changed: Thursday, 04. April 2019 19:39 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 10. April 2019 13:10 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-gcp: 5.0.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  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 --
  kernel-stable-master-bug: 1823936
  phase: Packaging
  phase-changed: Wednesday, 10. April 2019 13:10 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

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

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

Marking the ufw task as Invalid. The kernel doesn't have what is needed
to run iptables.

** Changed in: ufw (Ubuntu)
   Status: New => Invalid

** Changed in: ufw (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

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

Title:
  disco: unable to enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

I can confirm that without linux-modules-extra-*, iptables is broken.

Reduced test case:
$ sudo iptables -L -n
iptables: No chain/target/match by that name.

Full test case:
$ sudo /usr/share/ufw/check-requirements -f
...
ERROR: could not create 'ufw-check-requirements'. Aborting
FAIL: check your kernel and that you have iptables >= 1.4.0

Perhaps the above should be added to image smoke tests?

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

** Summary changed:

- disco: unable to enable ufw under -virtual kernel
+ disco: unable to use iptables/enable ufw under -virtual kernel

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Confirmed
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-04-10 Thread Andrew Cloke

In comment #22 above, it states that "In a meeting with lagarcia, I was
informed this patch is very important, and that it is already on kernel
4.18-15 onwards."

So, I assume that the required patchset(s) are already applied to the
18.04 HWE kernel, and this bug requests a backport to the bionic 4.15
kernel.

Next step is for the Canonical kernel team to analyse this backport
request, dropping the commit fb1522e099f0 ("KVM: update to new
mmu_notifier semantic v2", 2017-08-31), to assess whether it can be
SRU'ed into the bionic 4.15 kernel.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

FYI, I saw this when looking at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862. In the
other bug, the reporter say a different error message, but I saw
'iptables v1.6.1: can't initialize iptables table `filter': Memory
allocation problem'. If those in this bug do not have linux-modules-
extra-5.0.0-8-generic installed, then this is a dupe of the other 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/1820114

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 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
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

To be clear, when I installed linux-modules-extra-5.0.0-8-generic, I no
longer saw this error message. Of course, it might not strictly be a
duplicate, but I'll let the kernel team figure that out.

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 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
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1795659] Re: kernel panic using CIFS share smb2_push_mandatory_locks

2019-04-10 Thread Guilherme G. Piccoli

Thanks for reporting that Stefan! There's a Debian bug report (although the 
kernel
version is different, seems the same issue): 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830771 .

Also, recently I had a report of this issue happening in Azure instance,
kernel version 4.15.0-1041-azure.

Cheers,


Guilherme

** Bug watch added: Debian Bug tracker #830771
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830771

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  kernel panic using CIFS share smb2_push_mandatory_locks

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

Bug description:
  Description:Ubuntu 16.04.5 LTS
  Release:16.04

  Kernel: 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Under load, getting a system crash when accessing files on an SMB3
  share. dmesg from crash attached. I can upload the crash dump if
  needed.

  Share is mounted with the following options:

  
"ro,_netdev,username=*,password=*,domain=*,vers=3.02,sec=ntlmsspi,nounix,noserverino,nobrl,cache=none"

  Dmesg points to the cifs module

  [ 2192.662345] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [ 2192.662407] IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]

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

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

[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

2019-04-10 Thread Dan Watkins

I can also confirm that installing linux-modules-extra-5.0.0-8-generic
(which also pulls in crda iw libnl-genl-3-200 wireless-regdb) caused
this problem to no longer appear.

(I'm happy for this to be marked duplicate, but I wonder if there's
still an iptables bug, given that memory allocation is perhaps not the
real problem it's hitting?)

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 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
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1776563]

2019-04-10 Thread kgs.void

"Things seem to work" is a bit confusing here. Can you boot without any
parameters? Because it worked with parameters before the bios/kernel
patches..

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1824038] Re: Network adapter doesn't work after returning from suspend

Looks like it has a Haswell CPU, so older kernels should be able to work
on this system.

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

Title:
  Network adapter doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Ubuntu 18.04 (Linux kernel 4.18.0-17-generic
  #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:12 UTC 2019). Network adapter
  does not resume after suspend. Wifi not available.

  References to a fix for r8169 driver found. Tried the following fixes:
  1. sudo service network-manager restart. This did not work.
  2. Script in /lib/systemd/system-sleep/r8169-refresh as described in 
https://askubuntu.com/questions/1029250/ubuntu-18-04-ethernet-disconnected-after-suspend
 This did not work.
  3. Updated kernel to 4.20.17. This did not work. There is reference to r8169 
fixes in version 4.21, but this is not available on the ubuntu mainline kernels 
https://kernel.ubuntu.com/~kernel-ppa/mainline/

  
  Possibly related to bug #1752772
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-08 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.17-042017-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

Sorry for not following this - does this still happen?

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

Title:
  [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The screen brightness cannot be changed.

  In 16.04, I could change the brightness via:
  xrandr --output eDP-1 --brightness 0.7

  WORKAROUND: Execute at a terminal:
  xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8

  WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/

  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marvin 1768 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
  MachineType: LENOVO 20FRS2M600
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2M600
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1821390] Re: apic-split will fail in kvm_units_tests

2019-04-10 Thread Sean Feole

affects, 4.18.0-1013.15 linux-aws

** Summary changed:

- apic-split will fail in kvm_units_tests on aws i3.metal 
+ apic-split will fail in kvm_units_tests

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

Title:
  apic-split will fail in kvm_units_tests

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Cosmic:
  Incomplete
Status in linux-aws source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  New

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=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  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/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

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

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

[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

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

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

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

** Description changed:

  This bug 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 --
  kernel-stable-master-bug: 1822808
- phase: Packaging
- phase-changed: Wednesday, 10. April 2019 13:11 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 15:12 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Holding -- builds not complete

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

Title:
  linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1822808
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 15:12 UTC
  reason:
promote-to-proposed: Holding -- builds not complete

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

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

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

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

Title:
  linux-aws: 4.4.0-1041.44 -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-signing-to-proposed series:
  Invalid
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: Wednesday, 10. April 2019 09:39 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/1822832/+subscriptions

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

[Kernel-packages] [Bug 1824175] [NEW] iGVT-g guest does not load graphics: kernel WARNING and wedged GPU

2019-04-10 Thread Leonardo Müller

Public bug reported:

On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel
GVT-g guest, it was noticed that the graphical interface does not load.
The following message appears:

[   19.844904] i915 :00:03.0: Failed to initialize GPU, declaring it
wedged!

And there are two kernel WARNING that appear. The first WARNING seems
harmless and it was already reported:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is
related to the host kernel, on this case 4.18.0-17 from HWE.

The second WARNING is new and probably is related to the failure to load
the graphics.

It is possible to access the guest using the serial console. While the
system claims GDM is working, there is no graphical interface visible.

I have tested with Xubuntu 19.04 Disco Dingo Beta too and the same
problem was noticed: two kernel WARNING, a wedged GPU and failure to
load the graphics, even if the LightDM services was shown as running by
systemctl status.

Ubuntu 18.04 guests with kernel 4.15 and 4.18 are working. Mageia 7
guests with kernel 5.0.7 are working too, this seems related to the
5.0.0 kernel from Disco. Tested with both 5.0.0-7 and 5.0.0-8.

Example of QEMU command line used:

qemu-system-x86_64 -global PIIX4_PM.disable_s4=1 -M pc,usb=false
-machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -name "Ubuntu
Disco" -k pt-br -nodefaults -accel kvm -m 2G -cpu host -smp
cores=2,threads=1 -netdev user,id=net0 -device e1000,netdev=net0,addr=8
-device vfio-
pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/84de120a-c340-48fc-
ba40-62f54c76f3ad,rombar=0,display=on,addr=0x3,id=iHD520 -device nec-
usb-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 -device
usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display gtk,gl=on
-hda /home/usuario/.local/share/libvirt/images/ubuntu_disco.qcow2
-monitor vc -serial vc

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-8-generic 5.0.0-8.9
ProcVersionSignature: User Name 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Apr 10 12:04:47 2019
InstallationDate: Installed on 2019-04-09 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
IwConfig:
 ens8  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 002: ID 46f4:0002  
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=deb9f102-2eaf-4c05-96da-8c541c55726b ro quiet splash console=ttyS0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-8-generic N/A
 linux-backports-modules-5.0.0-8-generic  N/A
 linux-firmware   1.178
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.1
dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.1
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug 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/1824175

Title:
  iGVT-g guest does not load graphics: kernel WARNING and wedged GPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel
  GVT-g guest, it was noticed that the graphical interface does not
  load. The following message appears:

  [   19.844904] i915 :00:03.0: Failed to initialize GPU, declaring
  it wedged!

  And there are two kernel WARNING that appear. The first WARNING seems
  harmless and it was already reported:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is
  related to the host kernel, on this case 4.18.0-17 from HWE.

  The second WARNING is new and probably is related to the failure to
  load the graphics.

  It is possible to access the guest using the serial console. While the
  system claims GDM is working, there is no graphical interface visible.

  I have tested with

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

All that seems to be missing is bpffilter. I've made a test build with
this moved to linux-modules. It appears to be working for check-
requirements. Can you test and make sure everything is working as
expected? Thanks!

http://people.canonical.com/~sforshee/lp1823862/

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Kernel-packages] [Bug 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

2019-04-10 Thread 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/1822788

Title:
  linux-aws: 4.18.0-1013.15 -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:
  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-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-aws package in Ubuntu:
  Invalid
Status in linux-aws 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 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 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/1822788/+subscriptions

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

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

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

** 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-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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: Ready for Promote to Proposed
  phase-changed: Friday, 05. April 2019 17:41 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 09:02 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

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

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

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

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 09:02 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

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

** This bug has been marked a duplicate of bug 1823862
   disco: unable to use iptables/enable ufw under -virtual kernel

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 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
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests

2019-04-10 Thread Sean Feole

affects 4.18.0-1013.15 linux-aws

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

Title:
  vmx tests fail in kvm_unit_tests

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

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=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N]

[Kernel-packages] [Bug 1811850] Re: linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

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

** This bug is no longer a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

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

** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1819716
  phase: Ready for Release
  phase-changed: Tuesday, 02. April 2019 09:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
promote-to-updates: Pending -- ready to copy

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

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

[Kernel-packages] [Bug 1815061] Re: linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

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

** This bug is no longer a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Testing
  phase-changed: Sunday, 03. March 2019 06:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

** 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 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822788

Title:
  linux-aws: 4.18.0-1013.15 -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:
  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-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-aws package in Ubuntu:
  Invalid
Status in linux-aws 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 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 03. April 2019 23:34 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/1822788/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  iGVT-g guest does not load graphics: kernel WARNING and wedged GPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel
  GVT-g guest, it was noticed that the graphical interface does not
  load. The following message appears:

  [   19.844904] i915 :00:03.0: Failed to initialize GPU, declaring
  it wedged!

  And there are two kernel WARNING that appear. The first WARNING seems
  harmless and it was already reported:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is
  related to the host kernel, on this case 4.18.0-17 from HWE.

  The second WARNING is new and probably is related to the failure to
  load the graphics.

  It is possible to access the guest using the serial console. While the
  system claims GDM is working, there is no graphical interface visible.

  I have tested with Xubuntu 19.04 Disco Dingo Beta too and the same
  problem was noticed: two kernel WARNING, a wedged GPU and failure to
  load the graphics, even if the LightDM services was shown as running
  by systemctl status.

  Ubuntu 18.04 guests with kernel 4.15 and 4.18 are working. Mageia 7
  guests with kernel 5.0.7 are working too, this seems related to the
  5.0.0 kernel from Disco. Tested with both 5.0.0-7 and 5.0.0-8.

  Example of QEMU command line used:

  qemu-system-x86_64 -global PIIX4_PM.disable_s4=1 -M pc,usb=false
  -machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -name "Ubuntu
  Disco" -k pt-br -nodefaults -accel kvm -m 2G -cpu host -smp
  cores=2,threads=1 -netdev user,id=net0 -device
  e1000,netdev=net0,addr=8 -device vfio-
  pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/84de120a-c340-48fc-
  ba40-62f54c76f3ad,rombar=0,display=on,addr=0x3,id=iHD520 -device nec-
  usb-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 -device
  usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display
  gtk,gl=on -hda
  /home/usuario/.local/share/libvirt/images/ubuntu_disco.qcow2 -monitor
  vc -serial vc

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: User Name 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Apr 10 12:04:47 2019
  InstallationDate: Installed on 2019-04-09 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  IwConfig:
   ens8  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 002: ID 46f4:0002  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=deb9f102-2eaf-4c05-96da-8c541c55726b ro quiet splash console=ttyS0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-3.1
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1264125] Re: kernel crash with "alx 0000:03:00.0 eth2: fatal interrupt 0x4019607, resetting"

2019-04-10 Thread Raushan Kumar Pandey

Facing this bug on ubuntu 19.04

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

Title:
  kernel crash with "alx :03:00.0 eth2: fatal interrupt 0x4019607,
  resetting"

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  Crash happened while playing video in browser.

  in syslog:
  Dec 25 15:17:01 peter-Lenovo-G510 CRON[17742]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
  Dec 25 15:17:33 peter-Lenovo-G510 kernel: [111598.474218] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  Dec 25 15:17:33 peter-Lenovo-G510 kernel: [111598.474324] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  Dec 25 15:17:33 peter-Lenovo-G510 kernel: [111598.474525] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  same message repeats until  reset 
  Dec 25 15:17:34 peter-Lenovo-G510 kernel: [111598.919434] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting
  Dec 25 15:17:34 peter-Lenovo-G510 kernel: [111598.919647] alx :03:00.0 
eth2: fatal interrupt 0x4019607, resetting

  peter@peter-Lenovo-G510:~$ uname -a
  Linux peter-Lenovo-G510 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:04:55 
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  peter@peter-Lenovo-G510:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #2 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  02:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
  03:00.0 Ethernet controller: Qualcomm Atheros QCA8172 Fast Ethernet (rev 10)

  peter@peter-Lenovo-G510:~$ dmesg | grep alx
  [4.478587] alx :03:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet 
[xx:xx:xx:xx:xx:xx]
  [   15.221697] alx :03:00.0: irq 46 for MSI/MSI-X
  [   15.223260] alx :03:00.0 eth2: NIC Up: 100 Mbps Full

  peter@peter-Lenovo-G510:/var/log$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  
  peter@peter-Lenovo-G510:/var/log$ grep alx pm-suspend.log
  alx32792  0 
  mdio   13807  1 alx
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend:
  Unloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend: success.
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend:
  Reloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend: success.
  alx32792  0 
  mdio   13807  1 alx
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend:
  Unloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend: success.
  Running hook /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend:
  Reloading alx kernel module ...
  /usr/lib/pm-utils/sleep.d/50unload_alx resume suspend: success.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1944 F pulseaudio
   /dev/snd/controlC1:  peter  1944 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=8de0eb76-c3d0-4219-b6a2-0837381be140
  InstallationDate: Installed on 2013-11-16 (39 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20238
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed 
root=UUID=

[Kernel-packages] [Bug 1822832] Re: linux-aws: 4.4.0-1041.44 -proposed tracker

** 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: Wednesday, 10. April 2019 09:39 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   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/1822832

Title:
  linux-aws: 4.4.0-1041.44 -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-signing-to-proposed series:
  Invalid
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: Wednesday, 10. April 2019 09:39 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/1822832/+subscriptions

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

** 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: Ready for Promote to Proposed
- phase-changed: Friday, 05. April 2019 17:41 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 10. April 2019 15:42 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

-- 
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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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: Promote to Proposed
  phase-changed: Wednesday, 10. April 2019 15:42 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

** 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 --
  kernel-stable-master-bug: 1822820
- phase: Ready for Packaging
- phase-changed: Wednesday, 03. April 2019 09:02 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 10. April 2019 15:36 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Packaging
  phase-changed: Wednesday, 10. April 2019 15:36 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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

Re: [Kernel-packages] [Bug 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

2019-04-10 Thread marvin

Hey. Cool.

Yea. I have a key board combination now which uses the xrander command, so
I have a work around. But the oled screen is not working on linux in
general because of the backlight issue. oled has no backlight.

What I find strange is that lenovo is not doing anything.

For example here. One of many posts.
https://forums.lenovo.com/t5/Other-Linux-Discussions/X-1-Yoga-OLED-brightness-control-under-linux/td-p/3948282


On Wed, Apr 10, 2019 at 5:21 PM Kai-Heng Feng 
wrote:

> Sorry for not following this - does this still happen?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768208
>
> Title:
>   [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The screen brightness cannot be changed.
>
>   In 16.04, I could change the brightness via:
>   xrandr --output eDP-1 --brightness 0.7
>
>   WORKAROUND: Execute at a terminal:
>   xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
>
>   WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/
>
>   ---
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  marvin 1768 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
>   MachineType: LENOVO 20FRS2M600
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-20-generic N/A
>linux-backports-modules-4.15.0-20-generic  N/A
>linux-firmware 1.173
>   Tags:  bionic
>   Uname: Linux 4.15.0-20-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 06/23/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1FET41W (1.15 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FRS2M600
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad X1 Yoga 1st
>   dmi.product.name: 20FRS2M600
>   dmi.product.version: ThinkPad X1 Yoga 1st
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+subscriptions
>

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

Title:
  [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The screen brightness cannot be changed.

  In 16.04, I could change the brightness via:
  xrandr --output eDP-1 --brightness 0.7

  WORKAROUND: Execute at a terminal:
  xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8

  WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/

  ---
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marvin 1768 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69
  MachineType: LENOVO 20FRS2M600
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2M600
  dmi.product.versio

[Kernel-packages] [Bug 1776563]

2019-04-10 Thread erikjohansson

As i wrote i still use parameters.
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
For me i couldn't boot with anything other then pci=noacpi before, but now ivrs 
parameters work and i got a working touchpad.
"Things seem to work" is because i have only used the laptop for a day and i 
haven't tested every single scenario, but as far as i can tell it works.
I wasn't able to boot with ivrs parameter before and i had no use of the laptop 
that was only useful as an paperweight, it couldn't suspend or hibernate. 
Now i have a working laptop that i can finally use and no fans going berserk.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1824177] [NEW] dmesg spammed with nvidia-nvlink messages during install

You have been subscribed to a public bug:

I'm doing an install of Ubuntu 19.04 on an nVidia equipped laptop. I've
selected the 3rd party driver option in ubiquity and now my dmesg is
spammed 10x per second with this chunk. This appears to be slowing down
the install.

[Wed Apr 10 16:30:12 2019] nvidia-nvlink: Unregistered the Nvlink Core, major 
device number 235
[Wed Apr 10 16:30:12 2019] nvidia-nvlink: Nvlink Core is being initialized, 
major device number 235
[Wed Apr 10 16:30:12 2019] NVRM: The NVIDIA probe routine was not called for 1 
device(s).
[Wed Apr 10 16:30:12 2019] NVRM: This can occur when a driver such as: 
   NVRM: nouveau, rivafb, nvidiafb or rivatv 
   NVRM: was loaded and obtained ownership of the 
NVIDIA device(s).
[Wed Apr 10 16:30:12 2019] NVRM: Try unloading the conflicting kernel module 
(and/or
   NVRM: reconfigure your kernel without the conflicting
   NVRM: driver(s)), then try loading the NVIDIA kernel 
module
   NVRM: again.
[Wed Apr 10 16:30:12 2019] NVRM: No NVIDIA graphics adapter probed!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
CasperVersion: 1.402
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 16:29:38 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-410 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug disco rls-dd-incoming ubiquity-19.04.9 ubuntu
-- 
dmesg spammed with nvidia-nvlink messages during install
https://bugs.launchpad.net/bugs/1824177
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-410 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 1824177] Re: dmesg spammed with nvidia-nvlink messages during install

2019-04-10 Thread Steve Langasek

This looks like a problem with the integration in the nvidia drivers
package, which should not be trying to load modules immediately after
installation and prior to a reboot.  Reassigning for investigation.

** Package changed: ubiquity (Ubuntu) => nvidia-graphics-drivers-410
(Ubuntu)

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

Title:
  dmesg spammed with nvidia-nvlink messages during install

Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  I'm doing an install of Ubuntu 19.04 on an nVidia equipped laptop.
  I've selected the 3rd party driver option in ubiquity and now my dmesg
  is spammed 10x per second with this chunk. This appears to be slowing
  down the install.

  [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Unregistered the Nvlink Core, major 
device number 235
  [Wed Apr 10 16:30:12 2019] nvidia-nvlink: Nvlink Core is being initialized, 
major device number 235
  [Wed Apr 10 16:30:12 2019] NVRM: The NVIDIA probe routine was not called for 
1 device(s).
  [Wed Apr 10 16:30:12 2019] NVRM: This can occur when a driver such as: 
 NVRM: nouveau, rivafb, nvidiafb or rivatv 
 NVRM: was loaded and obtained ownership of the 
NVIDIA device(s).
  [Wed Apr 10 16:30:12 2019] NVRM: Try unloading the conflicting kernel module 
(and/or
 NVRM: reconfigure your kernel without the 
conflicting
 NVRM: driver(s)), then try loading the NVIDIA 
kernel module
 NVRM: again.
  [Wed Apr 10 16:30:12 2019] NVRM: No NVIDIA graphics adapter probed!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 16:29:38 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190410)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

--- Comment From leona...@ibm.com 2019-04-10 12:08 EDT---
(In reply to comment #68)
> In comment #22 above, it states that "In a meeting with lagarcia, I was
> informed this patch is very important, and that it is already on kernel
> 4.18-15 onwards."
>
> So, I assume that the required patchset(s) are already applied to the 18.04
> HWE kernel, and this bug requests a backport to the bionic 4.15 kernel.
>
> Next step is for the Canonical kernel team to analyse this backport request,
> dropping the commit fb1522e099f0 ("KVM: update to new mmu_notifier semantic
> v2", 2017-08-31), to assess whether it can be SRU'ed into the bionic 4.15
> kernel.

I may be wrong, but the patch to be dropped is "KVM: PPC: Remove unused
kvm_unmap_hva callback" (7fe24f427a09).

On this commit, it says it's removing code that is dead since commit
fb1522e099f0.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker

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

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

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

Title:
  linux-aws: 4.4.0-1080.90 -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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
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: Ready for Promote to Proposed
  phase-changed: Friday, 05. April 2019 10:07 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

Tested with the kernel+modules linked in #22

I can confirm I was able to enable ufw and query the installed iptables
rules:

$ uname -a
Linux juju-0f0cbd-disco-testing-38 5.0.0-10-generic #11+lp1823862v201904100938 
SMP Wed Apr 10 14:40:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup

$ sudo iptables-save
# Generated by iptables-save v1.6.1 on Wed Apr 10 16:15:01 2019
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
:ufw-after-forward - [0:0]
:ufw-after-input - [0:0]
:ufw-after-logging-forward - [0:0]
:ufw-after-logging-input - [0:0]
:ufw-after-logging-output - [0:0]
:ufw-after-output - [0:0]
:ufw-before-forward - [0:0]
:ufw-before-input - [0:0]
:ufw-before-logging-forward - [0:0]
:ufw-before-logging-input - [0:0]
:ufw-before-logging-output - [0:0]
:ufw-before-output - [0:0]
:ufw-logging-allow - [0:0]
:ufw-logging-deny - [0:0]
:ufw-not-local - [0:0]
:ufw-reject-forward - [0:0]
:ufw-reject-input - [0:0]
:ufw-reject-output - [0:0]
:ufw-skip-to-policy-forward - [0:0]
:ufw-skip-to-policy-input - [0:0]
:ufw-skip-to-policy-output - [0:0]
:ufw-track-forward - [0:0]
:ufw-track-input - [0:0]
:ufw-track-output - [0:0]
:ufw-user-forward - [0:0]
:ufw-user-input - [0:0]
:ufw-user-limit - [0:0]
:ufw-user-limit-accept - [0:0]
:ufw-user-logging-forward - [0:0]
:ufw-user-logging-input - [0:0]
:ufw-user-logging-output - [0:0]
:ufw-user-output - [0:0]
-A INPUT -j ufw-before-logging-input
-A INPUT -j ufw-before-input
-A INPUT -j ufw-after-input
-A INPUT -j ufw-after-logging-input
-A INPUT -j ufw-reject-input
-A INPUT -j ufw-track-input
-A FORWARD -j ufw-before-logging-forward
-A FORWARD -j ufw-before-forward
-A FORWARD -j ufw-after-forward
-A FORWARD -j ufw-after-logging-forward
-A FORWARD -j ufw-reject-forward
-A FORWARD -j ufw-track-forward
-A OUTPUT -j ufw-before-logging-output
-A OUTPUT -j ufw-before-output
-A OUTPUT -j ufw-after-output
-A OUTPUT -j ufw-after-logging-output
-A OUTPUT -j ufw-reject-output
-A OUTPUT -j ufw-track-output
-A ufw-after-input -p udp -m udp --dport 137 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 138 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 139 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 445 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 67 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 68 -j ufw-skip-to-policy-input
-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input
-A ufw-after-logging-forward -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW BLOCK] "
-A ufw-after-logging-input -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW BLOCK] "
-A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-forward -j ufw-user-forward
-A ufw-before-input -i lo -j ACCEPT
-A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny
-A ufw-before-input -m conntrack --ctstate INVALID -j DROP
-A ufw-before-input -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-input -p udp -m udp --sport 67 --dport 68 -j ACCEPT
-A ufw-before-input -j ufw-not-local
-A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
-A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT
-A ufw-before-input -j ufw-user-input
-A ufw-before-output -o lo -j ACCEPT
-A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-output -j ufw-user-output
-A ufw-logging-allow -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW ALLOW] "
-A ufw-logging-deny -m conntrack --ctstate INVALID -m limit --limit 3/min 
--limit-burst 10 -j RETURN
-A ufw-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix 
"[UFW BLOCK] "
-A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN
-A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN
-A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN
-A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny
-A ufw-not-local -j DROP
-A ufw-skip-to-policy-forward -j DROP
-A ufw-skip-to-policy-input -j DROP
-A ufw-skip-to-policy-output -j ACCEPT
-A ufw-track-output -p tcp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-track-output -p udp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-user-limit -m limit --limit 3/min -j LOG --log-p

[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker