date:20190417

** 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 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

** 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 1825071] Re: Super + p does not work as expected, it's defective

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 1825071] Re: Super + p does not work as expected, it's defective

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 1825071] Re: Super + p does not work as expected, it's defective

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 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

** 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 1825071] Re: Super + p does not work as expected, it's defective

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

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

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

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 1825280] Missing required logs.

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

apport-collect 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 1825280] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel

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

** 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 1825280] [NEW] test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel

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 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 1825222] Missing required logs.

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

apport-collect 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 1825272] Re: headset-mic doesn't work on two Dell laptops.

** 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 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 1825222] Re: Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf and aarch64) kernel config?

** 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 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 1825272] Missing required logs.

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

apport-collect 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 1825272] [NEW] headset-mic doesn't work on two Dell laptops.

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 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 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

** 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 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 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker

** 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 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

** 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 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker

** 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 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker

** 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 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

** 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 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 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 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822787 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Testing
  phase-changed: Wednesday, 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 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker

** 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 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 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 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 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 1825229] Missing required logs.

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

apport-collect 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 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 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 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker

** 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 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] 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 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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

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

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

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

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

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

** 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: Promote to Proposed
- phase-changed: Wednesday, 17. April 2019 14:35 UTC
+ phase: Signoff
+ phase-changed: Wednesday, 17. April 2019 17:35 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1822810

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 17:35 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/1822810/+subscriptions

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

[Kernel-packages] [Bug 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update

2019-04-17 Thread Gianfranco Costamagna

** Summary changed:

- Please sync vbox modules from virtualbox 6.0.6 on next kernel update
+ [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update

** Description changed:

+ [SRU Justification]
+ * the changes are already in disco (vbox-guest-dkms), and they are fixes for 
the kernel 5.0.
+ They might seem a lot of changes, but they are needed, and probably some of 
them are even CVE fixes...
+ 
  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

Title:
  [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel
  update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [SRU Justification]
  * the changes are already in disco (vbox-guest-dkms), and they are fixes for 
the kernel 5.0.
  They might seem a lot of changes, but they are needed, and probably some of 
them are even CVE fixes...

  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

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

[Kernel-packages] [Bug 1809624] Re: net test in ubuntu_kernel_selftest failed on s390x KVM

** Summary changed:

- net test in ubuntu_kernel_selftest failed on B s390x KVM
+ net test in ubuntu_kernel_selftest failed on s390x KVM

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

Title:
  net test in ubuntu_kernel_selftest failed on s390x KVM

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

Bug description:
  Verified with the testing tool in the upstream kernel, this issue can
  be reproduced with it.

   not ok 1..4 selftests:  reuseport_dualstack [FAIL]
   selftests: reuseaddr_conflict

  Please find the complete test report here:
  https://pastebin.ubuntu.com/p/3sRh6Nr9KR/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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.5
  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.
  Date: Mon Dec 24 03:10:49 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  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=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-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/1809624/+subscriptions

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

[Kernel-packages] [Bug 1768452] Re: Unable to insert test_bpf module for ubuntu_bpf_jit s390x

** Summary changed:

- Unable to insert test_bpf module for ubuntu_bpf_jit on Xenial s390x
+ Unable to insert test_bpf module for ubuntu_bpf_jit s390x

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

Title:
  Unable to insert test_bpf module for ubuntu_bpf_jit s390x

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

Bug description:
  After the test_bpf insert issue for Xenial was fixed in bug 1765698

  But it looks like the s390x needs some extra work.
  $ sudo modprobe test_bpf
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  4 tests failed here:
test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524

  Complete test result:
  https://pastebin.ubuntu.com/p/zMDwVjwF7X/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-123-generic 4.4.0-123.147
  ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128
  Uname: Linux 4.4.0-123-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed May  2 03:45:22 2018
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-123-generic N/A
   linux-backports-modules-4.4.0-123-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: '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/1768452/+subscriptions

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

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

** Changed in: kernel-sru-workflow/promote-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: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 14:35 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux 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 14:35 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/1822810/+subscriptions

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

[Kernel-packages] [Bug 1825210] Re: Please sync vbox modules from virtualbox 6.0.6 on next kernel update

2019-04-17 Thread Gianfranco Costamagna

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

** Tags added: bot-stop-nagging

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

Title:
  Please sync vbox modules from virtualbox 6.0.6 on next kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

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

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

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

apport-collect 1825210

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

Title:
  Please sync vbox modules from virtualbox 6.0.6 on next kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

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

[Kernel-packages] [Bug 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked

2019-04-17 Thread Pyru

I can confirm using the latest kernel 5.0.7 (Ubuntu 18.10) - The issue
has been fixed.

Thank you.

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

Title:
  Lenovo ideapad 330-15ICH Wifi rfkill hard blocked

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:
  === SRU Justification ===

  [Impact]
  Lenovo ideapad 330-15ICH 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 ===

  The issue here is that the drivers/platform/x86/ideapad_laptop.c
  module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill
  switch, reads the I/O port for its state, gets a zero, and therefore
  reports to the kernel that RFkill is hard-blocked.

  The current workaround is to blacklist the module to stop it being
  loaded.

  I've attached a simple patch for the module that teaches it that this
  model does not have a hardware RF kill switch.

   Original Report -

  Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165
  card, specifically on a Lenovo ideapad 330 laptop.

  A current workaround:

  - Blacklist the "ideapad-laptop" module.
  - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or 
something similar (if it does not already exist), and append "blacklist 
ideapad-laptop" to the file. Save and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dustin 1948 F pulseaudio
   /dev/snd/pcmC0D0p:   dustin 1948 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 04:08:20 2019
  InstallationDate: Installed on 2019-01-15 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210e Acer, Inc
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 3938:1047
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FK
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 
2012" quiet splash nouveau.modeset=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ZCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ICH
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH:
  dmi.product.family: ideapad 330-15ICH
  dmi.product.name: 81FK
  dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH
  dmi.product.version: Lenovo ideapad 330-15ICH
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1825210] [NEW] Please sync vbox modules from virtualbox 6.0.6 on next kernel update

2019-04-17 Thread Gianfranco Costamagna

Public bug reported:

As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
thanks

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: Confirmed


** Tags: bot-stop-nagging

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

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

Title:
  Please sync vbox modules from virtualbox 6.0.6 on next kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

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

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

** 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 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
+ phase: Signoff
+ phase-changed: Wednesday, 17. April 2019 15: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

-- 
You 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:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  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: Signoff
  phase-changed: Wednesday, 17. April 2019 15:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/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 1825108] Re: test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15 i386

2019-04-17 Thread Tyler Hicks

Fix: https://git.launchpad.net/qa-regression-
testing/commit/?id=b5f561affe4eb739c5b01b88569618d59ae6f664

** Changed in: qa-regression-testing
   Status: In Progress => Fix Released

** Changed in: ubuntu-kernel-tests
   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/1825108

Title:
  test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15
  i386

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

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

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

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

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

** Changed in: kernel-sru-workflow/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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Promote to Proposed
- phase-changed: Wednesday, 17. April 2019 13:26 UTC
+ phase: Signoff
+ phase-changed: Wednesday, 17. April 2019 15:07 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
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/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 1822692] Re: Please ship the ib_uverbs driver module in the main modules package

2019-04-17 Thread Kamal Mostafa

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

-- 
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:
  New
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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 12. April 2019 15:29 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 17. April 2019 14:35 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/1822810

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

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

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

[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled

2019-04-17 Thread Nivedita Singhvi

Submitted SRU request for Bionic, Cosmic.

Huge thanks for the testing, Matthew!

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

Title:
  Geneve tunnels don't work when ipv6 is disabled

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

Bug description:
  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.

  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 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)
  ret = geneve_sock_add(geneve, true);
  #endif

[Kernel-packages] [Bug 1825108] Re: test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15 i386

2019-04-17 Thread Tyler Hicks

** Changed in: qa-regression-testing
   Status: Triaged => In Progress

** Changed in: qa-regression-testing
   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/1825108

Title:
  test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15
  i386

Status in QA Regression Testing:
  In Progress
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid

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 1790595] Re: Line 6 POD HD500 driver fault

2019-04-17 Thread Kai-Heng Feng

It was
[ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
[ 165.844742] usb 1-1: selecting invalid altsetting 1

Now the altsetting is correct:
[  183.317968] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found
[  183.322074] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now attached

So it's a different issue if it still doesn't work.

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

Title:
  Line 6 POD HD500 driver fault

Status in linux package in Ubuntu:
  Confirmed

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

  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  uname:

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

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


  dmesg:

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

[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled

2019-04-17 Thread Nivedita Singhvi

** Tags added: cosmic xenial

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

Title:
  Geneve tunnels don't work when ipv6 is disabled

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

Bug description:
  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.

  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 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)
  ret = geneve_sock_add(geneve, true);
  #endif
  if (!ret && (!ipv6 || metadata))

[Kernel-packages] [Bug 1825108] Re: test_260_config_PTI in ubuntu_qrt_kernel_security failed with 4.15 i386

2019-04-17 Thread Tyler Hicks

QRT does need to be updated now that Bionic has received the
CVE-2017-5754 mitigations for i386. I can update QRT.

(There is no kernel bug to fix from this failure)

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

** Changed in: qa-regression-testing
   Status: New => Triaged

** Changed in: qa-regression-testing
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

-- 
You 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:
  Triaged
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid

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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -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/1822810

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux 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: Friday, 12. April 2019 15:29 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/1822810/+subscriptions

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

[Kernel-packages] [Bug 1824953] Re: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned

2019-04-17 Thread Daniel Holbach

dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  libgtk2.0-0:amd64 -> libc-bin
 packages' pending triggers which are or may be unresolvable:
  linux-image-5.0.0-11-generic: linux-update-5.0.0-11-generic
  install-info: /usr/share/info
  sgml-base: /usr/share/xml: update-sgmlcatalog: /etc/sgml: /usr/share/sgml
  shared-mime-info: /usr/share/mime/packages
  dbus: /etc/dbus-1/system.d
  ca-certificates: update-ca-certificates
  systemd: /etc/init.d
  libc-bin: ldconfig
  libgtk2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules
  dictionaries-common: update-default-ispell: update-default-wordlist: 
aspell-autobuildhash
  cups: /usr/share/cups/ppd-updaters
  hicolor-icon-theme: /usr/share/icons/hicolor
  initramfs-tools: update-initramfs
  mime-support: /usr/share/applications: /usr/lib/mime/packages
dpkg: error processing package linux-image-5.0.0-11-generic (--configure):
 triggers looping, abandoned

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgrade from cosmic to disco.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-11-generic 5.0.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 3431 F pulseaudio
  Date: Tue Apr 16 09:01:08 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-14 (366 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  SourcePackage: linux
  Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-16 (0 days ago)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

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

Maybe understanding how the configuration:interface:altsetting:endpoint
is arranged on this usb device is helpful.

Could you please collect 2 logs:

1st: sudo su;cat /sys/kernel/debug/usb/devices > devices.txt

2nd: lsusb -d 0e41:414d -v > lsusb-v.txt

Then upload these two logs.

thx.

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

Title:
  Line 6 POD HD500 driver fault

Status in linux package in Ubuntu:
  Confirmed

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

  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  uname:

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

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


  dmesg:

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

[Kernel-packages] [Bug 1822036] Re: Add devicetree overlay to support the SLB9670 TPM module for RPi

2019-04-17 Thread Stefan Bader

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

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

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

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

Title:
  Add devicetree overlay to support the SLB9670 TPM module for RPi

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * Currently it is not possible to use the SLB9670 TPM module with
  Ubuntu Core since we do not ship the required devicetree overlay to
  enable it
  
https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed
  and there is no way for snaps to easily add their own devicetree
  overlay. Finally it is not practical to expect Ubuntu Core users to
  have to build and maintain their own kernels just to support a
  particular hardware device.

  For background discussion, refer to this thread on the snapcraft
  forums - https://forum.snapcraft.io/t/guidance-on-snap-interface-to-
  load-a-device-tree-overlay-on-rpi-core18/10106/11

   * Once this overlay is added, then users simply need to modify the
  boot config.txt to enable the overlay to be loaded automatically. In
  the future, snapd might also enable support so this can be managed by
  snapd via snap system configuration.

  [Test Case]

   * Boot a RPi with a SLB9670 connected, modify /boot/config.txt to
  specify dtoverlay=tpm-slb9670, then load the tpm_tis_spi module and
  /dev/tpm0 should the be available.

  [Regression Potential]

   * Almost zero chance of regression potential since this is simply
  adding a new overlay to the kernel. This is not loaded automatically
  so there is no real chance of regression.

  [Other Info]
   
   * All that is required for this SRU is to merge 
https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed
 to the current bionic raspi kernel branch.

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

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

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

2019-04-17 Thread Stefan Bader

** Tags added: kernel-block-proposed

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

Title:
  linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822817
  phase: Signoff
  phase-changed: Tuesday, 16. April 2019 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker

2019-04-17 Thread Stefan Bader

** Tags added: kernel-block-proposed

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

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

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1822834
  phase: Packaging
  phase-changed: Tuesday, 16. April 2019 07:10 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 13:26 UTC
  reason:
-   promote-signing-to-proposed: Ongoing -- review in progress
+   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
+ sync

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Fix Committed
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:
  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 13:26 UTC
  reason:
promote-signing-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/1824592/+subscriptions

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

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

** 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: Wednesday, 17. April 2019 13:18 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 17. April 2019 13:26 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-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:
  In Progress
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:
  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 13:26 UTC
  reason:
promote-signing-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 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker

2019-04-17 Thread Andy Whitcroft

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  In Progress
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:
  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 13:26 UTC
  reason:
promote-signing-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 1824592] Re: linux-fips: 4.15.0-1005.6 -proposed tracker

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Promote to Proposed
- phase-changed: Wednesday, 17. April 2019 08:30 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 17. April 2019 13:18 UTC
  reason:
-   promote-signing-to-proposed: Holding -- builds not complete
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-signing-to-proposed: Pending -- ready for review

-- 
You 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:
  In Progress
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:
  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: Wednesday, 17. April 2019 13:18 UTC
  reason:
promote-signing-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 1824841] Re: linux-azure: 4.18.0-1016.16 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 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

-- 
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

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

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

  backports: bug 1824839 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: 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
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 1824841] Re: linux-azure: 4.18.0-1016.16 -proposed tracker

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  New

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

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

  backports: bug 1824839 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: 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
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 1824839] Re: linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  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-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
- arch=amd64:channel=18/candidate:rev=52'
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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

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

  derivatives: bug 1824838 (linux-azure-edge)

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 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-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
- arch=amd64:channel=18/candidate:rev=68'
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

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- 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-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
- arch=amd64:channel=latest/candidate:rev=67'

-- 
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 1825074] Re: amdgpu resume failure: failed to allocate wb slot

2019-04-17 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  amdgpu resume failure: failed to allocate wb slot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [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.

[Kernel-packages] [Bug 1824953] Re: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned

2019-04-17 Thread Seth Forshee

There should have been some output about the triggers involved in the
loop; did you capture that? If not you might find it in
/var/log/apt/term.log.

My suspicion is that the problem lies in some other package's triggers
since the kernel triggers haven't changes since cosmic.

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgrade from cosmic to disco.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-11-generic 5.0.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 3431 F pulseaudio
  Date: Tue Apr 16 09:01:08 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-14 (366 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  SourcePackage: linux
  Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-16 (0 days ago)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

** 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: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 08:30 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/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:
  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 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-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/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 1821823] Re: No wireless networks displayed for broadcom BCM43142

2019-04-17 Thread Łukasz Zemczak

I have prepared and uploaded a fix for that into the disco queue. We are
reverting this change as it seems to be a regression from expected
behavior - even man dkms (or checking the manpage on their github
upstream repo) mentions `dkms uninstall` leaving the module in the
'built' state. I suspect that for us this change should be relatively
safe. But who knows.

Not sure if it'll make it for the disco release though. In case we're
respinning, we'll be sure to get that in along with the other changes
(after review).

Thanks for reporting this!

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

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

Title:
  No wireless networks displayed for broadcom BCM43142

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

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/dkms/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-04-17 Thread Yaroslav

Thank you @Santiago Londoño. I spend a lot of hours trying to fix this
problem on my ux533fd. You saved me)

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

2019-04-17 Thread Georgi Boiko

Thanks for tipping me off. Support for 5.x kernels was added in
390.>=116 (legacy branch) and the 418.>=43 (bleeding edge) drivers, but
not to the current stable or any other branch, so it was failing for me.

Mainline 5.0.8 with 418.56 also works fine, so it's "just" the LTS
kernel branches that have the bug. Back to running mainline Frankenbuntu
on prod I suppose.

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

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

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

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

Steps to reproduce:

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

Errors in dmesg indicate that i915 driver is somehow involved:

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

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

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

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

Other reports that may be related:

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

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

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

[Kernel-packages] [Bug 1824839] Re: linux-azure: 4.18.0-1016.16~18.04.1 -proposed tracker

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1824838 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   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'
+   snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/candidate:rev=52'
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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

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

  derivatives: bug 1824838 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1824841
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
  arch=amd64:channel=18/candidate:rev=52'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 08:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   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'
+   snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
+ arch=amd64:channel=18/candidate:rev=68'
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:
  Confirmed
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
snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
  arch=amd64:channel=18/candidate:rev=68'
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 1819305] Re: Synaptic touchpad not working

Hello,
it looks like this is a fresh install,
does it work with the updated kernel on Bionic? (4.15.0-47, you can upgrade 
your system with the software updater)
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/1819305

Title:
  Synaptic touchpad not working

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  nan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 10:17:53 2019
  InstallationDate: Installed on 2019-03-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Testing
  phase-changed: Wednesday, 17. April 2019 09:09 UTC
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   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'
+   snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
+ arch=amd64:channel=latest/candidate:rev=67'

-- 
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:
  Confirmed
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
snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
  arch=amd64:channel=latest/candidate:rev=67'

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 1823126] Re: touchpad doesn't work (not listed in xinput)

Hello,
did you perform an update before this issue happened?

If yes, can you boot to an older kernel to confirm if it's a regression to the 
new kernel?
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/1823126

Title:
  touchpad doesn't work (not listed in xinput)

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  My touchpad worked yesterday, but today it is not working.
  I tried to search all information about synaptics touchpad on my Xubuntu 
16.04 but touchpad information are not listed with xinput and other command.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  4 09:21:52 2019
  InstallationDate: Installed on 2017-11-06 (513 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/1823126/+subscriptions

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

[Kernel-packages] [Bug 1774824] Re: la nueva versión de mi ubuntu budgi x64 bits no reconoce tarjeta wiffi

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

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

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

2019-04-17 Thread Łukasz Zemczak

So essentially this is the change that 'broke' dkms:

https://github.com/dell/dkms/commit/0c19129b5d1f8e03498f6f2455ad9f7e14e9e606

I think per expected behavior we should actually *not* be removing
modules from the dkms tree on uninstall, right? This is a regression,
not sure why someone actually got that in. Reverting it fixes the world.

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed => In Progress

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

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

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

** Changed in: ubiquity (Ubuntu)
   Status: In Progress => Invalid

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

** Changed in: dkms (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  No wireless networks displayed for broadcom BCM43142

Status in dkms package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Invalid

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/dkms/+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 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished

2019-04-17 Thread Colin Ian King

Fix committed: https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=66c09c1a1b73d58855173474daaec98138926e62

Was accidentally killing a child before that child could complete a wait
and reap of it's own child.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Committed

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 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822833 (trusty/linux-lts-xenial), bug 1824775 
(trusty/linux-aws)
  derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 
(linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
-   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 in Ubuntu.
https://bugs.launchpad.net/bugs/1822834

Title:
  linux: 4.4.0-146.172 -proposed tracker

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

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

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

  backports: bug 1822833 (trusty/linux-lts-xenial), bug 1824775 
(trusty/linux-aws)
  derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 
(linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

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

[Kernel-packages] [Bug 1801975] Re: update to build for 4.19

2019-04-17 Thread Thadeu Lima de Souza Cascardo

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

** Also affects: dm-writeboost (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: dm-writeboost (Ubuntu Bionic)
   Status: New => In Progress

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

** Changed in: dm-writeboost (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: dm-writeboost (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Description changed:

+ [Impact]
+ dm-writeboost-dkms won't build with bionic/linux-hwe-edge 5.0.
+ 
+ [Test case]
+ Test that the dkms now builds with 5.0 kernel and still builds with 4.15 
kernel.
+ 
+ [Regression potential]
+ The module may not build anymore on older kernels, that has been tested.
+ ===
+ 
  dm-writeboost-dkms fails to build on linux 4.19.

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

Title:
  update to build for 4.19

Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in dm-writeboost source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in dm-writeboost source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid

Bug description:
  [Impact]
  dm-writeboost-dkms won't build with bionic/linux-hwe-edge 5.0.

  [Test case]
  Test that the dkms now builds with 5.0 kernel and still builds with 4.15 
kernel.

  [Regression potential]
  The module may not build anymore on older kernels, that has been tested.
  ===

  dm-writeboost-dkms fails to build on linux 4.19.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+subscriptions

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

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