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

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

apport-collect 1825229

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

Title:
  request to supercede the interim changes for 1815268  with upstream
  commit 8065a779

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The interm patch in LP# 1815268 was positioned as a way of mitigation
  to the rename race condition as described in that bug. Now, the
  upstream patch has been accepted and it eliminates the need of the
  delay. The patch is now in staging tree and should be pulled into
  mainline soon:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97

  Hence we request to back out the delay patch for 1815268 and instead
  apply the upstream patch above.

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

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


[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot

2019-04-17 Thread dann frazier
Upstream thread:
  http://lists.infradead.org/pipermail/linux-arm-kernel/2019-April/647345.html

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

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

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


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

2019-04-17 Thread Simone Pernice
I have the same bug on my new laptop, a Teclast F6:

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
Bus 001 Device 006: ID 27c6:5740  
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 058f:3841 Alcor Micro Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  kernel/system

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

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

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

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

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

  Thanks in advance,
  Haz

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

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

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


[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 535 after opening lid black screen and freeze occurs

2019-04-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  Acer Aspire Travelmate 535 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04
  i386 32 bit processor

  On settings "do anything when closing lid" is aplied.
  Hard reset needs .

  Tried all other ways.

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

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


[Kernel-packages] [Bug 1825229] [NEW] request to supercede the interim changes for 1815268 with upstream commit 8065a779

2019-04-17 Thread Si-Wei Liu
Public bug reported:

The interm patch in LP# 1815268 was positioned as a way of mitigation to
the rename race condition as described in that bug. Now, the upstream
patch has been accepted and it eliminates the need of the delay. The
patch is now in staging tree and should be pulled into mainline soon:

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97

Hence we request to back out the delay patch for 1815268 and instead
apply the upstream patch above.

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

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

Title:
  request to supercede the interim changes for 1815268  with upstream
  commit 8065a779

Status in linux package in Ubuntu:
  New

Bug description:
  The interm patch in LP# 1815268 was positioned as a way of mitigation
  to the rename race condition as described in that bug. Now, the
  upstream patch has been accepted and it eliminates the need of the
  delay. The patch is now in staging tree and should be pulled into
  mainline soon:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97

  Hence we request to back out the delay patch for 1815268 and instead
  apply the upstream patch above.

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

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


[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi

2019-04-17 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1825235

** Tags added: iso-testing

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

Title:
  Load average inexplicably high with 5.0 kernel on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
  2019 aarch64 aarch64 aarch64 GNU/Linux

  I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
  After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
  ubuntu@ubuntu:~$ w
   19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

  /proc/loadavg is consistent with these numbers. But when I check top,
  there are no obvious culprits hogging the cpu or anything. Typically
  everything looks to be <1% cpu usage, with top being the biggest cpu
  hog at about 2%. The system doesn't seem too slow (for a pi), but it's
  unusual to see such high numbers.

  Nothing seems to be swapping:

  ubuntu@ubuntu:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:908 173 422   6 312 
707
  Swap: 0   0   0

  
  ubuntu@ubuntu:~$ iostat
  Linux 5.0.0-1006-raspi2 (ubuntu)  04/17/19_aarch64_   (4 CPU)

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 1.640.151.572.060.00   94.57

  Device tpskB_read/skB_wrtn/skB_readkB_wrtn
  loop0 0.08 0.50 0.00354  0
  loop1 2.56 3.98 0.00   2805  0
  loop2 0.01 0.01 0.00  4  0
  mmcblk0  12.70   367.40   705.16 258830 496785

  ubuntu@ubuntu:~$ vmstat 1
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0  0  0 514540  18004 2240720097   182 2564   76  2  2 94  2 
 0
   0  0  0 514512  18004 22413600 0  2012 10136  142  0  0 94  
5  0
   0  0  0 514512  18004 22413600 0 0 10117  106  0  0 100  
0  0
   0  0  0 514512  18004 22413600 0 0 10121   98  0  0 100  
0  0
   0  0  0 514512  18012 22412800 0  2028 10129  141  0  0 93  
7  0
   0  0  0 514512  18012 22413600 0 0 10149  135  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0 0 10108   97  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0  2012 10125  126  0  0 95  
5  0
   0  0  0 514512  18012 22413600 0 0 10117  101  0  0 100  
0  0
   0  1  0 514512  18012 22413600 0  2012 10109  104  0  0 98  
2  0
   0  0  0 514512  18020 22412800 012 10139  150  0  0 96  
4  0
   0  0  0 514512  18020 22412800 0 0 10108   90  0  0 100  
0  0

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

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


[Kernel-packages] [Bug 982299] Re: [Dell Inspiron 1520] Screen stays black after laptop lid is opened

2019-04-17 Thread Emrah ÖZCAN
*** This bug is a duplicate of bug 1825219 ***
https://bugs.launchpad.net/bugs/1825219

** This bug has been marked a duplicate of bug 1825219
   Acer Aspire Travelmate 535 after opening lid black screen and freeze occurs

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

Title:
  [Dell Inspiron 1520] Screen stays black after laptop lid is opened

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

Bug description:
  Every time I close my laptop's lid and wait for few minutes -- screen stays 
black.
  I can switch to text console (Alt-Ctrl-F1) and back to black X screen 
(Alt-Ctrl-F7). I can login in console.
  I don't see mouse cursor on X screen.
  I'm using free nouveau drivers.

  This issue appeared just after I've upgraded to 12.04 beta2.

  I'm running 'sudo restart lightdm' from console to bring X to life.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sun Apr 15 16:35:07 2012
  DistUpgraded: 2012-03-30 06:52:10,270 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/gnome/defaults.list'
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Dell Inc. Inspiron 1520
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to precise on 2012-03-30 (16 days ago)
  dmi.bios.date: 07/11/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0UW306
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0UW306:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu35
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Kernel-packages] [Bug 1825219] [NEW] Acer Aspire Travelmate 535 after opening lid black screen and freeze occurs

2019-04-17 Thread Emrah ÖZCAN
Public bug reported:

ubuntu 16.04
i386 32 bit processor

On settings "do anything when closing lid" is aplied.
Hard reset needs .

Tried all other ways.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1825219

Title:
  Acer Aspire Travelmate 535 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04
  i386 32 bit processor

  On settings "do anything when closing lid" is aplied.
  Hard reset needs .

  Tried all other ways.

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

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


[Kernel-packages] [Bug 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 08:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-signing-to-proposed: Holding -- builds not complete
+   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 in Ubuntu.
https://bugs.launchpad.net/bugs/1822830

Title:
  linux-fips: 4.4.0-1008.10 -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:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 08:31 UTC
  reason:
promote-signing-to-proposed: Holding -- builds not complete
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/1822830/+subscriptions

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


[Kernel-packages] [Bug 1825235] [NEW] Load average inexplicably high with 5.0 kernel on rpi

2019-04-17 Thread Paul Larson
Public bug reported:

Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
2019 aarch64 aarch64 aarch64 GNU/Linux

I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
ubuntu@ubuntu:~$ w
 19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

/proc/loadavg is consistent with these numbers. But when I check top,
there are no obvious culprits hogging the cpu or anything. Typically
everything looks to be <1% cpu usage, with top being the biggest cpu hog
at about 2%. The system doesn't seem too slow (for a pi), but it's
unusual to see such high numbers.

Nothing seems to be swapping:

ubuntu@ubuntu:~$ free -m
  totalusedfree  shared  buff/cache   available
Mem:908 173 422   6 312 707
Swap: 0   0   0


ubuntu@ubuntu:~$ iostat
Linux 5.0.0-1006-raspi2 (ubuntu)04/17/19_aarch64_   (4 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
   1.640.151.572.060.00   94.57

Device tpskB_read/skB_wrtn/skB_readkB_wrtn
loop0 0.08 0.50 0.00354  0
loop1 2.56 3.98 0.00   2805  0
loop2 0.01 0.01 0.00  4  0
mmcblk0  12.70   367.40   705.16 258830 496785

ubuntu@ubuntu:~$ vmstat 1
procs ---memory-- ---swap-- -io -system-- --cpu-
 r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa st
 0  0  0 514540  18004 2240720097   182 2564   76  2  2 94  2  0
 0  0  0 514512  18004 22413600 0  2012 10136  142  0  0 94  5  0
 0  0  0 514512  18004 22413600 0 0 10117  106  0  0 100  0 
 0
 0  0  0 514512  18004 22413600 0 0 10121   98  0  0 100  0 
 0
 0  0  0 514512  18012 22412800 0  2028 10129  141  0  0 93  7  0
 0  0  0 514512  18012 22413600 0 0 10149  135  0  0 100  0 
 0
 0  0  0 514512  18012 22413600 0 0 10108   97  0  0 100  0 
 0
 0  0  0 514512  18012 22413600 0  2012 10125  126  0  0 95  5  0
 0  0  0 514512  18012 22413600 0 0 10117  101  0  0 100  0 
 0
 0  1  0 514512  18012 22413600 0  2012 10109  104  0  0 98  2  0
 0  0  0 514512  18020 22412800 012 10139  150  0  0 96  4  0
 0  0  0 514512  18020 22412800 0 0 10108   90  0  0 100  0 
 0

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

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

Title:
  Load average inexplicably high with 5.0 kernel on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
  2019 aarch64 aarch64 aarch64 GNU/Linux

  I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
  After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
  ubuntu@ubuntu:~$ w
   19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

  /proc/loadavg is consistent with these numbers. But when I check top,
  there are no obvious culprits hogging the cpu or anything. Typically
  everything looks to be <1% cpu usage, with top being the biggest cpu
  hog at about 2%. The system doesn't seem too slow (for a pi), but it's
  unusual to see such high numbers.

  Nothing seems to be swapping:

  ubuntu@ubuntu:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:908 173 422   6 312 
707
  Swap: 0   0   0

  
  ubuntu@ubuntu:~$ iostat
  Linux 5.0.0-1006-raspi2 (ubuntu)  04/17/19_aarch64_   (4 CPU)

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 1.640.151.572.060.00   94.57

  Device tpskB_read/skB_wrtn/skB_readkB_wrtn
  loop0 0.08 0.50 0.00354  0
  loop1 2.56 3.98 0.00   2805  0
  loop2 0.01 0.01 0.00  4  0
  mmcblk0  12.70   367.40   705.16 258830 496785

  ubuntu@ubuntu:~$ vmstat 1
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0  0  0 

[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

2019-04-17 Thread Joe Barnett
Either way, whatever fix is in the
https://people.canonical.com/~khfeng/lp1823029/ kernel is very effective
if not perfect -- can it be put into the main repo kernels or will I
need to keep kernel packages held for a while?

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

Title:
  [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when suspending, the suspend process fails, and the machine
  becomes unresponsive to any input, has nothing but a black/off
  display, and fans kick in and run high (which is actually 'good' for
  detecting the issue has happened).

  journalctl output from an unsuccessful suspend:

  Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending...
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5332] 
manager: sleep: sleep requested (sleeping: no  en
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5333] device 
(40:4E:36:47:ED:D1): state change: disconn
  Apr 02 13:39:54 taplop NetworkManager[4083]:   [1554237594.5358] 
manager: NetworkManager state is now ASLEEP
  Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline
  Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 
0x00F4).
  Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
  Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully.
  Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume...
  Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume.
  Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep.
  Apr 02 13:39:57 taplop systemd[1]: Starting Suspend...
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9078] caught 
SIGTERM, shutting down normally.
  Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager...
  Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was 
not added
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9485] dhcp4 
(wlp2s0): canceled DHCP transaction, DHCP c
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] dhcp4 
(wlp2s0): state changed bound -> done
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9486] device 
(wlp2s0): DHCPv4: 480 seconds grace period
  Apr 02 13:39:57 taplop NetworkManager[4083]:   [1554237597.9570] 
exiting (success)
  Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: 
[resource:///org/gnome/shell/ui/status/network.js 1187]: reference
  Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded.
  Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager.
  Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection 
(0x55d340e8f5a0), has been already deallocated — im
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for 
context 0x55d34160e1e0 ==
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0   55d345364700 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1   55d345364680 i   
resource:///org/gnome/shell/ui/status/networ
  Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2   7ffe97451d00 b   
self-hosted:979 (7fc3d4350a60 @ 440)
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from 
f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED 
bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge
  Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to 
flip inactive CRTC
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv6 with address fe80::1c45
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: 
https://daisy.ubuntu.com
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer 
relevant for mDNS.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on 
interface wlp2s0.IPv4 with address 10.30.2.26
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
fe80::1c45:b634:dc94:8f5f on wlp2s0.
  Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 
10.30.2.26 on wlp2s0.
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit 
ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
  Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface 
p2p-dev-wlp2s0 flags: No such device
  Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending 

[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-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/1824771

Title:
  linux-aws: 4.18.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


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

2019-04-17 Thread Jeremy
Wow.. just realized I forget to use -r... Sorry about that.

Attached is the output when I Select Mirror which "works"

** Attachment added: "journalctl-mirror.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+attachment/5256630/+files/journalctl-mirror.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/1825071

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


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

2019-04-17 Thread Jeremy
I just tested with Disco, the exact same thing on there too.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


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

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-aws: 4.4.0-1081.91 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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


[Kernel-packages] [Bug 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   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/1824773

Title:
  linux-aws: 4.15.0-1037.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
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/1824773/+subscriptions

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


[Kernel-packages] [Bug 1825222] [NEW] Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf and aarch64) kernel config?

2019-04-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

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

Related kernel config options:

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

Cheers,
Paweł Jarosz

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

-- 
Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf and 
aarch64) kernel config?
https://bugs.launchpad.net/bugs/1825222
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 1822937] Re: NVIDIA settings won't write to /etc/xorg

2019-04-17 Thread Doug McMahon
What one would see from terminal (pkexec ls works fine)

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in 
activate_name_owner
return self.get_name_owner(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
's', (bus_name,), **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could 
not get owner of name 'com.ubuntu.ScreenResolution.Mechanism': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/screen-resolution-extra/nvidia-polkit.py", line 75, in 

operation_status = main(options)
  File "/usr/share/screen-resolution-extra/nvidia-polkit.py", line 42, in main
conf = get_xkit_service()
  File "/usr/share/screen-resolution-extra/nvidia-polkit.py", line 33, in 
get_xkit_service
service_object = dbus.SystemBus().get_object(SERVICE_NAME, OBJECT_PATH)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: 
Cannot launch daemon, file not found or permissions invalid

ERROR: Unable to open X config file '/etc/X11/xorg.conf' for writing.

** Changed in: nvidia-settings (Ubuntu)
   Status: Incomplete => New

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

Title:
  NVIDIA settings won't write to /etc/xorg

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  I tried running it with root (`sudo nvidia-settings`) and without.

  I also generated an xorg file with `nvidia-xconfig`, and do the same
  thing, but it still won't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-settings 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr  3 00:33:48 2019
  InstallationDate: Installed on 2019-04-02 (0 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

2019-04-17 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/1824771

Title:
  linux-aws: 4.18.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 430809] Re: [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch

2019-04-17 Thread Malik
That's a trick question. Windows and Linux people are shouting on both
sides that their system is better than the other. In the end, both are
just tools. They're both a way to get a machine to do what you want it
to do. Each has it's own https://couponspirit.com/uber-coupon-
existing-user">selling points and ditching points. If you're cafeful
with your system, either one will suffice. That being said, I am an
Ubuntu user for the virus protection. However, the in-built spyware
makes me question sometimes whether or not it's worth it.

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

Title:
  [Dell Latitude D430, iwl3945] Wireless can't be activated after
  disabling kill switch

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

Bug description:
  It seems that this problem keeps reappearing. This is exactly the same
  as bug 193970, but opening a new bug since the first one is very big
  and noisy already.

  Summary: If I boot with the kill switch off (i. e. wifi enabled), the
  kill switch works just fine. But if I boot with kill switch on (i. e.
  wifi disabled), changing the kill switch doesn't do anything and
  network-manager keeps insisting that the network is disabled.

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2634 F pulseaudio
   /dev/snd/controlC0:  martin 2634 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,10280201,00102201'
 Controls  : 7
 Simple ctrls  : 5
  Card1.Amixer.info:
   Card hw:1 'Headset'/'Logitech Logitech USB Headset at 
usb-:00:1d.7-8.3.4, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0a01'
 Controls  : 6
 Simple ctrls  : 2
  CheckboxSubmission: 526c13623eeda7bcc3936c7be57b2d29
  CheckboxSystem: c8e8edcc4d15e0d55af04774be77e330
  Date: Wed Sep 16 17:49:06 2009
  DistroRelease: Ubuntu 9.10
  HibernationDevice: RESUME=UUID=5df2daed-eb83-4d60-a87c-9b71ff6b703f
  MachineType: Dell Inc. Latitude D430
  Package: linux-image-2.6.31-10-generic 2.6.31-10.32lp429241apw2
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic 
root=UUID=e43b0104-23d3-4bb8-9710-effa762ca2f6 ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.32lp429241apw2-generic
  RelatedPackageVersions:
   linux-backports-modules-2.6.31-10-generic N/A
   linux-firmware 1.18
  SourcePackage: linux
  Uname: Linux 2.6.31-10-generic i686
  dmi.bios.date: 05/21/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0HU754
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd05/21/2007:svnDellInc.:pnLatitudeD430:pvr:rvnDellInc.:rn0HU754:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D430
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1300218] Re: firmware for linux kernel drivers cannot install

2019-04-17 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  firmware for linux kernel drivers cannot install

Status in linux-firmware package in Ubuntu:
  Won't Fix

Bug description:
  Hello, 
  I bought dell inspiron 3537 with ubuntu pre-installed. Immediately after 
turning on, ubuntu updated. First, I lost my wireless connection but could 
connect by a cable. I managed to fix that, but now it says that it has 
downloaded firmware for Linux kernel drivers but cannot install them. In 
details the following message is shown:
  installArchives() failed: (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 214477 files and directories currently installed.)
  Preparing to replace linux-firmware 1.79.1 (using 
.../linux-firmware_1.79.10_all.deb) ...
  Unpacking replacement linux-firmware ...
  dpkg: error processing /var/cache/apt/archives/linux-firmware_1.79.10_all.deb 
(--unpack):
   trying to overwrite '/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is 
also in package bt-dw1705-firmware 0.1
  No apport report written because MaxReports is reached already
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-firmware_1.79.10_all.deb

  I am really new to ubuntu and this whole process is new to me, so I think I 
might have messed up somewhere. What should I do to fix this? 
  Everything else works fine. I mean, the whole system works fine apart for 
this installation process.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-47-generic 3.5.0-47.71~precise1
  ProcVersionSignature: Ubuntu 3.5.0-47.71~precise1-generic 3.5.7.30
  Uname: Linux 3.5.0-47-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC283 Analog [ALC283 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zlatko 2172 F pulseaudio
   /dev/snd/controlC0:  zlatko 2172 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xc081 irq 63'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xc0814000 irq 64'
 Mixer name : 'Realtek ALC283'
 Components : 'HDA:10ec0283,102805ea,0013'
 Controls  : 23
 Simple ctrls  : 12
  Date: Mon Mar 31 14:56:44 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  HibernationDevice: RESUME=UUID=ce2c08b7-3615-4cc3-af1d-d34ef0ccf332
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Inspiron 3537
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-47-generic 
root=UUID=870a5c69-c2cd-4574-aeaf-50c6670cdece ro radeon.modeset=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-47-generic N/A
   linux-backports-modules-3.5.0-47-generic 

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

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

apport-collect 1825280

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  with 5.0 kernel

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

Bug description:
  Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with
  deployment for ARM64 / AMD64).

  In disco, this option was enabled:
  $ grep RANDOM_TRUST_CPU 
~/ubuntu-disco/debian.master/config/config.common.ubuntu
  CONFIG_RANDOM_TRUST_CPU=y

  $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations 
  CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 
'y', 'ppc64el': 'y', 's390x': 'y'}>

  
  FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
  Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2835, in 
test_520_config_random_trust_cpu
  self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
    File "./test-kernel-security.py", line 208, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 195, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825280/+subscriptions

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

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822807 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Testing
- phase-changed: Friday, 12. April 2019 01:06 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 05:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
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-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:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 05:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
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/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 1822692] Re: Please ship the ib_uverbs driver module in the main modules package

2019-04-17 Thread Khaled El Mously
** Changed in: linux-aws (Ubuntu Trusty)
   Status: New => 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/1822692

Title:
  Please ship the ib_uverbs driver module in the main modules package

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Trusty:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Cosmic:
  Fix Committed
Status in linux-aws source package in Disco:
  Fix Released

Bug description:
  Please include the module drivers/infiniband/core/ib_uverbs.ko and its
  companion ib_umad.ko in the main linux-modules-*-aws package, in order
  to support upcoming Amazon features.

  +++ b/debian.aws/control.d/aws.inclusion-list

  +drivers/infiniband/core/ib_umad.ko
  +drivers/infiniband/core/ib_uverbs.ko

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

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


[Kernel-packages] [Bug 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1037.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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/1824773/+subscriptions

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


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

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-aws: 4.4.0-1081.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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


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

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

apport-collect 1825272

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

Title:
  headset-mic doesn't work on two Dell laptops.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  When we plugged a microphone or a headset into front audio slot.
  No audio input device is detected.
  Note from ODM: Rear audio port only support Lineout

  [Reproduce Steps]
  1. Plugged a microphone or a headset

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

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


[Kernel-packages] [Bug 1825280] [NEW] test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel

2019-04-17 Thread Po-Hsu Lin
Public bug reported:

Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with
deployment for ARM64 / AMD64).

In disco, this option was enabled:
$ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/config.common.ubuntu
CONFIG_RANDOM_TRUST_CPU=y

$ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations 
CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 
'y', 'ppc64el': 'y', 's390x': 'y'}>


FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2835, in 
test_520_config_random_trust_cpu
self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
  File "./test-kernel-security.py", line 208, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 195, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel 
config

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

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

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

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

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  with 5.0 kernel

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

Bug description:
  Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with
  deployment for ARM64 / AMD64).

  In disco, this option was enabled:
  $ grep RANDOM_TRUST_CPU 
~/ubuntu-disco/debian.master/config/config.common.ubuntu
  CONFIG_RANDOM_TRUST_CPU=y

  $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations 
  CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 
'y', 'ppc64el': 'y', 's390x': 'y'}>

  
  FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
  Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2835, in 
test_520_config_random_trust_cpu
  self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
    File "./test-kernel-security.py", line 208, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 195, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825280/+subscriptions

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


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

2019-04-17 Thread Jeremy
I will test with Disco but as this is a work environment for me I need
something a bit more stable than a Beta. I will test with a Live USB and
see if this behaves the same.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


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

2019-04-17 Thread Jeremy
Further tinkering, shows that External and Built-in do nothing but make
my monitors go blank (refresh).

If I select any of those while on Mirror, I remain on mirror. The same
goes for Join.

This is very strange behavior

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


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

2019-04-17 Thread Jeremy
So now that I have been playing a bit more, I found this out.

If I do not reconfigure my monitors after this resets it all. Built-in
and External do nothing at all. The screen does not go black or
anything. There is no output in journalctl.

If I do configure my system, then switch to built-in, it does nothing.
If I switch to External, then it clears out my settings and outputs:

-- Logs begin at Fri 2018-06-22 14:57:18 EDT, end at Thu 2019-04-18 00:00:47 
EDT. --
Apr 18 00:00:47 Zeus sudo[21299]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Apr 18 00:00:47 Zeus sudo[21299]: jpsimkins : TTY=pts/1 ; PWD=/home/jpsimkins ; 
USER=root ; COMMAND=/bin/journalctl -r
Apr 18 00:00:46 Zeus sudo[21182]: pam_unix(sudo:session): session closed for 
user root
Apr 18 00:00:40 Zeus rtkit-daemon[2437]: Supervising 5 threads of 1 processes 
of 1 users.
Apr 18 00:00:40 Zeus rtkit-daemon[2437]: Successfully made thread 21254 of 
process 3108 (n/a) owned by '1000' RT at priority 5.
Apr 18 00:00:40 Zeus rtkit-daemon[2437]: Supervising 4 threads of 1 processes 
of 1 users.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ffef19050), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff58ad310), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff49b2850), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff2c05090), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff5459040), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ffebbd220), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff815f030), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff62cf560), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff793dde0), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff9e48fb0), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff22e38e0), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff7d62290), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ff4abb450), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff4d368b0), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.BoxLayout (0x556ffeb90560), 
has been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #6 0x7c15e9b0 I   
self-hosted:916 (0x7fd0e03f12b8 @ 367)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #5 0x7c15e930 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd0e03b5de0 @ 71)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #4 0x556ff22c9620 i   
resource:///org/gnome/shell/ui/layout.js:531 (0x7fd0cbe042b8 @ 127)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #3 0x7c15dd50 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd0e03d2230 @ 386)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #2 0x7c15dcc0 I   
self-hosted:916 (0x7fd0e03f12b8 @ 367)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #1 0x7c15dc40 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd0e03b5de0 @ 71)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #0 0x7c15dbe0 b   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7fd0cbec7780 @ 273)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: == Stack trace for context 
0x556ff1e33320 ==
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #6 0x7c15e9b0 I   
self-hosted:916 (0x7fd0e03f12b8 @ 367)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #5 0x7c15e930 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd0e03b5de0 @ 71)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #4 0x556ff22c9620 i   
resource:///org/gnome/shell/ui/layout.js:531 (0x7fd0cbe042b8 @ 127)
Apr 18 00:00:36 Zeus org.gnome.Shell.desktop[3085]: #3 0x7c15dd50 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd0e03d2230 @ 386)
Apr 18 00:00:36 Zeus gnome-shell[3085]: Object St.Icon (0x556ff47a0ba0), has 
been already finalized. Impossible to set any property to it.
Apr 18 00:00:36 Zeus 

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

2019-04-17 Thread Jeremy
Not sure if this is anything but the monitors are numbered 1,2,3
respectively. On Disco, these are reverse of what I have now. Meaning, 3
is now 1 and 1 is now 3. I also noticed this is true for Windows 10
also. Just wanted to make note on this as I am unsure why. Windows 10
projector works but due to the monitor numbers being reverse, the
monitors are off too (but it does work on Win10)

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.18.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-04-17 Thread Jeff Walter
I have encountered this problem on Ubuntu Bionic (running in VMWare
Fusion) with Chrome latest open. Chrome will start drawing the page
randomly (I've seen that on really old versions of Chrome on Mac). When
it starts doing that I can lock-up my OS by doing a `killall chrome`
from terminal. When I do that, I can still move my mouse, but clicking
doesn't register. I end up having to reboot my VM.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

2019-04-17 Thread Hui Wang
** Description changed:

- I'm experiencing a repeating crackling noise after 19.04 upgrade that
- start just after the boot and before the login.
+ [Impact]
+ After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM 
is
+ enabled, on some codecs or for some hw design, there is noise with the codec
+ runtime PM enabled.
+ 
+ 
+ [Fix]
+ put the machine in the power_save_black_list, this will set the power_save=0
+ 
+ [Test Case]
+ just boot up and do some audio operations, there is no noise anymore
+ 
+ [Regression Risk]
+ Low. this patch ony applies to the specific machines.
+ 
+ 
+ 
+ I'm experiencing a repeating crackling noise after 19.04 upgrade that start 
just after the boot and before the login.
  
  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.
  
  The command "killall pulseaudio" usually stop the noise for 10 seconds,
  then the noise restart.
  
  The system was running smoothly on 18.10
  
  Alessandro-
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
  dmi.product.name: IMEDIA 5204
  dmi.product.version: PB34310106
  dmi.sys.vendor: Packard Bell NEC

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

Title:
  [regression][snd_hda_codec_realtek] repeating crackling noise after
  19.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM 
is
  enabled, on some codecs or for some hw design, there is noise with the codec
  runtime PM enabled.

  
  [Fix]
  put the machine in the power_save_black_list, this will set the power_save=0

  [Test Case]
  just boot up and do some audio operations, there is no noise anymore

  [Regression Risk]
  Low. this patch ony applies to the specific machines.


  
  I'm experiencing a repeating crackling noise after 19.04 upgrade that start 
just after the boot and before the login.

  I tried a bunch of fixes for pulseaudio I found googling, including this one 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling
   and this one 
https://askubuntu.com/questions/864608/audio-crackle-through-headphones. 
Neither of which helped.

  The command "killall pulseaudio" usually stop the noise for 10
  seconds, then the noise restart.

  The system was running smoothly on 18.10

  Alessandro-

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alessandro   3310 F pulseaudio
   /dev/snd/controlC0:  alessandro   3310 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 03:29:00 2019
  InstallationDate: Installed on 2016-07-09 (989 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago)
  dmi.bios.date: 02/14/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: GA-8TRC410M-NF
  dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
  dmi.chassis.type: 3
  dmi.chassis.vendor: NEC 

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

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822808
- phase: Testing
- phase-changed: Thursday, 11. April 2019 12:13 UTC
+ phase: Signoff
+ phase-changed: Thursday, 18. April 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
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-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:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822808
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
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/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 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

2019-04-17 Thread You-Sheng Yang
** Description changed:

+ [Impact]
+ Kernel NULL pointer dereference in mac80211_hwsim.
+ 
+ [Fix]
+ a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device 
registered
+ 
+ This fix has been included in 4.19.9 or above.
+ 
+ [Test Case]
+ $ git clone https://github.com/aircrack-ng/aircrack-ng
+ # Tested with 69a406c
+ $ cd aircrack-ng
+ $ grep 'sudo apt' README.md | bash
+ $ autoreconf -i
+ $ ./configure --with-experimental
+ $ make check
+ $ sudo bash scripts/airmon-ng.linux check kill
+ $ sudo make integration
+ 
+ # Run integration test again and check dmesg
+ $ sudo bash scripts/airmon-ng.linux check kill
+ $ sudo make integration
+ 
+ Verified with VMs setup locally.
+ 
+ [Regression Risk]
+ Low. Move forward data structure initialization only. This patch has
+ also been included in LTS stable kernel.
+ 
+  Original Bug Report 
+ 
  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.
  
  Output:
  
  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not 
supported by the AP
  [  434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not 
supported by the AP
  [  434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3)
  [  434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 
status=0 aid=1)
  [  434.761761] wlan1: associated
  [  434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
  [  437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  [  437.133996] mac80211_hwsim: initializing netlink
  [  437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht'
  [  437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
  [  437.140661] BUG: unable to handle kernel NULL pointer dereference at 

  [  437.140668] IP: 

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

2019-04-17 Thread Christoph Probst
** Summary changed:

- cifs related buffer overflow in strcat
+ cifs set_oplock overflow in strcat

** Summary changed:

- cifs set_oplock overflow in strcat
+ cifs set_oplock buffer overflow in strcat

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

Title:
  cifs set_oplock buffer overflow in strcat

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

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

  (Full dmesg output attached)

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

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

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

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

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


[Kernel-packages] [Bug 1825272] [NEW] headset-mic doesn't work on two Dell laptops.

2019-04-17 Thread Hui Wang
Public bug reported:

[Summary]
When we plugged a microphone or a headset into front audio slot.
No audio input device is detected.
Note from ODM: Rear audio port only support Lineout

[Reproduce Steps]
1. Plugged a microphone or a headset

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

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

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

Title:
  headset-mic doesn't work on two Dell laptops.

Status in linux package in Ubuntu:
  New

Bug description:
  [Summary]
  When we plugged a microphone or a headset into front audio slot.
  No audio input device is detected.
  Note from ODM: Rear audio port only support Lineout

  [Reproduce Steps]
  1. Plugged a microphone or a headset

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

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


[Kernel-packages] [Bug 1825222] Re: Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf and aarch64) kernel config?

2019-04-17 Thread Po-Hsu Lin
** Package changed: linux-hwe (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/1825222

Title:
  Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf
  and aarch64) kernel config?

Status in linux package in Ubuntu:
  New

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

  Related kernel config options:

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

  Cheers,
  Paweł Jarosz

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

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


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

2019-04-17 Thread Jeremy
It seems that the only option that works as expected is the Mirror
option. If I use Join as I am already on Join, then I lose my settings.

I have to use gnome-control-center to reconfigure my settings. So this
system works but this does not allow me to alter projector mode (super +
p), I just have to disable a monitor (this is what I am currently
doing).

If I disable a monitor then re-enable it later, I also have to redo my
settings (this one may be expected though).

My journalctl when using Mirror (which "works"):

-- Logs begin at Fri 2018-06-22 14:57:18 EDT, end at Wed 2019-04-17 23:34:23 
EDT. --
Jun 22 14:57:18 Zeus kernel: microcode: microcode updated early to revision 
0x24, date = 2018-01-21
Jun 22 14:57:18 Zeus kernel: Linux version 4.15.0-23-generic 
(buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) 
#25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 
4.15.18)
Jun 22 14:57:18 Zeus kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1
Jun 22 14:57:18 Zeus kernel: KERNEL supported cpus:
Jun 22 14:57:18 Zeus kernel:   Intel GenuineIntel
Jun 22 14:57:18 Zeus kernel:   AMD AuthenticAMD
Jun 22 14:57:18 Zeus kernel:   Centaur CentaurHauls
Jun 22 14:57:18 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 
floating point registers'
Jun 22 14:57:18 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE 
registers'
Jun 22 14:57:18 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX 
registers'
Jun 22 14:57:18 Zeus kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  
256
Jun 22 14:57:18 Zeus kernel: x86/fpu: Enabled xstate features 0x7, context size 
is 832 bytes, using 'standard' format.
Jun 22 14:57:18 Zeus kernel: e820: BIOS-provided physical RAM map:
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0x-0x00057fff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0x00058000-0x00058fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0x00059000-0x0009efff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0x0009f000-0x0009] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0x0010-0xb172dfff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xb172e000-0xb1734fff] ACPI NVS
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xb1735000-0xb2664fff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xb2665000-0xb2f1afff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xb2f1b000-0xda094fff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xda095000-0xda126fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xda127000-0xda18cfff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xda18d000-0xda2d1fff] ACPI NVS
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xda2d2000-0xdef39fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xdef3a000-0xdeffefff] type 20
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xdefff000-0xdeff] usable
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xfed1c000-0xfed1] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0xff00-0x] reserved
Jun 22 14:57:18 Zeus kernel: BIOS-e820: [mem 
0x0001-0x00081eff] usable
Jun 22 14:57:18 Zeus kernel: NX (Execute Disable) protection: active
Jun 22 14:57:18 Zeus kernel: efi: EFI v2.31 by American Megatrends
Jun 22 14:57:18 Zeus kernel: efi:  ACPI 2.0=0xda295000  ACPI=0xda295000  
SMBIOS=0xf04c0  MPS=0xfd480 
Jun 22 14:57:18 Zeus kernel: secureboot: Secure boot could not be determined 
(mode 0)
Jun 22 14:57:18 Zeus kernel: random: fast init done
Jun 22 14:57:18 Zeus kernel: SMBIOS 2.7 present.
Jun 22 14:57:18 Zeus kernel: DMI: Gigabyte Technology Co., Ltd. 
Z97X-UD5H/Z97X-UD5H, BIOS F10 08/03/2015
Jun 22 14:57:18 Zeus kernel: e820: update [mem 0x-0x0fff] usable 
==> reserved
Jun 22 14:57:18 Zeus kernel: e820: remove [mem 0x000a-0x000f] usable
Jun 22 14:57:18 Zeus kernel: e820: last_pfn = 0x81f000 max_arch_pfn = 
0x4
Jun 22 14:57:18 Zeus kernel: MTRR default type: uncachable
Jun 22 14:57:18 Zeus kernel: MTRR fixed ranges enabled:
Jun 22 14:57:18 Zeus kernel:   0-9 write-back
Jun 22 14:57:18 Zeus kernel:   A-B uncachable
Jun 22 14:57:18 Zeus kernel:   C-C write-protect
Jun 22 14:57:18 Zeus kernel:   

[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.18.0-1014.16 -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-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, 17. April 2019 08:26 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/1824771/+subscriptions

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


[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY

2019-04-17 Thread Daniel van Vugt
Also assigned to xorg-server, because Xorg should be intercepting
Alt+KEY. If Xorg fails to do so and somehow the key events get sent to
the VT then we get the unwanted VT's interpretation of Alt+KEY.

** Description changed:

+ WORKAROUND:
+ 
+ sudo kbd_mode -s
+ 
+ ORIGINAL DESCRIPTION:
+ 
  I'm running Ubuntu Lucid development branch.
  
  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.
  
  I'm pretty sure that my keyboard is not malfunctioning as I can use all
  my applications normally. (Pressing O and Ctrl-O do not have the same
  effect.)
  
  I'm not sure which package I should file this bug against. I'll happily
  do an apport-collect once I know.

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

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

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

** Summary changed:

- Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
+ Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from 
Alt+Left/Right

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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


[Kernel-packages] [Bug 1825272] Re: headset-mic doesn't work on two Dell laptops.

2019-04-17 Thread Hui Wang
** Description changed:

- [Summary]
- When we plugged a microphone or a headset into front audio slot.
- No audio input device is detected.
- Note from ODM: Rear audio port only support Lineout
+ [Impact]
+ the headset-mic can't be detected after we plug the headset into the audio 
jack
  
- [Reproduce Steps]
- 1. Plugged a microphone or a headset
+ [Fix]
+ Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE.
+ 
+ [Test Case]
+ Boot up the system
+ plug the headset into the audio jack
+ The audio device selecting dialogue will show up
+ selecting headset-mic icon, then rerord sound from headset-mic, it works well.
+ 
+ [Regression Risk]
+ Low. this patch only applies to specific dell machines which have the same 
pin config
+ as defined in the 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/1825272

Title:
  headset-mic doesn't work on two Dell laptops.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  the headset-mic can't be detected after we plug the headset into the audio 
jack

  [Fix]
  Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE.

  [Test Case]
  Boot up the system
  plug the headset into the audio jack
  The audio device selecting dialogue will show up
  selecting headset-mic icon, then rerord sound from headset-mic, it works well.

  [Regression Risk]
  Low. this patch only applies to specific dell machines which have the same 
pin config
  as defined in the patch.

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

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


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

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

apport-collect 1825222

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

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

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

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

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

Title:
  Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf
  and aarch64) kernel config?

Status in linux package in Ubuntu:
  Incomplete

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

  Related kernel config options:

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

  Cheers,
  Paweł Jarosz

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

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


[Kernel-packages] [Bug 1825280] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel

2019-04-17 Thread Po-Hsu Lin
** Description changed:

- With patch:
-   [PATCH][Disco] Trust CPU RNG to initialize kernel CRNG
+ Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with
+ deployment for ARM64 / AMD64).
  
- Landed in Disco kernel, it looks like we will need this config in the
- kernel
+ In disco, this option was enabled:
+ $ grep RANDOM_TRUST_CPU 
~/ubuntu-disco/debian.master/config/config.common.ubuntu
+ CONFIG_RANDOM_TRUST_CPU=y
+ 
+ $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations 
+ CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 
'y', 'ppc64el': 'y', 's390x': 'y'}>
+ 
  
  FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
  Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
  --
  Traceback (most recent call last):
-   File "./test-kernel-security.py", line 2835, in 
test_520_config_random_trust_cpu
- self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
-   File "./test-kernel-security.py", line 208, in assertKernelConfig
- self.assertKernelConfigSet(name)
-   File "./test-kernel-security.py", line 195, in assertKernelConfigSet
- '%s option was expected to be set in the kernel config' % name)
+   File "./test-kernel-security.py", line 2835, in 
test_520_config_random_trust_cpu
+ self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
+   File "./test-kernel-security.py", line 208, in assertKernelConfig
+ self.assertKernelConfigSet(name)
+   File "./test-kernel-security.py", line 195, in assertKernelConfigSet
+ '%s option was expected to be set in the kernel config' % name)
  AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel 
config

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  with 5.0 kernel

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

Bug description:
  Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with
  deployment for ARM64 / AMD64).

  In disco, this option was enabled:
  $ grep RANDOM_TRUST_CPU 
~/ubuntu-disco/debian.master/config/config.common.ubuntu
  CONFIG_RANDOM_TRUST_CPU=y

  $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations 
  CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 
'y', 'ppc64el': 'y', 's390x': 'y'}>

  
  FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
  Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2835, in 
test_520_config_random_trust_cpu
  self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
    File "./test-kernel-security.py", line 208, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 195, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel 
config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825280/+subscriptions

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


[Kernel-packages] [Bug 1825145] Re: test_072_strict_devmem in ubuntu_qrt_kernel_security failed to build with 5.0 hwe-edge kernel on BIonic

2019-04-17 Thread Po-Hsu Lin
** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  test_072_strict_devmem in ubuntu_qrt_kernel_security failed to build
  with 5.0 hwe-edge kernel on BIonic

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

Bug description:
  This might have something to do with bug 1823994
  Test failed to bulild with header not found issue

  ==
  FAIL: test_072_strict_devmem (__main__.KernelSecurityTest)
  /dev/mem unreadable for kernel memory
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 614, in test_072_strict_devmem
  self.assertShellExitEquals(0, ["make"])
File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
  self.assertEqual(expected, rc, msg + result + report)
  AssertionError: Got exit code 2, expected 0
  Command: 'make'
  Output:
  cc  -Wall -Werror -O2  readmem.c -o readmem -lcap
  make -C signpost
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
  make -C /usr/src/linux-headers-5.0.0-8-generic SUBDIRS=$PWD modules
  make[2]: Entering directory '/usr/src/linux-headers-5.0.0-8-generic'
  make[2]: Makefile: No such file or directory
  make[2]: *** No rule to make target 'Makefile'.  Stop.
  make[2]: Leaving directory '/usr/src/linux-headers-5.0.0-8-generic'
  Makefile:4: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
  Makefile:6: recipe for target 'all' failed
  make: *** [all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825145/+subscriptions

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


[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

2019-04-17 Thread You-Sheng Yang
** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1825058

Title:
  mac80211_hwsim unable to handle kernel NULL pointer dereference
  at

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

Bug description:
  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.

  Output:

  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not 
supported by the AP
  [  434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not 
supported by the AP
  [  434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3)
  [  434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 
status=0 aid=1)
  [  434.761761] wlan1: associated
  [  434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
  [  437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  [  437.133996] mac80211_hwsim: initializing netlink
  [  437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht'
  [  437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
  [  437.140661] BUG: unable to handle kernel NULL pointer dereference at 

  [  437.140668] IP: hrtimer_active+0xd/0x50
  [  437.140689] PGD 0 P4D 0 
  [  437.140692] Oops:  [#1] SMP PTI
  [  437.140693] Modules linked 

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

2019-04-17 Thread Kai-Heng Feng
I don't think it's a kernel issue, have you tried 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/1825071

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

2019-04-17 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  mac80211_hwsim unable to handle kernel NULL pointer dereference
  at

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

Bug description:
  The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well
  as linux-image-4.15.0-45-generic). It also happens with linux-
  image-4.15.0-47-generic on 18.04 as well as the HWE kernel
  (4.18.0-17-generic). All test were done on 64 bit in a virtual machine
  and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has
  other issues on this kernel that are solved in 19.04, most likely
  unrelated to this) or 19.04.

  Output:

  [  406.036796] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
  [  406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  [  406.110060] mac80211_hwsim: initializing netlink
  [  406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  [  406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
  [  406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  406.894434] device wlan1 entered promiscuous mode
  [  407.623768] mac80211_hwsim: initializing netlink
  [  407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
  [  407.761474] device wlan0 entered promiscuous mode
  [  412.293557] mac80211_hwsim: initializing netlink
  [  412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht'
  [  412.410453] device wlan0 entered promiscuous mode
  [  417.040581] mac80211_hwsim: initializing netlink
  [  417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
  [  417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
  [  417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  417.755334] device wlan1 entered promiscuous mode
  [  419.690453] mac80211_hwsim: initializing netlink
  [  419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
  [  419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht'
  [  419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  420.406242] device wlan1 entered promiscuous mode
  [  422.434785] mac80211_hwsim: initializing netlink
  [  422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht'
  [  422.579207] device wlan0 entered promiscuous mode
  [  427.126059] mac80211_hwsim: initializing netlink
  [  427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht'
  [  427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
  [  427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht'
  [  427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [  427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  427.932765] device wlan2 entered promiscuous mode
  [  430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
  [  434.757426] wlan1: authenticate with 02:00:00:00:00:00
  [  434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3)
  [  434.758851] wlan1: authenticated
  [  434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP 
use
  [  434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not 
supported by the AP
  [  434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not 
supported by the AP
  [  434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3)
  [  434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 
status=0 aid=1)
  [  434.761761] wlan1: associated
  [  434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
  [  437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  [  437.133996] mac80211_hwsim: initializing netlink
  [  437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht'
  [  437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht'
  [  437.140661] BUG: unable to handle kernel NULL pointer dereference at 

  [  437.140668] IP: hrtimer_active+0xd/0x50
  [  437.140689] PGD 0 P4D 0 
  [  437.140692] Oops:  [#1] SMP PTI
  [  437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 
coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 
snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 
crypto_simd glue_helper 

[Kernel-packages] [Bug 1814892] Re: [19.04 FEAT] qeth: Enhanced link speed - kernel part

2019-04-17 Thread Po-Hsu Lin
Mark this with verification done as per Frank's comment in #11

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

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

Title:
  [19.04 FEAT] qeth: Enhanced link speed - kernel part

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

Bug description:
  SRU Justification:
  --

  * This is more a request (rather than a bug) to add support for the newest 
OSA-Express7S (network-) card,
so that even cosmic and bionic users should be able to benefit from it.

  * The support became upstream accepted with 4.20, mainly with commit

  [Test Case]

  * Due to the absence of that particular card in our (Canonical)
  system, the testing is up to IBM.

  * The recognition of the card type itself can be done via 'lsqeth |
  grep card_type',

  * and the functionality can be tested by network test tools, like
  stress-ng.

  * A regression test can of course be done on our (Canonical) system.

  [Regression Potential]

  * The regression potential can be considered as low since it only
  affects the s390x platform

  * and there only the qeth driver/module.

  * The patch itself is less complex and adds mainly lines and fields
  for the recognition of the new card.

  * The entire code needed is already included in disco and a sniff test was 
done based on disco's kernel 5.0.
  __

  Function:
  Provide enhanced link speed for OSA networks
  Business Case:
  Improved performance with OSA networks

  Available with kernel 4.20
  Git-Commit: s390/qeth: report 25Gbit link speed [54e049c227]

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

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


[Kernel-packages] [Bug 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished

2019-04-17 Thread Po-Hsu Lin
** Description changed:

- On a s390x KVM, the enosys test is still running even the test has
- completed
+ On a s390x Bionic / Cosmic KVM, the enosys test is still running even
+ the test has completed
  
  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  root  2384  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep 
--color=auto stress
  root 19352  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19395  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19449  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19481  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  
- 
  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  
  04:03:13 WARNI| Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395
 for more info
  04:03:13 INFO |   GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   completed successfully
- 04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   
+ 04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
- 04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13   
+ 04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0
- 
  
  And the job on jenkins will eventually times out.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  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.9-0ubuntu7.6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
-  
+ 
  Date: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
-  
+ 
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
-  
+ 
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-48-generic N/A
-  linux-backports-modules-4.15.0-48-generic  N/A
-  linux-firmware 1.173.3
+  linux-restricted-modules-4.15.0-48-generic N/A
+  linux-backports-modules-4.15.0-48-generic  N/A
+  linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

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

Bug description:
  On a s390x Bionic / Cosmic KVM, the enosys test is still running even
  the test has completed

  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u 

[Kernel-packages] [Bug 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker

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

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 15. April 2019 06:39 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/1822830/+subscriptions

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


[Kernel-packages] [Bug 1752613] Re: Kernel 4.13.0-36-generic has memory issues on Hyper-V hosts.

2019-04-17 Thread Po-Hsu Lin
Hello,
do you still seeing this issue with the latest 4.15 HWE kernel?
Thanks

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

** Changed in: linux-signed-hwe (Ubuntu)
   Status: Confirmed => 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/1752613

Title:
  Kernel 4.13.0-36-generic has memory issues on Hyper-V hosts.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-hwe package in Ubuntu:
  Incomplete

Bug description:
  Following update from kernel 4.13.0-32-generic to 4.13.0-36-generic,
  my Hyper-V 2012 R2 hosted Ubunntu servers experienced problems with
  memory allocation--they reported total assigned memory less than the
  initial allocation of the dynamic memory configuration, corresponding
  with 98% memory utilization and over 35 load average.

  I was able to boot back to 4.13.0-32-generic, and the issue went away.
  I was also able to resolve the issue by changing the servers from
  dynamic memory allocations (512 initial 4096 max) to static memory
  allocations (4096 static).

  Sar memory snapshots as follows, only change was kernel booted:

  Linux 4.13.0-36-generic (servername)  03/01/2018  _x86_64_(4 CPU)
  09:14:34 AM kbmemfree kbmemused  %memused kbbuffers  kbcached  kbcommit   
%commit  kbactive   kbinact   kbdirty
  09:14:35 AM  6312409676 98.48  1528 28696   2416712
257.02 37948 4697628
  09:14:36 AM  7268408720 98.25  1368 27944   2418800
257.24 38360 45096   124
  Average: 6790409198 98.37  1448 28320   2417756
257.13 38154 4603676
  
__
  Linux 4.13.0-32-generic (servername)  03/01/2018  _x86_64_(4 CPU)

  09:31:02 AM kbmemfree kbmemused  %memused kbbuffers  kbcached  kbcommit   
%commit  kbactive   kbinact   kbdirty
  09:31:03 AM   1276908   1885452 59.62 32256735348   2728356 
74.01798260768032   260
  09:31:04 AM   1276908   1885452 59.62 32264735348   2728356 
74.01798304768036   280
  Average:  1276908   1885452 59.62 32260735348   2728356 
74.01798282768034   270

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar  1 10:17:06 2018
  InstallationDate: Installed on 2016-08-25 (552 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

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

apport-collect 1825089

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

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

Bug description:
  On a s390x KVM, the enosys test is still running even the test has
  completed

  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  root  2384  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep 
--color=auto stress
  root 19352  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19395  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19449  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19481  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable

  
  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  
  04:03:13 WARNI| Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395
 for more info
  04:03:13 INFO |   GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   completed successfully
  04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
  04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13   
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0

  
  And the job on jenkins will eventually times out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  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.9-0ubuntu7.6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)

2019-04-17 Thread Walter Lapchynski
What are you doing with pavucontrol that "fixes" it? With that last
comment, it's clear it's not the installation that solves the problem.
You're doing something with the program but I'm not sure what.

Also you said that you tried several things to fix it that didn't work.
What were they?

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

Title:
  Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed
  via add of pavucontrol)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-Test (LIVE x86_64)

  Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT)
  Two dell displays, left is landscape, right is portrait

  This live test had two packages added:  `vim` & `ubuntu-restricted-
  extras`

  Background:
  I added ubuntu-restricted-extras so I could run requested test on this system 
which had me streaming videos from utube - it was required to get around H264 
errors  (vim because I can't cope with other editors & added `multiverse` to my 
sources.

  Issue:
  With firefox streaming ABC News 24 (local AU news) I suspended machine.  
Waited
  Awoke machine - everything resumed as expected .. Some circling was apparent 
on firefox before picture resumed, however no sound.

  I was unable to fix it using any tools installed - to fix I `sudo apt
  install pavucontrol`, went to Configuration (or last tab) and
  Profile=Off on the drop-down menu, then returned to
  Profile=AnalogStereo Duplex.   This is something I do on occasion for
  this machine on installed system or other machines I use.

  This is really a minor issue, & may not be an issue on an installed
  system (though I come across it semi-regularly & just live with it).
  In regular use I pause/stop sound & know this makes this almost a non-
  issue (almost never happens when sound isn't playing).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 11:01:59 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished

2019-04-17 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

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

Bug description:
  On a s390x KVM, the enosys test is still running even the test has
  completed

  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  root  2384  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep 
--color=auto stress
  root 19352  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19395  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19449  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19481  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable

  
  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  
  04:03:13 WARNI| Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395
 for more info
  04:03:13 INFO |   GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   completed successfully
  04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
  04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13   
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0

  
  And the job on jenkins will eventually times out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  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.9-0ubuntu7.6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)

2019-04-17 Thread Chris Guiver
Yeah writing is not great... my mind wanders...

"went to Configuration (or last tab) and Profile=Off on the drop-down
menu, then returned to Profile=AnalogStereo Duplex."

is how I described it. The 'AnalogStereo Duplex' in that description
will be whatever it was before I switch it off, then return it...

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

Title:
  Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed
  via add of pavucontrol)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-Test (LIVE x86_64)

  Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT)
  Two dell displays, left is landscape, right is portrait

  This live test had two packages added:  `vim` & `ubuntu-restricted-
  extras`

  Background:
  I added ubuntu-restricted-extras so I could run requested test on this system 
which had me streaming videos from utube - it was required to get around H264 
errors  (vim because I can't cope with other editors & added `multiverse` to my 
sources.

  Issue:
  With firefox streaming ABC News 24 (local AU news) I suspended machine.  
Waited
  Awoke machine - everything resumed as expected .. Some circling was apparent 
on firefox before picture resumed, however no sound.

  I was unable to fix it using any tools installed - to fix I `sudo apt
  install pavucontrol`, went to Configuration (or last tab) and
  Profile=Off on the drop-down menu, then returned to
  Profile=AnalogStereo Duplex.   This is something I do on occasion for
  this machine on installed system or other machines I use.

  This is really a minor issue, & may not be an issue on an installed
  system (though I come across it semi-regularly & just live with it).
  In regular use I pause/stop sound & know this makes this almost a non-
  issue (almost never happens when sound isn't playing).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 11:01:59 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)

2019-04-17 Thread Walter Lapchynski
OH! Interesting. Three more questions:

 1. Before installing/trying pavucontrol what else did you try?
 2. When you resume with no audio and have pavucontrol installed already, if 
you go to the profile selection tab, is it in the "off" state?
 3. Am I correct that you tested this and had it occur in both Lubuntu and 
Ubuntu? Did you test with any other flavors?

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

Title:
  Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed
  via add of pavucontrol)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-Test (LIVE x86_64)

  Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT)
  Two dell displays, left is landscape, right is portrait

  This live test had two packages added:  `vim` & `ubuntu-restricted-
  extras`

  Background:
  I added ubuntu-restricted-extras so I could run requested test on this system 
which had me streaming videos from utube - it was required to get around H264 
errors  (vim because I can't cope with other editors & added `multiverse` to my 
sources.

  Issue:
  With firefox streaming ABC News 24 (local AU news) I suspended machine.  
Waited
  Awoke machine - everything resumed as expected .. Some circling was apparent 
on firefox before picture resumed, however no sound.

  I was unable to fix it using any tools installed - to fix I `sudo apt
  install pavucontrol`, went to Configuration (or last tab) and
  Profile=Off on the drop-down menu, then returned to
  Profile=AnalogStereo Duplex.   This is something I do on occasion for
  this machine on installed system or other machines I use.

  This is really a minor issue, & may not be an issue on an installed
  system (though I come across it semi-regularly & just live with it).
  In regular use I pause/stop sound & know this makes this almost a non-
  issue (almost never happens when sound isn't playing).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 11:01:59 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1821276] Re: Add support for MAC address pass through on RTL8153-BD

2019-04-17 Thread Jesse Sung
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

** Changed in: hwe-next
   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/1821276

Title:
  Add support for MAC address pass through on RTL8153-BD

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

Bug description:
  == SRU Justification ==

  * Impact:
  RTL8153-BD is used in Dell DA300 type-C dongle and should be added to the 
whitelist of devices to activate MAC address passthrough.

  * Fix:
  Two commits in upstream need to be applied in order to support this feature. 
Both of them are in 5.0.

  commit 8e29d23e28ee7fb995a00c1ca7e1a4caf5070b12
  Author: David Chen david.ch...@dell.com
  Date: Sat Feb 16 17:16:42 2019 +0800

  r8152: Add support for MAC address pass through on RTL8153-BD

  commit c286909fe5458f69e533c845b757fd2c35064d26
  Author: David Chen david.ch...@dell.com
  Date: Wed Feb 20 13:47:19 2019 +0800

  r8152: Fix an error on RTL8153-BD MAC Address Passthrough support

  * Testcase:
  BIOS settings must be properly set before verifying.
  1.[Settings][POST Behavior][MAC Address Pass-Through]: Passthrough MAC Address
  2. There should be two MAC addresses in BIOS settings, ex: 
[Settings][General][System Information]
  Attach the dongle and see if MAC passthrough works.

  * Risk of Regression:
  Clean cherry-pick from mainline, and only add specific hardware to the 
whitelist. Risk is low.

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

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


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

2019-04-17 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 16. April 2019 13:04 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/1824592/+subscriptions

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


[Kernel-packages] [Bug 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)

2019-04-17 Thread Naveen Kumar Goyal
Summing UP all Above comments:


Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic


this scenario is: i need to create 1000 of virtual interface , this is scale 
environment, where each new interface causing restart of networkd-dispatcher, 
losing out on older interface, if there creation is not completed successfully.
 

--
Operation:
create 2 virtual interface of mac vlan type, as 2icx0, 2icx1,
always the last created interface is availble, older one get deleted due to

Apr 16 10:56:28 u18_svr_madsz networkd-dispatcher[824]: 
WARNING:Unknown index 72 seen, reloading interface list
Apr 16 10:56:28 u18_svr_madsz systemd-networkd[22168]: 2icx0: Lost 
carrier

Same feature macvlan work in 16.04

---


problem occurs when both interface created using multiprocessing module of 
python

Process 1 execution ->
ip link add link ens34 2icx0 type macvlan
ifconfig 2icx0 up
ip addr add 192.168.49.230/16 dev 2icx0

Process 2 execution ->
ip link add link ens34 2icx1 type macvlan
ifconfig 2icx1 up
ip addr add 192.168.49.231/16 dev 2icx1



however this works when run in a order like:

ip link add link ens34 2icx0 type macvlan
ifconfig 2icx0 up
ip addr add 192.168.49.230/16 dev 2icx0
ip link add link ens34 2icx1 type macvlan
ifconfig 2icx1 up
ip addr add 192.168.49.231/16 dev 2icx1
 




Failed Logs:
--
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30948]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30948]: Could not 
generate persistent MAC address for 2icx0: No such file or directory
Apr 16 10:56:27 u18_svr_madsz systemd-networkd[22168]: 2icx0: Gained 
carrier
Apr 16 10:56:27 u18_svr_madsz networkd-dispatcher[824]: 
WARNING:Unknown index 71 seen, reloading interface list
Apr 16 10:56:27 u18_svr_madsz systemd-timesyncd[22214]: Network 
configuration changed, trying to establish connection.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30960]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30960]: Could not 
generate persistent MAC address for 2icx1: No such file or directory
Apr 16 10:56:28 u18_svr_madsz systemd-networkd[22168]: 2icx1: Gained 
carrier
Apr 16 10:56:28 u18_svr_madsz networkd-dispatcher[824]: 
WARNING:Unknown index 72 seen, reloading interface list
Apr 16 10:56:28 u18_svr_madsz systemd-networkd[22168]: 2icx0: Lost 
carrier
Apr 16 10:56:28 u18_svr_madsz systemd-timesyncd[22214]: Synchronized 
to time server 91.189.89.199:123 (ntp.ubuntu.com).
Apr 16 10:56:29 u18_svr_madsz systemd-networkd[22168]: 2icx1: Gained 
IPv6LL

Successful Logs:
--
Apr 16 12:10:38 u18_svr_madsz systemd-udevd[31348]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 12:10:38 u18_svr_madsz systemd-networkd[22168]: 2icx0: Gained 
carrier
Apr 16 12:10:38 u18_svr_madsz systemd-timesyncd[22214]: Network 
configuration changed, trying to establish connection.
Apr 16 12:10:38 u18_svr_madsz networkd-dispatcher[824]: 
WARNING:Unknown index 75 seen, reloading interface list
Apr 16 12:10:38 u18_svr_madsz systemd-udevd[31348]: Could not 
generate persistent MAC address for 2icx0: No such file or directory
Apr 16 12:10:38 u18_svr_madsz systemd-udevd[31358]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 12:10:38 u18_svr_madsz systemd-udevd[31358]: Could not 
generate persistent MAC address for 2icx1: No such file or directory
Apr 16 12:10:38 u18_svr_madsz systemd-networkd[22168]: 2icx1: Gained 
carrier
Apr 16 12:10:38 u18_svr_madsz networkd-dispatcher[824]: 
WARNING:Unknown index 76 seen, reloading interface list
Apr 16 12:10:38 u18_svr_madsz systemd-timesyncd[22214]: Synchronized 
to time server 91.189.91.157:123 (ntp.ubuntu.com).
Apr 16 12:10:39 u18_svr_madsz systemd-networkd[22168]: 2icx0: Gained 
IPv6LL
Apr 16 12:10:40 u18_svr_madsz systemd-networkd[22168]: 2icx1: Gained 
IPv6LL

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

Title:
  Ubuntu 18.04 networking issue (connection drops after approx. 15
  minutes)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently troubleshooting some network issues on Ubuntu 18.04 LTS Bionic. 
After checking a few logs I noticed that the networkd-dispatcher is generating 
errors. I'm unsure if this is a bug but I'd like to report it over here just to 
be sure:
   
  ```
  Jun 04 18:14:21 [servername] systemd-networkd-wait-online[2079]: managing: br2
  Jun 04 18:14:22 [servername] networkd-dispatcher[1890]: WARNING:Unknown 

[Kernel-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-17 Thread Po-Hsu Lin
Mark this as verification done for Cosmic as per Sami's comment in #48
Thanks

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   

[Kernel-packages] [Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

2019-04-17 Thread You-Sheng Yang
Set to INVALID per #10.

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

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

Title:
  Intel 8260 Bluetooth non-functioning, command timeouts

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When trying to use the Gigabyte Z170N-Gaming 5, with Intel 8260
  wifi+bluetooth, bluetooth does not function.

  Dmesg shows:
  [   13.051985] Bluetooth: Core ver 2.22
  [   13.051996] Bluetooth: HCI device and connection manager initialized
  [   13.051998] Bluetooth: HCI socket layer initialized
  [   13.051999] Bluetooth: L2CAP socket layer initialized
  [   13.052031] Bluetooth: SCO socket layer initialized
  [   15.100035] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   15.100036] Bluetooth: hci0: command 0xfc05 tx timeout
  [   15.100270] Bluetooth: hci0: Hardware error 0x08
  [   15.978374] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.978375] Bluetooth: BNEP filters: protocol multicast
  [   15.978377] Bluetooth: BNEP socket layer initialized
  [   17.116013] Bluetooth: hci0: command 0x0c03 tx timeout
  [   25.308049] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   27.324270] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   27.324275] Bluetooth: hci0: command 0xfc05 tx timeout
  [   27.324612] Bluetooth: hci0: Hardware error 0x08
  [   29.340020] Bluetooth: hci0: command 0x0c03 tx timeout
  [   37.340274] Bluetooth: hci0: Reset after hardware error failed (-110)
  [   39.356059] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [   39.356071] Bluetooth: hci0: command 0xfc05 tx timeout
  [   39.356499] Bluetooth: hci0: Hardware error 0x08

  
  I have tried the latest intel firmwares from mainline based on:
  https://bugzilla.kernel.org/show_bug.cgi?id=197147#c81
  and
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

  with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fmstrat2489 F pulseaudio
   /dev/snd/controlC0:  fmstrat2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 09:14:54 2019
  InstallationDate: Installed on 2019-01-20 (83 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Z170N-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=16462d84-0501-4b74-aeff-7765953b648f ro modprobe.blacklist=nouveau 
quiet splash intel_iommu=on hugepages=4096 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170N-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/25/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170N-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170N-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170N-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1769808] Re: System installed nvidia driver turned to black screen after upgrading

2019-04-17 Thread Marian Hello
I've same problem with nvidia 960 in combo with intel integrated card.
Even when I disable integrated card in BIOS, it doesn't help, but contrary 
making it default helps, but of course then system is using integrated card as 
main card.

I tried setting NOMODESET and WaylandEnable=false, but those didn't help.
Removing nvidia drivers and using noveau works.

Will also try replacing gdm with lightdm as suggested in
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-384/+bug/1705369

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

Title:
  System installed nvidia driver turned to black screen after upgrading

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

Bug description:
  My Ubuntu is the version of 18.04, after system upgrading (I remembered with 
Kernel being upgraded), the screen will turn black before login window shows up.
  PS: Currently I am only able to login to the system in the terminal instead 
of GUI. I don't know how to get related logs. If anyone needs logs for 
analysis, please tell me how I can collect the logs. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1769808/+subscriptions

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


[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot

2019-04-17 Thread You-Sheng Yang
** Description changed:

+ [Impact]
+ Systems with video cards using amdgpu driver may fail to resume due to 
resource leakage.
+ 
+ [Fix]
+ 73469585510d drm/amdgpu: fix for wb_clear
+ 
+ [Test Case]
+ Verified with fwts for a thounsand runs.
+ 
+ [Regression Risk]
+ Low. This patch has been included in stable kernel v4.16.y and on, and
+ it's mostly a trivial bug fix.
+ 
+  Original Bug Report 
  [Summary]
  When do the S3 stress test with AMD RX550 installed, the system hung after 
resume from S3 at 112nd S3.
  
  The kernel message:
  [ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
  [ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 11 (-22).
  [ 8120.979662] [drm] ib test on ring 12 succeeded
  [ 8120.981952] [drm] ib test on ring 13 succeeded
  [ 8120.984578] [drm] ib test on ring 14 succeeded
  [ 8120.984813] [drm] ib test on ring 15 succeeded
  [ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test 
failed (-22).
  [ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
  [ 8121.022465] [drm] 92GH: [Block 0]
  [ 8121.022465] [drm] 92GH: [Block 1]
  [ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18, 
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
  [ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1, 
channel_count = 2, sample_rate = 7, sample_size = 7
  [ 8121.022573] PM: resume of devices complete after 412.170 msecs
  [ 8121.023076] acpi LNXPOWER:04: Turning OFF
  [ 8121.023113] PM: Finishing wakeup.
  [ 8121.023114] OOM killer enabled.
  [ 8121.023114] Restarting tasks ...
  [ 8121.023455] pci_bus :04: Allocating resources
  [ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04] 
add_size 1000
  [ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 04] add_size 20 add_align 10
  [ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to 
[bus 04] add_size 20 add_align 10
  [ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
  [ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 
0x0020]
  [ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
  [ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
  [ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
  [ 8121.024358] done.
  [ 8121.082344] video LNXVIDEO:00: Restoring backlight state
  [ 8121.082346] PM: suspend exit
  [ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
  [ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
  [ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
  [ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
  [ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
  [ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
  [ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8122.183439] [drm] RC6 on
  [ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  [ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  [ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring 
  [ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)
  [ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
  
  [Reproduce Steps]
  1. apt-get install -y fwts
  2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60
  
  [Results]
  Expected: pass the S3 stress test
  Actual: system hung at 112nd S3
  
  [Additional Information]
  Kernel Version: 4.15.0-1035-oem
  GPU: AMD RX550 (OPGA14) 1002:699f

-- 
You received this bug notification because you are a member of Kernel

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

2019-04-17 Thread Stefan Bader
** 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
+   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 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 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)
+ derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), 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-4.15), bug 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)
  
  -- 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
-   regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
-   verification-testing: Ongoing -- testing in progress
+   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 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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  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 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-4.15), bug 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)

  -- 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
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 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 16. April 2019 13:04 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 17. April 2019 08:30 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1824592

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 08:30 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/1824592/+subscriptions

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


[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

** 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: Promote to Proposed
- phase-changed: Tuesday, 16. April 2019 16:04 UTC
+ phase: Testing
+ phase-changed: Wednesday, 17. April 2019 08:26 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: 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/1824771

Title:
  linux-aws: 4.18.0-1014.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  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, 17. April 2019 08:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


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

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

apport-collect 1825108

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

Title:
  test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15
  i386

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

Bug description:
  Test failed with 4.15 i386 kernel, didn't see this on other arches

  FAIL: test_260_config_PTI (__main__.KernelSecurityConfigTest)
  Ensure kernel page table isolation is set appropriately
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2566, in test_260_config_PTI
  self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)
File "./test-kernel-security.py", line 210, in assertKernelConfig
  self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 201, in assertKernelConfigUnset
  '%s option was expected to be unset in the kernel config' % name)
  AssertionError: PAGE_TABLE_ISOLATION option was expected to be unset in the 
kernel config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825108/+subscriptions

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


[Kernel-packages] [Bug 1825136] [NEW] ubuntu_nbd_smoke_test failed with 4.15 kernel

2019-04-17 Thread Po-Hsu Lin
Public bug reported:

ubuntu_nbd_smoke_test is failing with 4.15 kernel, can be reproduced on
KVM / bare metals:

creating backing nbd image /tmp/nbd_image.img


Image path: /tmp/nbd_image.img
Mount point: /mnt/nbd-test-11013
Date: Fri Apr 12 00:41:45 UTC 2019
Host: curly
Kernel: 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019
Machine: curly x86_64 x86_64
CPUs online: 2
CPUs total: 2
Page size: 4096
Pages avail: 249824
Pages total: 510259
Free space:
Filesystem Size Used Avail Use% Mounted on
udev 967M 0 967M 0% /dev
tmpfs 200M 752K 199M 1% /run
/dev/vda1 7.3G 4.1G 2.9G 59% /
tmpfs 997M 0 997M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 997M 0 997M 0% /sys/fs/cgroup
tmpfs 200M 0 200M 0% /run/user/1000


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

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

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

creating large file /mnt/nbd-test-11013/largefile
-rw-r--r-- 1 root root 100M Apr 12 00:41 /mnt/nbd-test-11013/largefile

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

removing file /mnt/nbd-test-11013/largefile
unmounting /mnt/nbd-test-11013
stopping client
disconnect, sock, done
Found kernel warning, IO error and/or call trace
echo
[ 487.485530] creating backing nbd image /tmp/nbd_image.img
[ 489.055452] NBD device /dev/nbd0 created
[ 489.755524] found nbd export
[ 490.810667] starting client with NBD device /dev/nbd0
[ 490.819578] creating ext4 on /dev/nbd0
[ 491.171437] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
[ 491.369456] checking ext4 on /dev/nbd0
[ 491.391980] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: 
(null)
[ 491.403665] mounted on /dev/nbd0
[ 491.406022] creating large file /mnt/nbd-test-11013/largefile
[ 492.853579] removing file /mnt/nbd-test-11013/largefile
[ 493.011021] unmounting /mnt/nbd-test-11013
[ 494.062904] stopping client
[ 494.066127] block nbd0: NBD_DISCONNECT
[ 494.066593] block nbd0: shutting down sockets
[ 494.066983] nbd0: detected capacity change from 0 to 134217728
[ 494.067033] print_req_error: I/O error, dev nbd0, sector 0
[ 494.068313] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.069987] print_req_error: I/O error, dev nbd0, sector 0
[ 494.070790] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.071799] print_req_error: I/O error, dev nbd0, sector 0
[ 494.072608] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.073606] ldm_validate_partition_table(): Disk read failed.
[ 494.073613] print_req_error: I/O error, dev nbd0, sector 0
[ 494.074400] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.075390] print_req_error: I/O error, dev nbd0, sector 0
[ 494.076206] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.077208] print_req_error: I/O error, dev nbd0, sector 0
[ 494.077995] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.078985] print_req_error: I/O error, dev nbd0, sector 0
[ 494.079772] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.080771] Dev nbd0: unable to read RDB block 0
[ 494.081734] print_req_error: I/O error, dev nbd0, sector 0
[ 494.082522] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.083518] print_req_error: I/O error, dev nbd0, sector 24
[ 494.084465] Buffer I/O error on dev nbd0, logical block 3, async page read
[ 494.085729] print_req_error: I/O error, dev nbd0, sector 0
[ 494.086517] Buffer I/O error on dev nbd0, logical block 0, async page read
[ 494.087509] nbd0: unable to read partition table
[ 494.171320] Found kernel warning, IO error and/or call trace
[ 494.171374] echo
killing server


Completed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1036-oem 4.15.0-1036.41
ProcVersionSignature: User Name 4.15.0-1036.41-oem 4.15.18
Uname: Linux 4.15.0-1036-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Wed Apr 17 08:44:35 2019
SourcePackage: linux-signed-oem
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug bionic package-from-proposed uec-images

** Package changed: 

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

2019-04-17 Thread bugproxy
--- Comment From sathe...@in.ibm.com 2019-04-17 03:01 EDT---
Tested on host with proposed kernel(4.15.0-48-generic #51) and the issue is 
fixed, this bug can be closed.

Host kernel: 4.15.0-48-generic #51
Guest Kernel: 3.10.0-957.5.1.el7.ppc64le
libvirt-bin4.0.0-1ubuntu8.8
qemu-kvm   1:2.11+dfsg-1ubuntu7.12

Guest Mem: 400G

Guest console:

Red Hat Enterprise Linux Server 7.6 (Maipo)
Kernel 3.10.0-957.5.1.el7.ppc64le on an ppc64le

localhost login: root
Password:
Last login: Wed Apr 17 02:54:58 on hvc0
[root@localhost ~]# ls
anaconda-ks.cfg  original-ks.cfg  perl5
[root@localhost ~]# free -g
totalusedfree  shared  buff/cache   available
Mem:395   3 390   0   1 390
Swap: 4   0   4
[root@localhost ~]# lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):256
On-line CPU(s) list:   0-255
Thread(s) per core:1
Core(s) per socket:1
Socket(s): 256
NUMA node(s):  1
Model: 2.2 (pvr 004e 1202)
Model name:POWER8 (architected), altivec supported
Hypervisor vendor: KVM
Virtualization type:   para
L1d cache: 32K
L1i cache: 32K
NUMA node0 CPU(s): 0-255
[root@localhost ~]# dmesg -l3
[root@localhost ~]#

Regards,
-Satheesh

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

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

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

Bug description:
  == SRU Justification ==

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

  == Fix ==

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

  == Regression Potential ==

  Low. Fix is trivial.

  == Test Case ==

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

  == Original description ==

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

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

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

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

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

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

  Machine Type = power9 ppc64le

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

  2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name 
guest=avocado-vt-vm1,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
 -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid 
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device 
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
 -device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
 -device 

[Kernel-packages] [Bug 1814892] Re: [19.04 FEAT] qeth: Enhanced link speed - kernel part

2019-04-17 Thread Kleber Sacilotto de Souza
Thank you, Frank!

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

Title:
  [19.04 FEAT] qeth: Enhanced link speed - kernel part

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

Bug description:
  SRU Justification:
  --

  * This is more a request (rather than a bug) to add support for the newest 
OSA-Express7S (network-) card,
so that even cosmic and bionic users should be able to benefit from it.

  * The support became upstream accepted with 4.20, mainly with commit

  [Test Case]

  * Due to the absence of that particular card in our (Canonical)
  system, the testing is up to IBM.

  * The recognition of the card type itself can be done via 'lsqeth |
  grep card_type',

  * and the functionality can be tested by network test tools, like
  stress-ng.

  * A regression test can of course be done on our (Canonical) system.

  [Regression Potential]

  * The regression potential can be considered as low since it only
  affects the s390x platform

  * and there only the qeth driver/module.

  * The patch itself is less complex and adds mainly lines and fields
  for the recognition of the new card.

  * The entire code needed is already included in disco and a sniff test was 
done based on disco's kernel 5.0.
  __

  Function:
  Provide enhanced link speed for OSA networks
  Business Case:
  Improved performance with OSA networks

  Available with kernel 4.20
  Git-Commit: s390/qeth: report 25Gbit link speed [54e049c227]

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

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


[Kernel-packages] [Bug 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Promote to Proposed
- phase-changed: Tuesday, 16. April 2019 16:22 UTC
+ phase: Testing
+ phase-changed: Wednesday, 17. April 2019 08:30 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=18/beta'
+   snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=18/edge'
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1037.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=18/beta'
snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=18/edge'
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1824177] Re: dmesg spammed with nvidia-nvlink messages during install

2019-04-17 Thread Alberto Milone
** Changed in: nvidia-graphics-drivers-410 (Ubuntu)
   Status: Confirmed => Invalid

** No longer affects: 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 casper package in Ubuntu:
  Fix Released

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/casper/+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 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 15. April 2019 06:39 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 17. April 2019 08:31 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1822830

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 08:31 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/1822830/+subscriptions

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


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

2019-04-17 Thread Sebastien Bacher
Could you add your journalctl log to the bug after trying the
configuration that does work? Does it work if you change the config from
gnome-control-center?

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  When using super+p there are 4 options:

  - Mirror
  - Join
  - External
  - Built-in

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

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

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

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

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

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


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

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

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

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


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

2019-04-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
- phase: Promote to Proposed
- phase-changed: Tuesday, 16. April 2019 16:32 UTC
+ phase: Testing
+ phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta'
+   snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge'

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

Title:
  linux-aws: 4.4.0-1081.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge'

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

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


[Kernel-packages] [Bug 1824472] Re: Unable to set brightness on Dell G3 3579 with nomodeset

2019-04-17 Thread You-Sheng Yang
Mark INVALID per #5.

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

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

Title:
  Unable to set brightness on Dell G3 3579 with nomodeset

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have Dell inspiron G3.
  I am not able to change the screen brightness. I tried many solutions, but 
none worked.

  1. I tried changing acpi_backlight = vendor:
  Now this does solve but it creates another problem. Because for my laptop to 
shutdown and start properly the LINUX_GRUB_DEFAULT must be set to nomodeset.

  2. I tried installing applications:
  But when I run these applications it show "No backlights were found on the 
system"

  Kindly address the issue and provide a solution. It is causing great
  trouble.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rishita1806 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 11:55:50 2019
  HibernationDevice: RESUME=UUID=b45c9211-82df-4eb1-88ef-95ba16bfe090
  InstallationDate: Installed on 2019-02-28 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G3 3579
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=4aaeabb9-cce5-41e4-8dfd-2a30aaf8d649 ro quiet splash nomodeset 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 05K0D2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/25/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn05K0D2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.sys.vendor: Dell Inc.

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

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


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

2019-04-17 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), 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-4.15), bug 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)
  
  -- 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
-   regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
-   verification-testing: Ongoing -- testing in progress
+   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 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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  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 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-4.15), bug 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)

  -- 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
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 1824841] Re: linux-azure: 4.18.0-1016.16 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1824839 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
- phase: Promote to Proposed
- phase-changed: Tuesday, 16. April 2019 13:04 UTC
+ phase: Testing
+ phase-changed: Wednesday, 17. April 2019 08:27 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1016.16 -proposed tracker

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

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

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

  backports: bug 1824839 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1825145] [NEW] test_072_strict_devmem in ubuntu_qrt_kernel_security failed to build with 5.0 hwe-edge kernel on BIonic

2019-04-17 Thread Po-Hsu Lin
Public bug reported:

This might have something to do with bug 1823994
Test failed to bulild with header not found issue

==
FAIL: test_072_strict_devmem (__main__.KernelSecurityTest)
/dev/mem unreadable for kernel memory
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 614, in test_072_strict_devmem
self.assertShellExitEquals(0, ["make"])
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code 2, expected 0
Command: 'make'
Output:
cc  -Wall -Werror -O2  readmem.c -o readmem -lcap
make -C signpost
make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
make -C /usr/src/linux-headers-5.0.0-8-generic SUBDIRS=$PWD modules
make[2]: Entering directory '/usr/src/linux-headers-5.0.0-8-generic'
make[2]: Makefile: No such file or directory
make[2]: *** No rule to make target 'Makefile'.  Stop.
make[2]: Leaving directory '/usr/src/linux-headers-5.0.0-8-generic'
Makefile:4: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
Makefile:6: recipe for target 'all' failed
make: *** [all] Error 2

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

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

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

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

Title:
  test_072_strict_devmem in ubuntu_qrt_kernel_security failed to build
  with 5.0 hwe-edge kernel on BIonic

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

Bug description:
  This might have something to do with bug 1823994
  Test failed to bulild with header not found issue

  ==
  FAIL: test_072_strict_devmem (__main__.KernelSecurityTest)
  /dev/mem unreadable for kernel memory
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 614, in test_072_strict_devmem
  self.assertShellExitEquals(0, ["make"])
File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
  self.assertEqual(expected, rc, msg + result + report)
  AssertionError: Got exit code 2, expected 0
  Command: 'make'
  Output:
  cc  -Wall -Werror -O2  readmem.c -o readmem -lcap
  make -C signpost
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
  make -C /usr/src/linux-headers-5.0.0-8-generic SUBDIRS=$PWD modules
  make[2]: Entering directory '/usr/src/linux-headers-5.0.0-8-generic'
  make[2]: Makefile: No such file or directory
  make[2]: *** No rule to make target 'Makefile'.  Stop.
  make[2]: Leaving directory '/usr/src/linux-headers-5.0.0-8-generic'
  Makefile:4: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/mem/signpost'
  Makefile:6: recipe for target 'all' failed
  make: *** [all] Error 2

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

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


[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled

2019-04-17 Thread Nivedita Singhvi
** Description changed:

  SRU Justification
  
  Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically.
  
  Fix:
  Fixed by upstream commit in v5.0:
  Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
  "geneve: correctly handle ipv6.disable module parameter"
  
- Hence available in Disco and later; required in X,B,C
- Cherry picked and tested successfully for X, B, C.
+ Hence available in Disco and later; required in X,B,C.
  
  Testcase:
  1. Boot with "ipv6.disable=1"
  2. Then try and create a geneve tunnel using:
-# ovs-vsctl add-br br1
-# ovs-vsctl add-port br1 geneve1 -- set interface geneve1
- type=geneve options:remote_ip=192.168.x.z // ip of the other host
+    # ovs-vsctl add-br br1
+    # ovs-vsctl add-port br1 geneve1 -- set interface geneve1
+ type=geneve options:remote_ip=192.168.x.z // ip of the other host
  
  Regression Potential: Low, only geneve tunnels when ipv6 dynamically
  disabled, current status is it doesn't work at all.
  
  Other Info:
  * Mainline commit msg includes reference to a fix for
-   non-metadata tunnels (infrastructure is not yet in
-   our tree prior to Disco), hence not being included
-   at this time under this case.
+   non-metadata tunnels (infrastructure is not yet in
+   our tree prior to Disco), hence not being included
+   at this time under this case.
  
-   At this time, all geneve tunnels created as above
-   are metadata-enabled.
- 
+   At this time, all geneve tunnels created as above
+   are metadata-enabled.
  
  ---
  [Impact]
  
  When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
  an OS environment with open vswitch, where ipv6 has been disabled,
  the create fails with the error :
  
  “ovs-vsctl: Error detected while setting up 'geneve0': could not
  add network device geneve0 to ofproto (Address family not supported
  by protocol)."
  
  [Fix]
  There is an upstream commit for this in v5.0 mainline (and in Disco and later 
Ubuntu kernels).
  
  "geneve: correctly handle ipv6.disable module parameter"
  Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
  
  This fix is needed on all our series prior to Disco
  and the v5.0 kernel: X, C, B. It is identical to the
  fix we implemented and tested internally with, but had
  not pushed upstream yet.
  
  [Test Case]
  (Best to do this on a kvm guest VM so as not to interfere with
   your system's networking)
  
  1. On any Ubuntu Xenial kernel, disable ipv6. This example
-    is shown with the4.15.0-23-generic kernel (which differs
+    is shown with the 4.15.0-23-generic kernel (which differs
     slightly from 4.4.x in symptoms):
  
  - Edit /etc/default/grub to add the line:
  GRUB_CMDLINE_LINUX="ipv6.disable=1"
  - # update-grub
  - Reboot
  
  2. Install OVS
  # apt install openvswitch-switch
  
  3. Create a Geneve tunnel
  # ovs-vsctl add-br br1
  # ovs-vsctl add-port br1 geneve1 -- set interface geneve1
  type=geneve options:remote_ip=192.168.x.z
  
  (where remote_ip is the IP of the other host)
  
  You will see the following error message:
  
  "ovs-vsctl: Error detected while setting up 'geneve1'.
  See ovs-vswitchd log for details."
  
  From /var/log/openvswitch/ovs-vswitchd.log you will see:
  
  "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system:
  failed to add geneve1 as port: Address family not supported
  by protocol"
  
  You will notice from the "ifconfig" output that the device
  genev_sys_6081 is not created.
  
  If you do not disable IPv6 (remove ipv6.disable=1 from
  /etc/default/grub + update-grub + reboot), the same
  'ovs-vsctl add-port' command completes successfully.
  You can see that it is working properly by adding an
  IP to the br1 and pinging each host.
  
  On kernel 4.4 (4.4.0-128-generic), the error message doesn't
  happen using the 'ovs-vsctl add-port' command, no warning is
  shown in ovs-vswitchd.log, but the device genev_sys_6081 is
  also not created and ping test won't work.
  
  With the fixed test kernel, the interfaces and tunnel
  is created successfully.
  
  [Regression Potential]
  * Low -- affects the geneve driver only, and when ipv6 is
    disabled, and since it doesn't work in that case at all,
    this fix gets the tunnel up and running for the common case.
  
  [Other Info]
  
  * Analysis
  
  Geneve tunnels should work with either IPv4 or IPv6 environments
  as a design and support  principle.
  
  Currently, however, what's in the implementation requires support
  for ipv6 for metadata-based tunnels which geneve is:
  
  rather than:
  
  a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled
  b) ipv4 + metadata + ipv6
  
  What enforces this in the current 4.4.0-x code when opening a Geneve
  tunnel is the following in geneve_open() :
  
  bool ipv6 = geneve->remote.sa.sa_family == AF_INET6;
  bool metadata = geneve->collect_md;
  ...
  
  #if IS_ENABLED(CONFIG_IPV6)
  geneve->sock6 = NULL;
  if (ipv6 || metadata)
   

[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

2019-04-17 Thread Stefan Bader
The latter means that you still have 4.4.0-143 around and could select
that if you had any way of interfacing with the booting server. So you
could go back and confirm the regression happened between 143 and 145.

About IPMI, I don't know how one would do that with Windows, but using a
Linux box, there is a package (name in Ubuntu, might vary on other
distros) called ipmitool which can be used to do the SOL session without
any java and from a terminal window. Of course in any case to see
anything you have to figure out which ttyS# on the server is mapped to
the SOL session (ttyS0 or ttyS1 usually). And then something like
"console=ttyS#,115200n8" has to be added to the default arguments in
/etc/default/grub to tell the kernel to re-direct the console to that
serial port.

just for completeness the command to initial a SOL session would be:
ipmitool -Ilanplus -H -U -P sol activate

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  
  After upgrading our server to this Kernel we experience frequent Kernel 
panics (Attachment).
  Every 3 hours. 
  Our machine has a throuput of about 600 Mbits/s 
  The Panics are around the area of ip6_expire_frag_queue.

__pskb_pull_tail
ip6_dst_lookup_tail
_decode_session6
__xfrm_decode_session
icmpv6_route_lookup
icmp6_send

  
  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488

  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()

  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
   crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
  InstallationDate: Installed on 2018-03-18 (393 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-145-generic N/A
   linux-backports-modules-4.4.0-145-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-145-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1821290] Re: Pop noise when headset is plugged in or removed from GHS/Line-out jack

2019-04-17 Thread Jesse Sung
We have 136824ef and da484d00 in Disco kernel through stable kernel
updates.

** Changed in: hwe-next
   Status: New => Fix Released

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Jesse Sung (wenchien)

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

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1821290

Title:
  Pop noise when headset is plugged in or removed from GHS/Line-out jack

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == SRU Justification ==

  * Impact:
  There's unpleasant pop noise when headset is plugged in or removed from 
GHS/Line-out jack.

  * Fix:
  Issue can be fixed by these four patches. All of them are accepted by 
upstream.
  - 4d4b0c52 - ALSA: hda/realtek - Add unplug function into unplug state of 
Headset Mode for ALC225
  - d1dd4211 - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of 
ALC225
  - 136824ef - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
  - da484d00 - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

  * Testcase:
  Connect/remove a headset to/from the jack and see if there's noise.

  * Risk of Regression:
  Low since these patches only affect specific platforms.

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

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


[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)

2019-04-17 Thread Chris Guiver
No it's NOT listed as off.  When I go there I just take note of what it
says ("Analogue Stereo Output" on this d960 box) and turn the profile so
it says off.  I then re-click the drop-down again to get the list, and
put it back to "Analogue Stereo Output" (for my current box).

It's occurred on Lubuntu, Ubuntu, Ubuntu-Studio in QA-Testing
(http://iso.qa.ubuntu.com/qatracker/reports/bugs/1816394) logs, it
occurs also in debian-testing and has occurred for some time (ie.
year+).

I just pause my music player, vlc or anything that creates sound, and
the chance of it occurring (ie. no sound on resume) is extremely-rare.
(I don't tend to suspend my fedora/opensuse boxes, so I'm not sure if
it's just ubuntu/debian affected sorry).

A program should be playing sound when suspended if trying to re-create
this (as it almost never occurs otherwise, and it's only occasional
anyway).


As for what else I've tried - currently I can't recall anything... This has 
occurred over a number of releases, and I only put it in a bug-report because 
it occurred during my QA-testing sorry - my bad.

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

Title:
  Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed
  via add of pavucontrol)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-Test (LIVE x86_64)

  Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT)
  Two dell displays, left is landscape, right is portrait

  This live test had two packages added:  `vim` & `ubuntu-restricted-
  extras`

  Background:
  I added ubuntu-restricted-extras so I could run requested test on this system 
which had me streaming videos from utube - it was required to get around H264 
errors  (vim because I can't cope with other editors & added `multiverse` to my 
sources.

  Issue:
  With firefox streaming ABC News 24 (local AU news) I suspended machine.  
Waited
  Awoke machine - everything resumed as expected .. Some circling was apparent 
on firefox before picture resumed, however no sound.

  I was unable to fix it using any tools installed - to fix I `sudo apt
  install pavucontrol`, went to Configuration (or last tab) and
  Profile=Off on the drop-down menu, then returned to
  Profile=AnalogStereo Duplex.   This is something I do on occasion for
  this machine on installed system or other machines I use.

  This is really a minor issue, & may not be an issue on an installed
  system (though I come across it semi-regularly & just live with it).
  In regular use I pause/stop sound & know this makes this almost a non-
  issue (almost never happens when sound isn't playing).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 11:01:59 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2019-04-17 Thread fossfreedom
** No longer affects: 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/1821823

Title:
  No wireless networks displayed for broadcom BCM43142

Status in ubiquity package in Ubuntu:
  New

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

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: noSourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1825108] Re: test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15 i386

2019-04-17 Thread Po-Hsu Lin
def test_260_config_PTI(self):
'''Ensure kernel page table isolation is set appropriately'''

expected = True
archs = ['amd64']
if self.kernel_at_least('4.19'):
archs += ['i386']
if self.dpkg_arch not in archs:
self._skipped("KPTI only in amd64 and i386 (4.19 and later)")
expected = False
self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)

The last change to this test seems to be in Jan. this year.

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754

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

Title:
  test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15
  i386

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Test failed with 4.15 i386 kernel, didn't see this on other arches

  FAIL: test_260_config_PTI (__main__.KernelSecurityConfigTest)
  Ensure kernel page table isolation is set appropriately
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2566, in test_260_config_PTI
  self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)
File "./test-kernel-security.py", line 210, in assertKernelConfig
  self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 201, in assertKernelConfigUnset
  '%s option was expected to be unset in the kernel config' % name)
  AssertionError: PAGE_TABLE_ISOLATION option was expected to be unset in the 
kernel config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825108/+subscriptions

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


[Kernel-packages] [Bug 1825108] [NEW] test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15 i386

2019-04-17 Thread Po-Hsu Lin
Public bug reported:

Test failed with 4.15 i386 kernel, didn't see this on other arches

FAIL: test_260_config_PTI (__main__.KernelSecurityConfigTest)
Ensure kernel page table isolation is set appropriately
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2566, in test_260_config_PTI
self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)
  File "./test-kernel-security.py", line 210, in assertKernelConfig
self.assertKernelConfigUnset(name)
  File "./test-kernel-security.py", line 201, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: PAGE_TABLE_ISOLATION option was expected to be unset in the 
kernel config

** Affects: qa-regression-testing
 Importance: Undecided
 Status: New

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

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

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

Title:
  test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15
  i386

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Test failed with 4.15 i386 kernel, didn't see this on other arches

  FAIL: test_260_config_PTI (__main__.KernelSecurityConfigTest)
  Ensure kernel page table isolation is set appropriately
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2566, in test_260_config_PTI
  self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)
File "./test-kernel-security.py", line 210, in assertKernelConfig
  self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 201, in assertKernelConfigUnset
  '%s option was expected to be unset in the kernel config' % name)
  AssertionError: PAGE_TABLE_ISOLATION option was expected to be unset in the 
kernel config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825108/+subscriptions

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


[Kernel-packages] [Bug 1825108] Re: test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15 i386

2019-04-17 Thread Po-Hsu Lin
I think this has something to do with the recent change patch for CVE:
[SRU][Bionic][PULL] Fix for CVE-2017-5754 (i386)

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

Title:
  test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15
  i386

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Test failed with 4.15 i386 kernel, didn't see this on other arches

  FAIL: test_260_config_PTI (__main__.KernelSecurityConfigTest)
  Ensure kernel page table isolation is set appropriately
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 2566, in test_260_config_PTI
  self.assertKernelConfig('PAGE_TABLE_ISOLATION', expected)
File "./test-kernel-security.py", line 210, in assertKernelConfig
  self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 201, in assertKernelConfigUnset
  '%s option was expected to be unset in the kernel config' % name)
  AssertionError: PAGE_TABLE_ISOLATION option was expected to be unset in the 
kernel config

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1825108/+subscriptions

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


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

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

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

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

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

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

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

Title:
  linux-aws: 4.4.0-1081.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Promote to Proposed
  phase-changed: Tuesday, 16. April 2019 16:32 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/1824774/+subscriptions

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


[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled

2019-04-17 Thread Nivedita Singhvi
** Description changed:

  [Impact]
  
  When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
  an OS environment with open vswitch, where ipv6 has been disabled,
  the create fails with the error :
  
  “ovs-vsctl: Error detected while setting up 'geneve0': could not
  add network device geneve0 to ofproto (Address family not supported
  by protocol)."
  
  [Fix]
  There is an upstream commit for this in v5.0 mainline (and in Disco and later 
Ubuntu kernels).
  
  "geneve: correctly handle ipv6.disable module parameter"
  Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
  
  This fix is needed on all our series prior to Disco
  and the v5.0 kernel: X, C, B. It is identical to the
  fix we implemented and tested internally with, but had
  not pushed upstream yet.
  
  [Test Case]
  (Best to do this on a kvm guest VM so as not to interfere with
   your system's networking)
  
  1. On any Ubuntu Xenial kernel, disable ipv6. This example
     is shown with the4.15.0-23-generic kernel (which differs
     slightly from 4.4.x in symptoms):
  
  - Edit /etc/default/grub to add the line:
  GRUB_CMDLINE_LINUX="ipv6.disable=1"
  - # update-grub
  - Reboot
  
  2. Install OVS
  # apt install openvswitch-switch
  
  3. Create a Geneve tunnel
  # ovs-vsctl add-br br1
  # ovs-vsctl add-port br1 geneve1 -- set interface geneve1
  type=geneve options:remote_ip=192.168.x.z
  
  (where remote_ip is the IP of the other host)
  
  You will see the following error message:
  
  "ovs-vsctl: Error detected while setting up 'geneve1'.
  See ovs-vswitchd log for details."
  
  From /var/log/openvswitch/ovs-vswitchd.log you will see:
  
  "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system:
  failed to add geneve1 as port: Address family not supported
  by protocol"
  
  You will notice from the "ifconfig" output that the device
  genev_sys_6081 is not created.
  
  If you do not disable IPv6 (remove ipv6.disable=1 from
  /etc/default/grub + update-grub + reboot), the same
  'ovs-vsctl add-port' command completes successfully.
  You can see that it is working properly by adding an
  IP to the br1 and pinging each host.
  
  On kernel 4.4 (4.4.0-128-generic), the error message doesn't
  happen using the 'ovs-vsctl add-port' command, no warning is
  shown in ovs-vswitchd.log, but the device genev_sys_6081 is
  also not created and ping test won't work.
  
  With the fixed test kernel, the interfaces and tunnel
  is created successfully.
  
  [Regression Potential]
- * Low -- affects the geneve driver only, and when ipv6 is 
-   disabled, and since it doesn't work in that case at all,
-   this fix gets the tunnel up and running for the common case.
- 
+ * Low -- affects the geneve driver only, and when ipv6 is
+   disabled, and since it doesn't work in that case at all,
+   this fix gets the tunnel up and running for the common case.
  
  [Other Info]
  
  * Analysis
  
  Geneve tunnels should work with either IPv4 or IPv6 environments
  as a design and support  principle.
  
  Currently, however, what's in the implementation requires support
  for ipv6 for metadata-based tunnels which geneve is:
  
  rather than:
  
  a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled
  b) ipv4 + metadata + ipv6
  
  What enforces this in the current 4.4.0-x code when opening a Geneve
  tunnel is the following in geneve_open() :
  
  bool ipv6 = geneve->remote.sa.sa_family == AF_INET6;
  bool metadata = geneve->collect_md;
  ...
  
  #if IS_ENABLED(CONFIG_IPV6)
  geneve->sock6 = NULL;
  if (ipv6 || metadata)
  ret = geneve_sock_add(geneve, true);
  #endif
  if (!ret && (!ipv6 || metadata))
  ret = geneve_sock_add(geneve, false);
  
  CONFIG_IPV6 is enabled, IPv6 is disabled at boot, but
  even though ipv6 is false, metadata is always true
  for a geneve open as it is set unconditionally in
  ovs:
  
  In /lib/dpif_netlink_rtnl.c :
  
  case OVS_VPORT_TYPE_GENEVE:
  nl_msg_put_flag(, IFLA_GENEVE_COLLECT_METADATA);
  
  The second argument of geneve_sock_add is a boolean
  value indicating whether it's an ipv6 address family
  socket or not, and we thus incorrectly pass a true
  value rather than false.
  
  The current "|| metadata" check is unnecessary and incorrectly
  sends the tunnel creation code down the ipv6 path, which
  fails subsequently when the code expects an ipv6 family socket.
  
  * This issue exists in all versions of the kernel upto present
     mainline and net-next trees.
  
  * Testing with a trivial patch to remove that and make
    similar changes to those made for vxlan (which had the
    same issue) has been successful. Patches for various
    versions to be attached here soon.
  
  * Example Versions (bug exists in all versions of Ubuntu
-   and mainline):
+   and mainline)
+ 
+ Update: This has been patched upstream after original description filed
+ here, fix available in v5.0 mainline and Disco 

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

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

apport-collect 1825136

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

Title:
  ubuntu_nbd_smoke_test failed with 4.15 kernel

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

Bug description:
  ubuntu_nbd_smoke_test is failing with 4.15 kernel, can be reproduced
  on KVM / bare metals:

  creating backing nbd image /tmp/nbd_image.img

  

  Image path: /tmp/nbd_image.img
  Mount point: /mnt/nbd-test-11013
  Date: Fri Apr 12 00:41:45 UTC 2019
  Host: curly
  Kernel: 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019
  Machine: curly x86_64 x86_64
  CPUs online: 2
  CPUs total: 2
  Page size: 4096
  Pages avail: 249824
  Pages total: 510259
  Free space:
  Filesystem Size Used Avail Use% Mounted on
  udev 967M 0 967M 0% /dev
  tmpfs 200M 752K 199M 1% /run
  /dev/vda1 7.3G 4.1G 2.9G 59% /
  tmpfs 997M 0 997M 0% /dev/shm
  tmpfs 5.0M 0 5.0M 0% /run/lock
  tmpfs 997M 0 997M 0% /sys/fs/cgroup
  tmpfs 200M 0 200M 0% /run/user/1000
  


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

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

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

  creating large file /mnt/nbd-test-11013/largefile
  -rw-r--r-- 1 root root 100M Apr 12 00:41 /mnt/nbd-test-11013/largefile

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

  removing file /mnt/nbd-test-11013/largefile
  unmounting /mnt/nbd-test-11013
  stopping client
  disconnect, sock, done
  Found kernel warning, IO error and/or call trace
  echo
  [ 487.485530] creating backing nbd image /tmp/nbd_image.img
  [ 489.055452] NBD device /dev/nbd0 created
  [ 489.755524] found nbd export
  [ 490.810667] starting client with NBD device /dev/nbd0
  [ 490.819578] creating ext4 on /dev/nbd0
  [ 491.171437] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  [ 491.369456] checking ext4 on /dev/nbd0
  [ 491.391980] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
  [ 491.403665] mounted on /dev/nbd0
  [ 491.406022] creating large file /mnt/nbd-test-11013/largefile
  [ 492.853579] removing file /mnt/nbd-test-11013/largefile
  [ 493.011021] unmounting /mnt/nbd-test-11013
  [ 494.062904] stopping client
  [ 494.066127] block nbd0: NBD_DISCONNECT
  [ 494.066593] block nbd0: shutting down sockets
  [ 494.066983] nbd0: detected capacity change from 0 to 134217728
  [ 494.067033] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.068313] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.069987] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.070790] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.071799] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.072608] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.073606] ldm_validate_partition_table(): Disk read failed.
  [ 494.073613] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.074400] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.075390] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.076206] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.077208] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.077995] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.078985] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.079772] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.080771] Dev nbd0: unable to read RDB block 0
  [ 494.081734] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.082522] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.083518] print_req_error: I/O error, dev nbd0, sector 24

[Kernel-packages] [Bug 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished

2019-04-17 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

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

Bug description:
  On a s390x Bionic / Cosmic KVM, the enosys test is still running even
  the test has completed

  $ ps uax| grep stress
  ubuntu2037  0.0  0.4  93020  9564 ?Ssl  03:46   0:00 python3 
ckct/runner --cloud maas ubuntu_stress_smoke_test
  root  2383  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  root  2384  0.0  0.6  24248 13416 ?S03:46   0:00 
/usr/bin/python -u autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep 
--color=auto stress
  root 19352  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19395  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19449  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root 19481  0.0  0.0  16460   752 ?S03:51   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable

  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  
  04:03:13 WARNI| Please verify 
/home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395
 for more info
  04:03:13 INFO |   GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13   completed successfully
  04:03:13 INFO |   END GOOD
ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
  04:03:13 INFO | END GOOD  timestamp=1555473793
localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0

  And the job on jenkins will eventually times out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  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.9-0ubuntu7.6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1824839] Re: linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => In Progress

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

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1824838 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
- phase: Promote to Proposed
- phase-changed: Tuesday, 16. April 2019 15:39 UTC
+ phase: Testing
+ phase-changed: Wednesday, 17. April 2019 09:12 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: 'Pending -- snap azure-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/beta'
+   snap-release-to-edge: 'Pending -- snap azure-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/edge'
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

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

  derivatives: bug 1824838 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap azure-kernel not in expected 
channel(s):
  arch=amd64:channel=18/beta'
snap-release-to-edge: 'Pending -- snap azure-kernel not in expected 
channel(s):
  arch=amd64:channel=18/edge'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1821271] Re: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

2019-04-17 Thread You-Sheng Yang
Verified bionic-proposed version 4.15.0-48.51 and cosmic-proposed
version 4.18.0-18.19, WiFi interface recognized and connected
automatically.

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

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

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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 Released

Bug description:
  [Impact] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

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

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


[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled

2019-04-17 Thread Nivedita Singhvi
** Description changed:

+ SRU Justification
+ 
+ Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically.
+ 
+ Fix:
+ Fixed by upstream commit in v5.0:
+ Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
+ "geneve: correctly handle ipv6.disable module parameter"
+ 
+ Hence available in Disco and later; required in X,B,C
+ Cherry picked and tested successfully for X, B, C.
+ 
+ Testcase:
+ 1. Boot with "ipv6.disable=1"
+ 2. Then try and create a geneve tunnel using:
+# ovs-vsctl add-br br1
+# ovs-vsctl add-port br1 geneve1 -- set interface geneve1
+ type=geneve options:remote_ip=192.168.x.z // ip of the other host
+ 
+ Regression Potential: Low, only geneve tunnels when ipv6 dynamically
+ disabled, current status is it doesn't work at all.
+ 
+ Other Info:
+ * Mainline commit msg includes reference to a fix for
+   non-metadata tunnels (infrastructure is not yet in
+   our tree prior to Disco), hence not being included
+   at this time under this case.
+ 
+   At this time, all geneve tunnels created as above
+   are metadata-enabled.
+ 
+ 
+ ---
  [Impact]
  
  When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
  an OS environment with open vswitch, where ipv6 has been disabled,
  the create fails with the error :
  
  “ovs-vsctl: Error detected while setting up 'geneve0': could not
  add network device geneve0 to ofproto (Address family not supported
  by protocol)."
  
  [Fix]
  There is an upstream commit for this in v5.0 mainline (and in Disco and later 
Ubuntu kernels).
  
  "geneve: correctly handle ipv6.disable module parameter"
  Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
  
  This fix is needed on all our series prior to Disco
  and the v5.0 kernel: X, C, B. It is identical to the
  fix we implemented and tested internally with, but had
  not pushed upstream yet.
  
  [Test Case]
  (Best to do this on a kvm guest VM so as not to interfere with
   your system's networking)
  
  1. On any Ubuntu Xenial kernel, disable ipv6. This example
     is shown with the4.15.0-23-generic kernel (which differs
     slightly from 4.4.x in symptoms):
  
  - Edit /etc/default/grub to add the line:
  GRUB_CMDLINE_LINUX="ipv6.disable=1"
  - # update-grub
  - Reboot
  
  2. Install OVS
  # apt install openvswitch-switch
  
  3. Create a Geneve tunnel
  # ovs-vsctl add-br br1
  # ovs-vsctl add-port br1 geneve1 -- set interface geneve1
  type=geneve options:remote_ip=192.168.x.z
  
  (where remote_ip is the IP of the other host)
  
  You will see the following error message:
  
  "ovs-vsctl: Error detected while setting up 'geneve1'.
  See ovs-vswitchd log for details."
  
  From /var/log/openvswitch/ovs-vswitchd.log you will see:
  
  "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system:
  failed to add geneve1 as port: Address family not supported
  by protocol"
  
  You will notice from the "ifconfig" output that the device
  genev_sys_6081 is not created.
  
  If you do not disable IPv6 (remove ipv6.disable=1 from
  /etc/default/grub + update-grub + reboot), the same
  'ovs-vsctl add-port' command completes successfully.
  You can see that it is working properly by adding an
  IP to the br1 and pinging each host.
  
  On kernel 4.4 (4.4.0-128-generic), the error message doesn't
  happen using the 'ovs-vsctl add-port' command, no warning is
  shown in ovs-vswitchd.log, but the device genev_sys_6081 is
  also not created and ping test won't work.
  
  With the fixed test kernel, the interfaces and tunnel
  is created successfully.
  
  [Regression Potential]
  * Low -- affects the geneve driver only, and when ipv6 is
    disabled, and since it doesn't work in that case at all,
    this fix gets the tunnel up and running for the common case.
  
  [Other Info]
  
  * Analysis
  
  Geneve tunnels should work with either IPv4 or IPv6 environments
  as a design and support  principle.
  
  Currently, however, what's in the implementation requires support
  for ipv6 for metadata-based tunnels which geneve is:
  
  rather than:
  
  a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled
  b) ipv4 + metadata + ipv6
  
  What enforces this in the current 4.4.0-x code when opening a Geneve
  tunnel is the following in geneve_open() :
  
  bool ipv6 = geneve->remote.sa.sa_family == AF_INET6;
  bool metadata = geneve->collect_md;
  ...
  
  #if IS_ENABLED(CONFIG_IPV6)
  geneve->sock6 = NULL;
  if (ipv6 || metadata)
  ret = geneve_sock_add(geneve, true);
  #endif
  if (!ret && (!ipv6 || metadata))
  ret = geneve_sock_add(geneve, false);
  
  CONFIG_IPV6 is enabled, IPv6 is disabled at boot, but
  even though ipv6 is false, metadata is always true
  for a geneve open as it is set unconditionally in
  ovs:
  
  In /lib/dpif_netlink_rtnl.c :
  
  case OVS_VPORT_TYPE_GENEVE:
  nl_msg_put_flag(, IFLA_GENEVE_COLLECT_METADATA);
  
  The second argument of geneve_sock_add is a boolean

[Kernel-packages] [Bug 1774824] Re: la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi

2019-04-17 Thread Po-Hsu Lin
Hello leonardo,
do you still have this issue with the latest 4.15 kernel on Bionic?
Thanks.

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

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

Title:
  la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  ubuntu budgi x64 bits no me reconoce mi tarjeta wifi Qualcomm Atheros
  AR9287 Wireless Network Adapter

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Jun  2 17:29:50 2018
  InstallationDate: Installed on 2018-06-02 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1823653] Re: Wireless key does not work on Dell G7 7588 with Bionic

2019-04-17 Thread Po-Hsu Lin
Works with dist-upgrade.
To be more precise, it works after upgrading the libudev1 and udev package.

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

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

Title:
  Wireless key does not work on Dell G7 7588 with Bionic

Status in linux-signed package in Ubuntu:
  Fix Released

Bug description:
  The wireless key (fn + PrtScn) does not work on this system.

  "sudo showkey -s" does not return anything
  But it will generate some noise in dmesg:
  [ 1863.388925] keyboard: can't emulate rawmode for keycode 240
  [ 1863.408641] keyboard: can't emulate rawmode for keycode 247
  [ 1863.408667] keyboard: can't emulate rawmode for keycode 247

  
  "sudo showkey -k" will show:
  keycode 240 press
  keycode 247 press
  keycode 247 release

  xev returns:
  KeyPress event, serial 37, synthetic NO, window 0x281,
  root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505),
  state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x281,
  root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505),
  state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 15:58:37 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1825136] Re: ubuntu_nbd_smoke_test failed with 4.15 kernel

2019-04-17 Thread Colin Ian King
*** This bug is a duplicate of bug 1822247 ***
https://bugs.launchpad.net/bugs/1822247

** This bug has been marked a duplicate of bug 1822247
   ubuntu_nbd_smoke_test failed on P9 with Bionic 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/1825136

Title:
  ubuntu_nbd_smoke_test failed with 4.15 kernel

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

Bug description:
  ubuntu_nbd_smoke_test is failing with 4.15 kernel, can be reproduced
  on KVM / bare metals:

  creating backing nbd image /tmp/nbd_image.img

  

  Image path: /tmp/nbd_image.img
  Mount point: /mnt/nbd-test-11013
  Date: Fri Apr 12 00:41:45 UTC 2019
  Host: curly
  Kernel: 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019
  Machine: curly x86_64 x86_64
  CPUs online: 2
  CPUs total: 2
  Page size: 4096
  Pages avail: 249824
  Pages total: 510259
  Free space:
  Filesystem Size Used Avail Use% Mounted on
  udev 967M 0 967M 0% /dev
  tmpfs 200M 752K 199M 1% /run
  /dev/vda1 7.3G 4.1G 2.9G 59% /
  tmpfs 997M 0 997M 0% /dev/shm
  tmpfs 5.0M 0 5.0M 0% /run/lock
  tmpfs 997M 0 997M 0% /sys/fs/cgroup
  tmpfs 200M 0 200M 0% /run/user/1000
  


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

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

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

  creating large file /mnt/nbd-test-11013/largefile
  -rw-r--r-- 1 root root 100M Apr 12 00:41 /mnt/nbd-test-11013/largefile

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

  removing file /mnt/nbd-test-11013/largefile
  unmounting /mnt/nbd-test-11013
  stopping client
  disconnect, sock, done
  Found kernel warning, IO error and/or call trace
  echo
  [ 487.485530] creating backing nbd image /tmp/nbd_image.img
  [ 489.055452] NBD device /dev/nbd0 created
  [ 489.755524] found nbd export
  [ 490.810667] starting client with NBD device /dev/nbd0
  [ 490.819578] creating ext4 on /dev/nbd0
  [ 491.171437] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  [ 491.369456] checking ext4 on /dev/nbd0
  [ 491.391980] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
  [ 491.403665] mounted on /dev/nbd0
  [ 491.406022] creating large file /mnt/nbd-test-11013/largefile
  [ 492.853579] removing file /mnt/nbd-test-11013/largefile
  [ 493.011021] unmounting /mnt/nbd-test-11013
  [ 494.062904] stopping client
  [ 494.066127] block nbd0: NBD_DISCONNECT
  [ 494.066593] block nbd0: shutting down sockets
  [ 494.066983] nbd0: detected capacity change from 0 to 134217728
  [ 494.067033] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.068313] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.069987] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.070790] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.071799] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.072608] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.073606] ldm_validate_partition_table(): Disk read failed.
  [ 494.073613] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.074400] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.075390] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.076206] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.077208] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.077995] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.078985] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.079772] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.080771] Dev nbd0: unable to read RDB block 0
  [ 494.081734] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.082522] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.083518] print_req_error: I/O error, dev nbd0, sector 24
  [ 494.084465] Buffer I/O error on dev nbd0, logical block 3, async page read
  [ 494.085729] print_req_error: I/O error, dev nbd0, sector 0
  [ 494.086517] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 494.087509] nbd0: unable to read partition table
  [ 494.171320] Found kernel warning, IO error and/or call trace
  [ 494.171374] echo
  killing server
  

  1   2   >