date:20181205

Seems like proprietary Nvidia driver is not there for your graphics card:
Kernel modules: nvidiafb, nouveau

** Also affects: nvidia-graphics-drivers (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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806472] Re: RTL8822BE WiFi Disabled in Kernel 4.18.0-12

** Description changed:

+ ===SRU Justification===
+ [Impact]
+ Realtek 8822be doesn't work under kernel lockdown.
+ 
+ [Fix]
+ Add r8822be.ko to signature-inclusion, so it can be signed and be loaded
+ when lockdown is enabled.
+  
+ [Test]
+ Since I can't signed the kernel so it's not tested.
+ 
+ [Regression Potential]
+ Low. The driver is maintained by a Realtek guy, so bugs are actually
+ getting fixed.
+ 
+ ===Original Bug Report===
  Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi 
appears to be unavailable.
  lspci still recognises the installed RTL8822BE card and a reboot back to the 
previous kernel version (4.18.0-11) seems to resolve the problem.
  
  We tried some debugging in the IRC channel and didn't get very far. The
  r8822be module alias is intact, trying to modprobe it or insert results
  in a "operation not permitted" error. Modprobing mac80211 and cfg80211
  which r8822be depends on did not seem to help.
  
  KMod Lists for -12 and -11 kernels:
  https://paste.ubuntu.com/p/pwx5mKszVt/
  
  `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 
/lib/modules/4.18.0-12-*/modules.alias` :
  https://paste.ubuntu.com/p/5zcCbXyM5g/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  callum 2989 F pulseaudio
-  /dev/snd/controlC0:  callum 2989 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  callum 2989 F pulseaudio
+  /dev/snd/controlC0:  callum 2989 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Dec  3 19:27:16 2018
  InstallationDate: Installed on 2018-11-10 (22 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: LENOVO 90H90015UK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=d5f81e09-382c-4759-8a6d-2503fe6959b4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-11-generic N/A
-  linux-backports-modules-4.18.0-11-generic  N/A
-  linux-firmware 1.175.1
+  linux-restricted-modules-4.18.0-11-generic N/A
+  linux-backports-modules-4.18.0-11-generic  N/A
+  linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O3FKT26A
  dmi.board.name: 36E1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259620440547
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO3FKT26A:bd06/15/2018:svnLENOVO:pn90H90015UK:pvrLegionY720T-34ASU:rvnLENOVO:rn36E1:rvrSDK0J40709WIN3259620440547:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: Legion Y720T-34ASU
  dmi.product.name: 90H90015UK
  dmi.product.sku: LENOVO_MT_90H9_BU_LENOVO_FM_Legion Y720T-34ASU
  dmi.product.version: Legion Y720T-34ASU
  dmi.sys.vendor: LENOVO

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

Title:
  RTL8822BE WiFi Disabled in Kernel 4.18.0-12

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ===SRU Justification===
  [Impact]
  Realtek 8822be doesn't work under kernel lockdown.

  [Fix]
  Add r8822be.ko to signature-inclusion, so it can be signed and be loaded
  when lockdown is enabled.
   
  [Test]
  Since I can't signed the kernel so it's not tested.

  [Regression Potential]
  Low. The driver is maintained by a Realtek guy, so bugs are actually
  getting fixed.

  ===Original Bug Report===
  Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi 
appears to be unavailable.
  lspci still recognises the installed RTL8822BE card and a reboot back to the 
previous kernel version (4.18.0-11) seems to resolve the problem.

  We tried some debugging in the IRC channel and didn't get very far.
  The r8822be module alias is intact, trying to modprobe it or insert
  results in a "operation not permitted" error. Modprobing mac80211 and
  cfg80211 which r8822be depends on did not seem to help.

  KMod Lists for -12 and -11 kernels:
  https://paste.ubuntu.com/p/pwx5mKszVt/

  `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 
/lib/modules/4.18.0-12-*/modules.alias` :
  https://paste.ubuntu.com/p/5zcCbXyM5g/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp

[Kernel-packages] [Bug 1806335] Re: Enable new Realtek card reader

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

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

Title:
  Enable new Realtek card reader

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New

Bug description:
  [Impact]
  USB Storage based Realtek card reader doesn't work, because the usb-storage 
module tries to use it in UAS mode instead of using "ums-realtek".

  [Fix]
  Add new IDs to ums-realtek driver.
  In addition to that, we add a new module knob, "enable_mmc=", to 
enable/disable MMC, as vendors may not pay MMC royalties. "enable_mmc" defaults 
to 1.

  [Test]
  After applying the patch, the card reader works, and verified "enable_mmc=" 
can enable/disable MMC support.

  [Regression Potential]
  Minimal. This SRU enables two specific card readers that don't work as UAS, 
the new module knob only introduces new behavior when enable_mmc=0.

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread Aroiu Ovidiu

There is a new version of BIOS for aspire 3 a315-41 (v 1.11) but the
download page is not working at the moment

https://www.acer.com/ac/en/US/content/support-product/7540?b=1

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530

No you don't need to do anything. I'll update the driver in Ubuntu's
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/1787775

Title:
  touchpad not working on lenovo yoga 530

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is not working and does not show up in cat
  /proc/bus/input/devices on multiple kernels. I've tried the newest
  kernel to date (19.08.18) and a few others.

  The touchpad works on windows.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-08-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.3-041803-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1803492] Re: Update AMD PCIe MP2 for AMDI0011

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

** This bug has been marked a duplicate of bug 1787775
   touchpad not working on lenovo yoga 530

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

Title:
  Update AMD PCIe MP2 for AMDI0011

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We need to update AMD PCIe MP2 driver [1] otherwise it breaks some new
  laptops [2].

  [1] https://patchwork.ozlabs.org/patch/997823/
  [2] 
https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1773940/comments/10

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

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

[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence

2018-12-05 Thread Shahar Or

Hey, I've just upgraded from bionic to cosmic and I seem to be hit by
this. Perhaps. What I experience is that while I have an encrypted root,
with the cosmic kernel I don't get a chance to input my passphrase.

Anything I can do to help debug this? I'm a web developer. I can use git
bisect.

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

Title:
  Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
  login screen in a normal sequence

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5
  LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean
  and natural install, no funky custom kernel or drivers or anything...

  Everything worked fine (with the 4.13.* kernel) until I've upgraded
  all my packages (which included the "wonderful" 4.15.0-29 kernel,
  which broke my system).

  Now, everytime I try to boot normally, it asks me for my disk password (I 
have an encrypted LVM) and after that, guess what ?: blank screen. The login 
screen does not appear.
  I can switch the Terminals with Ctrl+Alt+Fx, however.

  However, the same kernel, if I boot it in recovery mode and then I
  select "Resume", the login screen appears, but it lags a little bit...

  Needless to say, if I boot the older kernel (4.13), everything works
  perfectly.

  I dug up some logs and found something like "sddm-greeter"
  segmentation fault in nouveau_dri.so or something like this.

  So, it looks like the new kernel doesn't quite seem to look eye-to-eye
  with nouveau drivers...

  And no, I don't want the NVidia proprietary drivers because I get
  along just perfectly with Nouveau on other machines, and I don't want
  to reinstall nvidia drivers everytime I'm upgrading the kernel.

  And yes, I already have "haveged" installed, to provide sufficient
  entropy (I saw that the possible lack of entropy might be a problem in
  some cases)...

  If I boot in recovery mode and then select "resume", everything works.

  So, what is going on ?

  Any help would be appreciated...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jul 27 10:40:31 2018
  InstallationDate: Installed on 2018-07-04 (22 days ago)
  InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1806570] Re: linux-aws: 4.4.0-1037.40 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:40 UTC
  reason:
-   prepare-package: Version not specified
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded

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

Title:
  linux-aws: 4.4.0-1037.40 -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 upload-to-ppa 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:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:40 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806570] Re: linux-aws: 4.4.0-1037.40 -proposed tracker

2018-12-05 Thread Khaled El Mously

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1037.40 -proposed tracker

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.4.0-1037.40 -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 upload-to-ppa 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:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:40 UTC
  reason:
prepare-package: Version not specified

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

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

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Would it be possible to try 16.04's thermald instead of removing it?

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

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

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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

[Kernel-packages] [Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

2018-12-05 Thread David Jao

OK, false alarm -- 4.4.0-140 is now crashing for me as well. As far as I
know nothing has changed between now and yesterday. Same computer, same
drives, everything. Back to 4.4.0-138 for 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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1806573] Re: linux-aws: 4.4.0-1074.84 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:39 UTC
  reason:
-   prepare-package: Version not specified
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded

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

Title:
  linux-aws: 4.4.0-1074.84 -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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa 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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:39 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3

** Tags added: originate-from-1791001 somerville

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

Title:
  Fix Terminus USB hub that may breaks connected USB devices after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  USB devices connected to Terminus USB hub stop working after S3.

  [Fix]
  The Terminus hub seems to have a rather slow reset command, so we need to 
wait for extra time before doing any further action.

  [Test]
  After applying the fix, USB devices connected to the HUB no longer stop 
functioning after S3.

  [Regression Potential]
  Low. Although the fix affects all devices connect to the HUB, it has no 
functional change other than imposes longer delay time.

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

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

[Kernel-packages] [Bug 1806573] Re: linux-aws: 4.4.0-1074.84 -proposed tracker

2018-12-05 Thread Khaled El Mously

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1074.84 -proposed tracker

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.4.0-1074.84 -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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa 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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:39 UTC
  reason:
prepare-package: Version not specified

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

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

[Kernel-packages] [Bug 1806578] Re: linux-kvm: 4.4.0-1039.45 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:40 UTC
  reason:
-   prepare-package: Version not specified
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded

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

Title:
  linux-kvm: 4.4.0-1039.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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:40 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806578] Re: linux-kvm: 4.4.0-1039.45 -proposed tracker

2018-12-05 Thread Khaled El Mously

** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.4.0-1039.45 -proposed tracker

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-kvm: 4.4.0-1039.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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806569
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 10:40 UTC
  reason:
prepare-package: Version not specified

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

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

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

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

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

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

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

[Kernel-packages] [Bug 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle

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

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

Title:
  PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long
  idle

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Western Digital PC SN720 
NVMe SSD SDAPNTW-256G.

  Short idle: 5.3
  Long idle: 3.0
  S2I: 5.07

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the WD NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 1.66W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

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

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

[Kernel-packages] [Bug 1806428] Re: linux: 3.13.0-164.214 -proposed tracker

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1806429 (linux-lts-trusty)
  derivatives:
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 11:37 UTC
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: 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/1806428

Title:
  linux: 3.13.0-164.214 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806429 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 11:37 UTC
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2018-12-05 Thread Andres Rodriguez

FWIW, I patched ipxe with the CentOS patch as a test, which Vern was going to
test:
https://launchpadlibrarian.net/400355423/ipxe_1.0.0+git-20180124.fbe8c52d-0ubuntu2_1.0.0+git-20180124.fbe8c52d-0ubuntu2.2~18.04.1.diff.gz

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

Title:
iPXE ignores vlan 0 traffic

Status in MAAS:
Invalid
Status in ipxe package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed

Bug description:
I have three MAAS rack/region nodes which are blades in a Cisco UCS
chassis. This is an FCE deployment where MAAS has two DHCP servers,
infra1 is the primary and infra3 is the secondary. The pod VMs on
infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
primary or secondary) then the pod VMs on infra2 will PXE boot but the
pod VMs on the demoted infra node (that no longer serves DHCP) now
fail to PXE boot.

While commissioning a pod VM on infra2 I captured network traffic with
tcpdump on the vnet interface.

Here is the dump when the PXE boot fails (no dhcp server on infra2):
https://pastebin.canonical.com/p/THW2gTSv4S/

Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
https://pastebin.canonical.com/p/HH3XvZtTGG/

The only difference I can see is that in the unsuccessful scenario,
the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
can ping between the blades with no problem. Outgoing packets are
untagged but incoming packets are tagged vlan 0 -- but the ping works.
It seems vlan 0 is used as a part of 802.1p to set priority of
packets. This is separate from vlan, it just happens to use that
ethertype to do the priority tagging.

Someone confirmed to me that, in the iPXE source, it drops all packets
if they are vlan tagged.

The customer is unable to figure out why the packets between blades is
getting vlan tagged so we either need to figure out how to allow iPXE
to accept vlan 0 or the customer will need to use different equipment
for the MAAS nodes.

I found a conversation on the ipxe-devel mailing list that suggested a
commit was submitted and signed off but that was from 2016 so I'm not
sure what became of it. Notable messages in the thread:

http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

Would it be possible to install a local patch as part of the FCE
deployment? I suspect the patch(es) mentioned in the above thread
would require some modification to apply properly.

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

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

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2018-12-05 Thread Vern Hart

Success.
I installed ipxe-qemu from andreserl's ppa and was able to PXE boot a Pod VM 
from the infra node that wasn't running dhcpd.

# add-apt-repository ppa:andreserl/maas
# apt update
# apt install ipxe-qemu
# virsh list --all
# virsh start elastic-3

I watched the console of the VM and it succeeded to get DHCP and PXE
boot.

Subsequently, I used MAAS to deploy to VMs on all three infra nodes,
just to be sure. All succeeded.

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

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

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

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2018-12-05 Thread Mike Pontillo

Setting to 'Confirmed' in the kernel, although it's not clear what the
actual fix would entail. It would certainly be nice to be able to tell a
Linux virtual bridge to transparently strip off priority tags before L2
forwarding occurs. That would prevent the issue with iPXE.

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

** Changed in: ipxe (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/1805920

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

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

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

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

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

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

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

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2018-12-05 Thread Andres Rodriguez

Seems other users in other distros experiencing the same, and a kernel
update fixes the issues? https://serverfault.com/questions/497391/

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

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

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

[Kernel-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency

2018-12-05 Thread Dan Candeto

This also occurs on wireless network connections, and *may* coincide
with my USB mouse seeing lessened throughput.

It appears to be weakly correlated with the amount of load on the
system.  I see no evidence of it occurring at times when the system is
not in use.

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

Title:
  intermittent periods of packet loss and high latency

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Intermittently and unpredictably, ping response times and packet loss
  will spike to unusable levels.  Normal ping times are about .25 ms for
  other hosts on the local network, with essentially no packet loss.
  During the problematic periods (usually lasting 2-10 minutes), packet
  loss jumps to about 50% and ping response times on the packets that
  aren't dropped jump to between 250 and 750 ms.

  This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu
  18.04.  Changing which host on the network I test this with has no
  effect (and during this, those other hosts are able to use the network
  without any problem).  Replacing the cable changes nothing.  Using a
  different Ethernet interface changes nothing.  Replacing the switch
  changes nothing.  This is almost certainly not a hardware problem.

  There is a chance that using wireless instead of Ethernet would fix
  the issue, but I have been avoiding that since the wired connection is
  much faster when Kubuntu is not malfunctioning.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 20 12:48:05 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (711 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via [removed] dev enp0s31f6 proto dhcp metric 100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
   [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH
   enp0s31f6  ethernet  connected 
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b  
/org/freedesktop/NetworkManager/ActiveConnection/5
   [removed]  btdisconnected  /org/freedesktop/NetworkManager/Devices/5 
 --  ----
   wlp3s0 wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 --
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2053 F pulseaudio
   /dev/snd/pcmC1D0c:   dan2053 F...m pulseaudio
   /dev/snd/controlC1:  dan2053 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-12-09 (712 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 
100
  MachineType: Dell Inc. Precision Tower 3420
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-12-05 Thread ALinuxUser

It may be worth my repeating that, despite trying a Windows PreBoot
Environment and a Windows Live Environment - but not full windows,
because I don't have that on the machine - I can't get the latest
touchpad firmware installed.

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version:

[Kernel-packages] [Bug 1806430] Re: linux: 3.2.0-139.185 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 
  derivatives:
  -- swm properties --
- phase: Packaging
- phase-changed: Monday, 03. December 2018 15:31 UTC
+ phase: Uploaded
+ phase-changed: Wednesday, 05. December 2018 21:36 UTC
  reason:
-   prepare-package: Package not yet uploaded
-   prepare-package-lbm: Package not yet uploaded
-   prepare-package-meta: Package not yet uploaded
+   promote-to-proposed: Builds not complete

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

Title:
  linux: 3.2.0-139.185 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: 
  derivatives:
  -- swm properties --
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 21:36 UTC
  reason:
promote-to-proposed: Builds not complete

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-12-05 Thread Pietari Heino

I have the non-NFC model. I'm running Ubuntu 18.10 with the latest
stable kernel (4.19.6) and latest libinput (1.12.1). I have set the
kernel boot parameter psmouse.synaptics_intertouch=0.

I have BIOS 1.34 and the very latest touchpad firmware (released 4th
Dec) (I booted into Windows to install the FW update).

During my initial testing the touchpad has survived multiple suspends
which was most definitely not the case before. For my setup the crucial
thing was the touchpad FW update along with the boot parameter.

I will report here if I encounter further problems.

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A

[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
-   promote-to-proposed: Master bug not ready for proposed
+   promote-to-proposed: Ready for review

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

Title:
  linux-gcp: 4.18.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-to-proposed series:
  Confirmed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
-   promote-to-proposed: Master bug not ready for proposed
+   promote-to-proposed: Ready for review

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

Title:
  linux-kvm: 4.18.0-1006.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 promote-to-proposed series:
  Confirmed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1806409] Re: linux: 4.18.0-13.14 -proposed tracker

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 
(linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), 
bug 1806425 (linux-azure-edge)
  derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 
(linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm)
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 09:33 UTC
  reason:
-   promote-to-proposed: Source package tags missing
+   promote-to-proposed: 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/1806409

Title:
  linux: 4.18.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 
(linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), 
bug 1806425 (linux-azure-edge)
  derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 
(linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 09:33 UTC
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-05 Thread Brian Murray

Could you provide your /var/log/dist-upgrade/main.log file from the
upgrade to Ubuntu 18.04?  Thanks in advance.

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1806409] Re: linux: 4.18.0-13.14 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 
(linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), 
bug 1806425 (linux-azure-edge)
  derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 
(linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm)
  -- swm properties --
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 09:33 UTC
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: Source package tags missing

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

Title:
  linux: 4.18.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 
(linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), 
bug 1806425 (linux-azure-edge)
  derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 
(linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm)
  -- swm properties --
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 09:33 UTC
  reason:
promote-to-proposed: Source package tags missing

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

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

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1806409
- phase: Packaging
- phase-changed: Wednesday, 05. December 2018 17:38 UTC
+ phase: Uploaded
+ phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
-   prepare-package-meta: Package not yet uploaded
-   promote-to-proposed: Source package tags missing
+   promote-to-proposed: Master bug not ready for proposed

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

Title:
  linux-kvm: 4.18.0-1006.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 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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
promote-to-proposed: Master bug not ready for proposed

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

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

[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1806409
- phase: Packaging
- phase-changed: Wednesday, 05. December 2018 16:05 UTC
+ phase: Uploaded
+ phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
-   prepare-package-meta: Package not yet uploaded
-   prepare-package-signed: Package not yet uploaded
-   promote-to-proposed: Source package tags missing
+   promote-to-proposed: Master bug not ready for proposed

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

Title:
  linux-gcp: 4.18.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-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 19:36 UTC
  reason:
promote-to-proposed: Master bug not ready for proposed

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

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

[Kernel-packages] [Bug 1806649] Re: Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter

2018-12-05 Thread Cristian Aravena Romero

Hello,

Source code:
https://github.com/tomaspinho/rtl8821ce

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter

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

Bug description:
  Hello,

  Not work Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE
  802.11ac PCIe Wireless Network Adapter.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2784 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 07:41:10 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 16:05 UTC
  reason:
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded
+   promote-to-proposed: Source package tags missing

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

Title:
  linux-gcp: 4.18.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 16:05 UTC
  reason:
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded
promote-to-proposed: Source package tags missing

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

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

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 17:38 UTC
  reason:
prepare-package-meta: Package not yet uploaded
+   promote-to-proposed: Source package tags missing

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

Title:
  linux-kvm: 4.18.0-1006.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:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 17:38 UTC
  reason:
prepare-package-meta: Package not yet uploaded
promote-to-proposed: Source package tags missing

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread Nikhil Gautam

Sorry, can't give you more data now as I am having my end sem exams in
college, but as soon as they are ie on 12, I will give you more data

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread Nikhil Gautam

Yuup, latest version (1.09).
I was also shocked when worked.

Pic:-

https://drive.google.com/file/d/1BUuJCczocVGFClxiTNGOk1GcnpfKdSLH/view?usp=drivesdk

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1806569] Re: linux: 4.4.0-141.167 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 10:32 UTC
  reason:
-   promote-to-proposed: Source package tags missing
+   promote-to-proposed: 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/1806569

Title:
  linux: 4.4.0-141.167 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
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 is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 10:32 UTC
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1806973] [NEW] zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build

2018-12-05 Thread BertN45

Public bug reported:

Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But ZFS
did work OK after upgrade.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: zfs-dkms 0.7.9-3ubuntu6
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.7.9 for kernel 4.18.0-12-generic (x86_64)
 Wed Dec  5 13:43:02 AST 2018
 make: *** No targets specified and no makefile found.  Stop.
DKMSKernelVersion: 4.18.0-12-generic
Date: Wed Dec  5 13:43:04 2018
InstallationDate: Installed on 2018-01-11 (328 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
PackageVersion: 0.7.9-3ubuntu6
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: zfs-linux
Title: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build
UpgradeStatus: Upgraded to cosmic on 2018-12-05 (0 days ago)

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


** Tags: amd64 apport-package cosmic

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

Title:
  zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But
  ZFS did work OK after upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: zfs-dkms 0.7.9-3ubuntu6
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.7.9 for kernel 4.18.0-12-generic (x86_64)
   Wed Dec  5 13:43:02 AST 2018
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.18.0-12-generic
  Date: Wed Dec  5 13:43:04 2018
  InstallationDate: Installed on 2018-01-11 (328 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  PackageVersion: 0.7.9-3ubuntu6
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build
  UpgradeStatus: Upgraded to cosmic on 2018-12-05 (0 days ago)

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

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

[Kernel-packages] [Bug 1806569] Re: linux: 4.4.0-141.167 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 10:32 UTC
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: Source package tags missing

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

Title:
  linux: 4.4.0-141.167 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
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 is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
  phase: Uploaded
  phase-changed: Wednesday, 05. December 2018 10:32 UTC
  reason:
promote-to-proposed: Source package tags missing

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread siyia

*without

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread siyia

bios version of your laptop?i find it hard to believe that you can boot
with additional kernel parameters

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

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

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

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

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

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

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

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

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

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

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

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

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

2018-12-05 Thread bugproxy

--- Comment From cborn...@de.ibm.com 2018-12-05 12:34 EDT---
Confirmed. I installed bionic,
add bionic-proposed
used virt-install to install a guest
shut down guest
and added a hostdev to guest
started guest:
[root@localhost ~]# lszcrypt
CARD.DOMAIN TYPE  MODESTATUS  REQUEST_CNT
-
06  CEX6A Accelerator online0
06.001a CEX6A Accelerator online0
08  CEX6C CCA-Coproc  online1
08.001a CEX6C CCA-Coproc  online1
0a  CEX6P EP11-Coproc online0
0a.001a CEX6P EP11-Coproc online0

Good to go from proposed into updates.

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

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

Bug description:
  [Impact]

   * The ability to pass through more cryptographic capabilities is a very
     important feature for users of s390x as virtualization platform.
     Its availability upstream now and its backport in this bug allows to
     exploit the crypto cards as new HW for these virtualization use
     cases.

   * This falls under both "other safe cases" SRU exceptions:
  - For Long Term Support releases we regularly want to enable new
    hardware ...
  - For Long Term Support releases we sometimes want to introduce new
    features. They must not change the behaviour on existing
    installations ...

   * This bug has three main components:
     - kernel (ability to do all of this)
     - qemu (add feature to exploit the new code)
     - libvirt (make the feature user consumable)

  [Test Case]

   * In general this consists of a few steps
 - get the updated kernel/qemu/libvirt
 - mask the card & domains from the usual driver
 - load vfio-ap
 - assign card to vfio-ap
 - prepare a guest
 - configure a guest to use the card

   * See comment #66 how to do all of that in detail

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/66

  [Regression Potential]

   * The changes are mostly s390x only and adding a new feature so
     regressions to existing components should be low. But to backport it
     slight changes to the MDEV handling had to be applied as well.
     The potential regressions I can see are in that MDEV handling if one
     of the backports would be bad.
     Fortunately we know that without the related libvirt fixes we added
     here using MDEVs didn't work at all yet, and people very rarely use
     qemu without libvirt for anything else than experiments.
     Therefore I'm confident that even if there would be a flaw in the
     MDEV changes no one is hugely relying on it.

  [Other Info]

   * n/a

  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
- phase-changed: Wednesday, 05. December 2018 09:39 UTC
+ phase-changed: Wednesday, 05. December 2018 17:38 UTC
  reason:
-   prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded

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

Title:
  linux-kvm: 4.18.0-1006.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:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 17:38 UTC
  reason:
prepare-package-meta: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806852] Re: the 4.15.0.42 kernel causes a slower PC

I hope that the report made by "apport-collect 1806852" is complete because the 
screen has become illegible during operation.
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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] Re: the 4.15.0.42 kernel causes a slower PC

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

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

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids

2018-12-05 Thread Cristian Aravena Romero

headphone jack.

** Tags added: 3px63la

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

Title:
  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids

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

Bug description:
  Hello,

  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids.

  In the upper part of gnome-shell it appears that they are with the
  headphones, and it is not like that.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2784 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2784 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 07:59:27 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1806115] Re: cannot set hmcdrv cachesize to 1GB

2018-12-05 Thread Frank Heimes

Yes, since hmcdrv and hmcdrvfs was designed for a different purpose and thus 
not offers whats needed (regarding latency and bandwidth) this can be closed.
Alternatives are under investigation.

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

Title:
  cannot set hmcdrv cachesize to 1GB

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  On an LPAR, execute Customize/Delete Activation Profile. Customize
  profile. In security section, tick "Input/Output (I/O) configuration
  control". Save. Ok. Close.

  Execute Deactivate task.
  Execute Activate task.

  ssh into lpar.

  Try to modprobe hmcdrv module, whilst setting cachesize to 1GiB. Going
  down to the smallest permissible value.

  First, observe that suffixes do not appear to be accepted, despite the
  documentation stating that it should be supported:

  ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=1G
  modprobe: ERROR: could not insert 'hmcdrv': Invalid argument

  ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=512M
  modprobe: ERROR: could not insert 'hmcdrv': Invalid argument

  Next try to request largish amounts of cache, and note how those calls fail:
  $ sudo modprobe hmcdrv cachesize=134217728
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=67108864 
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=33554432
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=16777216
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=8388608  
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=4194304
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=2097152
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=2097152
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  # 1MiB + 2048 bytes
  $ sudo modprobe hmcdrv cachesize=1050624
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=1048576
  $ echo $?
  0

  The LPAR in question is configured with 2000MB of storage
  (RAM/memory), thus imho should be able to handle more than 1MiB
  cachesize, when there are more than 900MiB of free storage:

  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  1.7Gi   348Mi   913Mi   0.0Ki   459Mi   
1.3Gi
  Swap: 1.9Gi  0B   1.9Gi

  Is 1MiB some kind of a cachesize limit of the hmcdrv module? Can it be fixed 
and/or bumped to be unlimited? I'm looking forward to be able to use a 1GiB 
cachesize.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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.
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=0972d5df-b2f2-499e-a787-9fb90b7ebf00 
crashkernel=256M break=bottom BOOT_IMAGE=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco
  Uname: Linux 4.18.0-11-generic s390x
  UpgradeStatus: Upgraded to disco on 2018-11-20 (10 days ago)
  UserGroups: adm cdrom cpacfstats dip kvm libvirt lpadmin lxd plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids

2018-12-05 Thread Cristian Aravena Romero

It seems that it is a hardware problem.

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

Title:
  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids

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

Bug description:
  Hello,

  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids.

  In the upper part of gnome-shell it appears that they are with the
  headphones, and it is not like that.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2784 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2784 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 07:59:27 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1806852] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219512/+files/ProcModules.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219513/+files/PulseList.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219511/+files/ProcInterrupts.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219515/+files/WifiSyslog.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1806852/+attachment/5219514/+files/UdevDb.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1806852/+attachment/5219505/+files/CRDA.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] Re: the 4.15.0.42 kernel causes a slower PC

apport information

** Tags added: apport-collected bionic

** Description changed:

- kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size
- of the display, and a blocking if I try to run "NVIDIA X Server
- Settings". If I chose the kernel 4.15.0.39 at startup the operation of
- ubuntu is normal.
+ kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  jojo   1715 F pulseaudio
+  /dev/snd/controlC0:  jojo   1715 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
+ InstallationDate: Installed on 2017-04-15 (598 days ago)
+ InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp1s7no wireless extensions.
+  
+  enp0s10   no wireless extensions.
+ Lsusb:
+  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
+ ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-42-generic N/A
+  linux-backports-modules-4.15.0-42-generic  N/A
+  linux-firmware 1.173.2
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 4.15.0-42-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
+ UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 01/13/2006
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: F6
+ dmi.board.name: GA-K8NF-9
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219504/+files/AlsaInfo.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1806852] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219506/+files/CurrentDmesg.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219509/+files/ProcCpuinfoMinimal.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219508/+files/ProcCpuinfo.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1806852/+attachment/5219510/+files/ProcEnviron.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1806852] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1806852/+attachment/5219507/+files/Lspci.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/1806852

Title:
  the 4.15.0.42 kernel causes a slower PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the 
display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose 
the kernel 4.15.0.39 at startup the operation of ubuntu is normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jojo   1715 F pulseaudio
   /dev/snd/controlC0:  jojo   1715 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a
  InstallationDate: Installed on 2017-04-15 (598 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp1s7no wireless extensions.
   
   enp0s10   no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago)
  UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark
  _MarkForUpload: True
  dmi.bios.date: 01/13/2006
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-K8NF-9
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr:

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

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

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

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

Title:
  The unsigned vf->num_mac will be decreased to below zero and cause the
  VF port not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The unsigned vf->num_mac in Ubuntu18.04.1 LTS i40e driver 2.1.14-k
  will be decreased to below zero when VF is trying to delete the MAC
  address which is added by PF and then add a new MAC address. And after
  this issue happens, VF won't be able to send/receive packets, and
  excepting for broadcast address, mac_filter_hash is empty in dumped
  VSI info.

  Ubuntu18.04.1 LTS kernel: 4.15.0-38-generic
  i40e driver: 2.1.14-k
  i40evf driver: 3.0.1-k

  Actual results:
  The unsigned vf->num_mac should decrease to below zero. The VF port doesn't 
work.

  Expected results:
  The unsigned vf->num_mac range is from 0 to 65535;
  or the vf is not allowed to delete the MAC addr which is added by PF

  Corresponding Patch is required for resolving this i40e driver issue

  i40e: Prevent deleting MAC address from VF when set by PF
  https://patchwork.ozlabs.org/patch/963036/

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread Nikhil Gautam

I don't know why Manjaro 18 (Gnome) works for me?maybe I got lucky ;-);
clean install, no damn boot args, everything works( brightness keys,
trackpad on advanced, etc), power management works like a charm.

At first, I had a WiFi bug, which was fixed when I updated Manjaro using
ethernet connection.

My laptop is Acer Aspire A315-41(Ryzen 5 2500u).Also, there will be no
WiFi issues if you can use KDE version, but just find it very buggy and
slow, so kept using Gnome

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1806605] Re: linux: -proposed tracker

2018-12-05 Thread Kleber Sacilotto de Souza

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 04. December 2018 10:01 UTC
  reason:
prepare-package: Version not specified

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

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

[Kernel-packages] [Bug 1806845] Re: The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working

2018-12-05 Thread Brian Murray

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

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

Title:
  The unsigned vf->num_mac will be decreased to below zero and cause the
  VF port not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The unsigned vf->num_mac in Ubuntu18.04.1 LTS i40e driver 2.1.14-k
  will be decreased to below zero when VF is trying to delete the MAC
  address which is added by PF and then add a new MAC address. And after
  this issue happens, VF won't be able to send/receive packets, and
  excepting for broadcast address, mac_filter_hash is empty in dumped
  VSI info.

  Ubuntu18.04.1 LTS kernel: 4.15.0-38-generic
  i40e driver: 2.1.14-k
  i40evf driver: 3.0.1-k

  Actual results:
  The unsigned vf->num_mac should decrease to below zero. The VF port doesn't 
work.

  Expected results:
  The unsigned vf->num_mac range is from 0 to 65535;
  or the vf is not allowed to delete the MAC addr which is added by PF

  Corresponding Patch is required for resolving this i40e driver issue

  i40e: Prevent deleting MAC address from VF when set by PF
  https://patchwork.ozlabs.org/patch/963036/

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

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

[Kernel-packages] [Bug 1806604] Re: linux: -proposed tracker

2018-12-05 Thread Kleber Sacilotto de Souza

** Changed in: kernel-sru-workflow
   Status: New => Invalid

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 04. December 2018 10:09 UTC
  reason:
prepare-package: Version not specified

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

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

[Kernel-packages] [Bug 1806845] [NEW] The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working

2018-12-05 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

The unsigned vf->num_mac in Ubuntu18.04.1 LTS i40e driver 2.1.14-k will
be decreased to below zero when VF is trying to delete the MAC address
which is added by PF and then add a new MAC address. And after this
issue happens, VF won't be able to send/receive packets, and excepting
for broadcast address, mac_filter_hash is empty in dumped VSI info.

Ubuntu18.04.1 LTS kernel: 4.15.0-38-generic
i40e driver: 2.1.14-k
i40evf driver: 3.0.1-k

Actual results:
The unsigned vf->num_mac should decrease to below zero. The VF port doesn't 
work.

Expected results:
The unsigned vf->num_mac range is from 0 to 65535;
or the vf is not allowed to delete the MAC addr which is added by PF

Corresponding Patch is required for resolving this i40e driver issue

i40e: Prevent deleting MAC address from VF when set by PF
https://patchwork.ozlabs.org/patch/963036/

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


** Tags: bot-comment i40e
-- 
The unsigned vf->num_mac will be decreased to below zero and cause the VF port 
not working
https://bugs.launchpad.net/bugs/1806845
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 1787405] Re: [FEAT] Guest-dedicated Crypto Adapters

2018-12-05 Thread Christian Ehrhardt 

Verified Bionic with the libvirt+qemu setup outlined in comment #66

Guest starting fine and in the guest:
$ lszcrypt 
CARD.DOMAIN TYPE  MODESTATUS  REQUEST_CNT
-
00  CEX5C CCA-Coproc  online1
00.0016 CEX5C CCA-Coproc  online1

qemu cmdline that was generated:
  -device 
vfio-ap,id=hostdev0,sysfsdev=/sys/bus/mdev/devices/24f952b3-03d1-4df2-9967-0d5f7d63d5f2

Cosmic is still a todo (but not today)

@IBM - will you also test and re-verify this or don't you have
time/motivation as the PPAs were essentially the same?


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

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

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

Bug description:
  [Impact]

   * The ability to pass through more cryptographic capabilities is a very
     important feature for users of s390x as virtualization platform.
     Its availability upstream now and its backport in this bug allows to
     exploit the crypto cards as new HW for these virtualization use
     cases.

   * This falls under both "other safe cases" SRU exceptions:
  - For Long Term Support releases we regularly want to enable new
    hardware ...
  - For Long Term Support releases we sometimes want to introduce new
    features. They must not change the behaviour on existing
    installations ...

   * This bug has three main components:
     - kernel (ability to do all of this)
     - qemu (add feature to exploit the new code)
     - libvirt (make the feature user consumable)

  [Test Case]

   * In general this consists of a few steps
 - get the updated kernel/qemu/libvirt
 - mask the card & domains from the usual driver
 - load vfio-ap
 - assign card to vfio-ap
 - prepare a guest
 - configure a guest to use the card

   * See comment #66 how to do all of that in detail

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/66

  [Regression Potential]

   * The changes are mostly s390x only and adding a new feature so
     regressions to existing components should be low. But to backport it
     slight changes to the MDEV handling had to be applied as well.
     The potential regressions I can see are in that MDEV handling if one
     of the backports would be bad.
     Fortunately we know that without the related libvirt fixes we added
     here using MDEVs didn't work at all yet, and people very rarely use
     qemu without libvirt for anything else than experiments.
     Therefore I'm confident that even if there would be a flaw in the
     MDEV changes no one is hugely relying on it.

  [Other Info]

   * n/a

  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow

[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
- phase-changed: Wednesday, 05. December 2018 09:38 UTC
+ phase-changed: Wednesday, 05. December 2018 16:05 UTC
  reason:
-   prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

Title:
  linux-gcp: 4.18.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 16:05 UTC
  reason:
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 09:39 UTC
  reason:
-   prepare-package: Version not specified
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded

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

Title:
  linux-kvm: 4.18.0-1006.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:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 09:39 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded

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

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

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

2018-12-05 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2018-12-05 10:45 EDT---
@Xnox: Does that mean, we can close it, due to working on alternate solutions???

Many 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/1806115

Title:
  cannot set hmcdrv cachesize to 1GB

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  On an LPAR, execute Customize/Delete Activation Profile. Customize
  profile. In security section, tick "Input/Output (I/O) configuration
  control". Save. Ok. Close.

  Execute Deactivate task.
  Execute Activate task.

  ssh into lpar.

  Try to modprobe hmcdrv module, whilst setting cachesize to 1GiB. Going
  down to the smallest permissible value.

  First, observe that suffixes do not appear to be accepted, despite the
  documentation stating that it should be supported:

  ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=1G
  modprobe: ERROR: could not insert 'hmcdrv': Invalid argument

  ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=512M
  modprobe: ERROR: could not insert 'hmcdrv': Invalid argument

  Next try to request largish amounts of cache, and note how those calls fail:
  $ sudo modprobe hmcdrv cachesize=134217728
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=67108864 
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=33554432
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=16777216
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=8388608  
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=4194304
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=2097152
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=2097152
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  # 1MiB + 2048 bytes
  $ sudo modprobe hmcdrv cachesize=1050624
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=1048576
  $ echo $?
  0

  The LPAR in question is configured with 2000MB of storage
  (RAM/memory), thus imho should be able to handle more than 1MiB
  cachesize, when there are more than 900MiB of free storage:

  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  1.7Gi   348Mi   913Mi   0.0Ki   459Mi   
1.3Gi
  Swap: 1.9Gi  0B   1.9Gi

  Is 1MiB some kind of a cachesize limit of the hmcdrv module? Can it be fixed 
and/or bumped to be unlimited? I'm looking forward to be able to use a 1GiB 
cachesize.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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.
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=0972d5df-b2f2-499e-a787-9fb90b7ebf00 
crashkernel=256M break=bottom BOOT_IMAGE=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco
  Uname: Linux 4.18.0-11-generic s390x
  UpgradeStatus: Upgraded to disco on 2018-11-20 (10 days ago)
  UserGroups: adm cdrom cpacfstats dip kvm libvirt lpadmin lxd plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

2018-12-05 Thread Stefan Bader

** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.18.0-1006.6 -proposed tracker

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

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

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

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

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

Title:
  linux-kvm: 4.18.0-1006.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:
  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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 09:39 UTC
  reason:
prepare-package: Version not specified

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

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

[Kernel-packages] [Bug 1806952] Re: linux: 4.19.0-8.9 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 
  derivatives:
+ -- swm properties --
+ phase: Packaging
+ phase-changed: Wednesday, 05. December 2018 15:33 UTC
+ reason:
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded
+   prepare-package-signed: Package not yet uploaded

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

Title:
  linux: 4.19.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: 
  derivatives:
  -- swm properties --
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 15:33 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806115] Re: cannot set hmcdrv cachesize to 1GB

2018-12-05 Thread Dimitri John Ledkov

Well, we discussed the performance. It seems like this interface is not
meant to be used as a backing storage for rootfs.

Will try other options instead.

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

** Changed in: ubuntu-z-systems
   Status: New => Won't Fix

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

Title:
  cannot set hmcdrv cachesize to 1GB

Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  On an LPAR, execute Customize/Delete Activation Profile. Customize
  profile. In security section, tick "Input/Output (I/O) configuration
  control". Save. Ok. Close.

  Execute Deactivate task.
  Execute Activate task.

  ssh into lpar.

  Try to modprobe hmcdrv module, whilst setting cachesize to 1GiB. Going
  down to the smallest permissible value.

  First, observe that suffixes do not appear to be accepted, despite the
  documentation stating that it should be supported:

  ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=1G
  modprobe: ERROR: could not insert 'hmcdrv': Invalid argument

  ubuntu@s1lp7:~$ sudo modprobe hmcdrv cachesize=512M
  modprobe: ERROR: could not insert 'hmcdrv': Invalid argument

  Next try to request largish amounts of cache, and note how those calls fail:
  $ sudo modprobe hmcdrv cachesize=134217728
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=67108864 
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=33554432
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=16777216
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=8388608  
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=4194304
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=2097152
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=2097152
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  # 1MiB + 2048 bytes
  $ sudo modprobe hmcdrv cachesize=1050624
  modprobe: ERROR: could not insert 'hmcdrv': Cannot allocate memory

  $ sudo modprobe hmcdrv cachesize=1048576
  $ echo $?
  0

  The LPAR in question is configured with 2000MB of storage
  (RAM/memory), thus imho should be able to handle more than 1MiB
  cachesize, when there are more than 900MiB of free storage:

  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  1.7Gi   348Mi   913Mi   0.0Ki   459Mi   
1.3Gi
  Swap: 1.9Gi  0B   1.9Gi

  Is 1MiB some kind of a cachesize limit of the hmcdrv module? Can it be fixed 
and/or bumped to be unlimited? I'm looking forward to be able to use a 1GiB 
cachesize.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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.
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=0972d5df-b2f2-499e-a787-9fb90b7ebf00 
crashkernel=256M break=bottom BOOT_IMAGE=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco
  Uname: Linux 4.18.0-11-generic s390x
  UpgradeStatus: Upgraded to disco on 2018-11-20 (10 days ago)
  UserGroups: adm cdrom cpacfstats dip kvm libvirt lpadmin lxd plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

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

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

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

This change was made by a bot.

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

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

Title:
  Machine will not correctly enter Suspend state (Thinkpad X1 5th gen,
  18.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce: 
  On a Thinkpad X1 Carbon running 18.04 bionic
  Attempt to suspend (using the the 'manual suspend' option from Gnome 
settings, hold down 'power' until changes to 'pause' symbol')

  Expected behaviour:
  machine goes into suspend state, display off, fans off, power led blinking 
slowing to indicate can be woken only by pressing power button

  
  Actual behaviour:
  - display goes off
  - fans shut down
  - physical power button led starts to flash slowing
  - i.e.  machine otherwise appears to go into normal 'suspend' state
  - however, after approximate 1 second, without touching anything:
  - the display wakes back up at the lock screen
  - power led comes back on full
  - machine is back out of suspend, without touching keys or mouse

  Other notes:
  - would appear to be 18.04 specific, as works find under 18.10
  - Lenovo bios version 1.35

  Possibly similiar to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797364
  but they report removing TLP solves problem (my machine does not have TLP 
installed) and they report dmesg errors that I do not see.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dchalmers   3237 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  5 09:00:25 2018
  InstallationDate: Installed on 2018-11-22 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 13d3:5682 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/system-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET50W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET50W(1.35):bd09/10/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread Aroiu Ovidiu

Yes...probably never

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1806952] [NEW] linux: 4.19.0-8.9 -proposed tracker

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

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

backports: 
derivatives:

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

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

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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

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


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.12.05 kernel-sru-master-kernel

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

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

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

** Tags added: disco

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.12.05

** Tags added: kernel-sru-master-kernel

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: 
+ derivatives:

** Summary changed:

-

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  Cherry-picked 3 upstream patches, these patches add the longname of the sound
  card for the dock station.

  
  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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

[Kernel-packages] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged

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

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

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

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

** Changed in: linux (Ubuntu Disco)
   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/1806818

Title:
  Fix Intel I210 doesn't work when ethernet cable gets plugged

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Plugging ethernet cable cannot wake up Intel I210 when it's runtime
  suspended. It's because the PME is not enabled.

  [Fix]
  PCI core doesn't enable PME because the driver explicitly saves its PCI
  state before runtime suspend routine. Don't save PCI state fixes the
  issue. 

  [Test]
  PME is correctly enabled, and cable plugging starts to work.

  [Regression Potential]
  Minimal. The fix limits to on device, and it's specific to runtime power
  management. Other functionalities are not affected.

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

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

[Kernel-packages] [Bug 1806838] Re: Workaround CSS timeout on AMD SNPS 3.0 xHC

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

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

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

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

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

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

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

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

Title:
  Workaround CSS timeout on AMD SNPS 3.0 xHC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  New

Bug description:
  [Impact]
  Raven Ridge xHC may fail to suspend, causes the USB stops working, and blocks 
the system entering system-wide suspend.

  [Fix]
  It's a hardware/firmware bug, workarounded by bailing out suspend function if 
it ever fails, and reset the xHC in next resume function.

  [Test]
  After applying the patch, the USB works, and the system can enter S3 
consecutively.

  [Regression Potential]
  Minimal. This workaround only applies to AMD Raven Ridge xHC.

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

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

[Kernel-packages] [Bug 1806947] [NEW] Machine will not correctly enter Suspend state (Thinkpad X1 5th gen, 18.04)

2018-12-05 Thread David Chalmers

Public bug reported:

Steps to reproduce: 
On a Thinkpad X1 Carbon running 18.04 bionic
Attempt to suspend (using the the 'manual suspend' option from Gnome settings, 
hold down 'power' until changes to 'pause' symbol')

Expected behaviour:
machine goes into suspend state, display off, fans off, power led blinking 
slowing to indicate can be woken only by pressing power button


Actual behaviour:
- display goes off
- fans shut down
- physical power button led starts to flash slowing
- i.e.  machine otherwise appears to go into normal 'suspend' state
- however, after approximate 1 second, without touching anything:
- the display wakes back up at the lock screen
- power led comes back on full
- machine is back out of suspend, without touching keys or mouse

Other notes:
- would appear to be 18.04 specific, as works find under 18.10
- Lenovo bios version 1.35

Possibly similiar to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797364
but they report removing TLP solves problem (my machine does not have TLP 
installed) and they report dmesg errors that I do not see.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-39-generic 4.15.0-39.42
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dchalmers   3237 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  5 09:00:25 2018
InstallationDate: Installed on 2018-11-22 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
 Bus 001 Device 003: ID 13d3:5682 IMC Networks 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HRCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/system-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-39-generic N/A
 linux-backports-modules-4.15.0-39-generic  N/A
 linux-firmware 1.173.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET50W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET50W(1.35):bd09/10/2018:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO

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


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

Title:
  Machine will not correctly enter Suspend state (Thinkpad X1 5th gen,
  18.04)

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce: 
  On a Thinkpad X1 Carbon running 18.04 bionic
  Attempt to suspend (using the the 'manual suspend' option from Gnome 
settings, hold down 'power' until changes to 'pause' symbol')

  Expected behaviour:
  machine goes into suspend state, display off, fans off, power led blinking 
slowing to indicate can be woken only by pressing power button

  
  Actual behaviour:
  - display goes off
  - fans shut down
  - physical power button led starts to flash slowing
  - i.e.  machine otherwise appears to go into normal 'suspend' state
  - however, after approximate 1 second, without touching anything:
  - the display wakes back up at the lock screen
  - power led comes back on full
  - machine is back out of suspend, without touching keys or mouse

  Other notes:
  - would appear to be 18.04 specific, as works find under 18.10
  - Lenovo bios version 1.35

  Possibly similiar to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797364
  but they report removing TLP solves problem (my machine does not have TLP 
installed) and they report dmesg errors that I do not see.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture:

[Kernel-packages] [Bug 1806472] Re: RTL8822BE WiFi Disabled in Kernel 4.18.0-12

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  RTL8822BE WiFi Disabled in Kernel 4.18.0-12

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi 
appears to be unavailable.
  lspci still recognises the installed RTL8822BE card and a reboot back to the 
previous kernel version (4.18.0-11) seems to resolve the problem.

  We tried some debugging in the IRC channel and didn't get very far.
  The r8822be module alias is intact, trying to modprobe it or insert
  results in a "operation not permitted" error. Modprobing mac80211 and
  cfg80211 which r8822be depends on did not seem to help.

  KMod Lists for -12 and -11 kernels:
  https://paste.ubuntu.com/p/pwx5mKszVt/

  `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 
/lib/modules/4.18.0-12-*/modules.alias` :
  https://paste.ubuntu.com/p/5zcCbXyM5g/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  callum 2989 F pulseaudio
   /dev/snd/controlC0:  callum 2989 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Dec  3 19:27:16 2018
  InstallationDate: Installed on 2018-11-10 (22 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: LENOVO 90H90015UK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=d5f81e09-382c-4759-8a6d-2503fe6959b4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O3FKT26A
  dmi.board.name: 36E1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259620440547
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO3FKT26A:bd06/15/2018:svnLENOVO:pn90H90015UK:pvrLegionY720T-34ASU:rvnLENOVO:rn36E1:rvrSDK0J40709WIN3259620440547:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: Legion Y720T-34ASU
  dmi.product.name: 90H90015UK
  dmi.product.sku: LENOVO_MT_90H9_BU_LENOVO_FM_Legion Y720T-34ASU
  dmi.product.version: Legion Y720T-34ASU
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1806472] Re: RTL8822BE WiFi Disabled in Kernel 4.18.0-12

Thanks for your testing.

This means staging drivers don't work when kernel lockdown is enabled.
I'll discuss with kernel team members how to sort this out.

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

Title:
  RTL8822BE WiFi Disabled in Kernel 4.18.0-12

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Received kernel patch 4.18.0-12 today on my machine. On reboot my WiFi 
appears to be unavailable.
  lspci still recognises the installed RTL8822BE card and a reboot back to the 
previous kernel version (4.18.0-11) seems to resolve the problem.

  We tried some debugging in the IRC channel and didn't get very far.
  The r8822be module alias is intact, trying to modprobe it or insert
  results in a "operation not permitted" error. Modprobing mac80211 and
  cfg80211 which r8822be depends on did not seem to help.

  KMod Lists for -12 and -11 kernels:
  https://paste.ubuntu.com/p/pwx5mKszVt/

  `ls -latr /lib/modules/4.18.0-12-*/ ; grep -i B822 
/lib/modules/4.18.0-12-*/modules.alias` :
  https://paste.ubuntu.com/p/5zcCbXyM5g/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  callum 2989 F pulseaudio
   /dev/snd/controlC0:  callum 2989 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Dec  3 19:27:16 2018
  InstallationDate: Installed on 2018-11-10 (22 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: LENOVO 90H90015UK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=d5f81e09-382c-4759-8a6d-2503fe6959b4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O3FKT26A
  dmi.board.name: 36E1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259620440547
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO3FKT26A:bd06/15/2018:svnLENOVO:pn90H90015UK:pvrLegionY720T-34ASU:rvnLENOVO:rn36E1:rvrSDK0J40709WIN3259620440547:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: Legion Y720T-34ASU
  dmi.product.name: 90H90015UK
  dmi.product.sku: LENOVO_MT_90H9_BU_LENOVO_FM_Legion Y720T-34ASU
  dmi.product.version: Legion Y720T-34ASU
  dmi.sys.vendor: LENOVO

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

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

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

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

Title:
  [18.04] update-initramfs fails to generate correct initrd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  I get many trouble in trying to generate a correct initrd.img for the
  following configuration

  clear lvm on /dev/sd4 partition (msdos)
  several logical volumes, some clear and some luks-encrypted
  / et /home on encrypted logical volumes, each with its own 512 byte binary 
key-file on removable device (USB stick)
  /boot et /usr on clear logical volumes

  I am still running 14.04 due to trouble with 16.04, maybe because I
  missed the introduction of the "initramfs" crypttab option. I dropped
  any investigation hoping for the trouble being solved with 18.04. This
  is not the case.

  I run into trouble as soon as I tried to update initrd.img with
  update-initramfs.

  victor-odos goes to /, victor-oikia goes to /home
  I rewrote passdev and stored it in /lib/cryptsetup/bash/passdev

  1/ with crypttab referencing my binary key-files

  victor-odos /dev/mapper/victor-odos_l 
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-odos:1 
luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs
  victor-oikia /dev/mapper/victor-oikia_l 
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-oikia:1 
luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs

  I join two files : /dev/stdout sent to .log and /dev/stderr to .err

  2/ with no key-files

  victor-odos /dev/mapper/victor-odos_l none luks,initramfs
  victor-oikia /dev/mapper/victor-oikia_l none luks,initramfs

  
  I don't know how to bypass this issue 

  
  When this has been solved, I intend to detach luks headers. How to code 
crypttab as I don't know the operational file hierarchy inside initrd ?

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

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

[Kernel-packages] [Bug 1806914] [NEW] [18.04] update-initramfs fails to generate correct initrd

2018-12-05 Thread Arbiel Perlacremaz

Public bug reported:

Hi

I get many trouble in trying to generate a correct initrd.img for the
following configuration

clear lvm on /dev/sd4 partition (msdos)
several logical volumes, some clear and some luks-encrypted
/ et /home on encrypted logical volumes, each with its own 512 byte binary 
key-file on removable device (USB stick)
/boot et /usr on clear logical volumes

I am still running 14.04 due to trouble with 16.04, maybe because I
missed the introduction of the "initramfs" crypttab option. I dropped
any investigation hoping for the trouble being solved with 18.04. This
is not the case.

I run into trouble as soon as I tried to update initrd.img with update-
initramfs.

victor-odos goes to /, victor-oikia goes to /home
I rewrote passdev and stored it in /lib/cryptsetup/bash/passdev

1/ with crypttab referencing my binary key-files

victor-odos /dev/mapper/victor-odos_l 
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-odos:1 
luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs
victor-oikia /dev/mapper/victor-oikia_l 
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-oikia:1 
luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs

I join two files : /dev/stdout sent to .log and /dev/stderr to .err

2/ with no key-files

victor-odos /dev/mapper/victor-odos_l none luks,initramfs
victor-oikia /dev/mapper/victor-oikia_l none luks,initramfs


I don't know how to bypass this issue 


When this has been solved, I intend to detach luks headers. How to code 
crypttab as I don't know the operational file hierarchy inside initrd ?

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


** Tags: bionic cryptsetup crypttab update-initramfs

** Attachment added: "key-files.updt.err"
   
https://bugs.launchpad.net/bugs/1806914/+attachment/5219452/+files/key-files.updt.err

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

Title:
  [18.04] update-initramfs fails to generate correct initrd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  I get many trouble in trying to generate a correct initrd.img for the
  following configuration

  clear lvm on /dev/sd4 partition (msdos)
  several logical volumes, some clear and some luks-encrypted
  / et /home on encrypted logical volumes, each with its own 512 byte binary 
key-file on removable device (USB stick)
  /boot et /usr on clear logical volumes

  I am still running 14.04 due to trouble with 16.04, maybe because I
  missed the introduction of the "initramfs" crypttab option. I dropped
  any investigation hoping for the trouble being solved with 18.04. This
  is not the case.

  I run into trouble as soon as I tried to update initrd.img with
  update-initramfs.

  victor-odos goes to /, victor-oikia goes to /home
  I rewrote passdev and stored it in /lib/cryptsetup/bash/passdev

  1/ with crypttab referencing my binary key-files

  victor-odos /dev/mapper/victor-odos_l 
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-odos:1 
luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs
  victor-oikia /dev/mapper/victor-oikia_l 
/dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-oikia:1 
luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs

  I join two files : /dev/stdout sent to .log and /dev/stderr to .err

  2/ with no key-files

  victor-odos /dev/mapper/victor-odos_l none luks,initramfs
  victor-oikia /dev/mapper/victor-oikia_l none luks,initramfs

  
  I don't know how to bypass this issue 

  
  When this has been solved, I intend to detach luks headers. How to code 
crypttab as I don't know the operational file hierarchy inside initrd ?

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

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

[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker

2018-12-05 Thread Stefan Bader

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.18.0-1005.6 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux-gcp: 4.18.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 09:38 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806423] Re: linux-gcp: 4.18.0-1005.6 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 09:38 UTC
  reason:
-   prepare-package: Version not specified
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded
+   prepare-package-signed: Package not yet uploaded

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

Title:
  linux-gcp: 4.18.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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806409
  phase: Packaging
  phase-changed: Wednesday, 05. December 2018 09:38 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

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

[Kernel-packages] [Bug 1806909] [NEW] Disco update: 4.19.6 upstream stable release

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   4.19.6 upstream stable release
   from git://git.kernel.org/


Linux 4.19.6
media: ov5640: fix auto controls values when switching to manual mode
media: ov5640: fix wrong binning value in exposure calculation
media: ov5640: fix auto gain & exposure when changing mode
media: ov5640: fix exposure regression
media: ov5640: Fix timings setup code
media: ov5640: Re-work MIPI startup sequence
rcu: Make need_resched() respond to urgent RCU-QS needs
gfs2: Fix iomap buffer head reference counting bug
tty: wipe buffer if not echoing data
tty: wipe buffer.
include/linux/pfn_t.h: force '~' to be parsed as an unary operator
dax: Avoid losing wakeup in dax_lock_mapping_entry
mm, page_alloc: check for max order in hot path
tmpfs: make lseek(SEEK_DATA/SEK_HOLE) return ENXIO with a negative offset
mm, memory_hotplug: check zone_movable in has_unmovable_pages
z3fold: fix possible reclaim races
efi/arm: Revert deferred unmap of early memmap mapping
powerpc/numa: Suppress "VPHN is not supported" messages
NFSv4: Fix an Oops during delegation callbacks
kdb: Use strscpy with destination buffer size
drm/amdgpu: fix bug with IH ring setup
RISC-V: Silence some module warnings on 32-bit
riscv: add missing vdso_install target
SUNRPC: Fix a bogus get/put in generic_key_to_expire()
block: copy ioprio in __bio_clone_fast() and bounce
perf/x86/intel/uncore: Add more IMC PCI IDs for KabyLake and CoffeeLake CPUs
sched/fair: Fix cpu_util_wake() for 'execl' type workloads
powerpc/io: Fix the IO workarounds code to work with Radix
floppy: fix race condition in __floppy_read_block_0()
crypto: simd - correctly take reqsize of wrapped skcipher into account
rtc: pcf2127: fix a kmemleak caused in pcf2127_i2c_gather_write
rtc: cmos: Do not export alarm rtc_ops when we do not support alarms
cpufreq: imx6q: add return value check for voltage scale
KVM: PPC: Move and undef TRACE_INCLUDE_PATH/FILE
scsi: hisi_sas: Remove set but not used variable 'dq_list'
scsi: lpfc: fix remoteport access
tools/testing/nvdimm: Fix the array size for dimm devices.
pinctrl: meson: fix meson8b ao pull register bits
pinctrl: meson: fix meson8 ao pull register bits
pinctrl: meson: fix gxl ao pull register bits
pinctrl: meson: fix gxbb ao pull register bits
pinctrl: meson: fix pinconf bias disable
fanotify: fix handling of events on child sub-directory
fsnotify: generalize handling of extra event flags
IB/hfi1: Eliminate races in the SDMA send error path
ACPICA: AML interpreter: add region addresses in global list during 
initialization
can: flexcan: remove not needed struct flexcan_priv::tx_mb and struct 
flexcan_priv::tx_mb_idx
can: flexcan: Always use last mailbox for TX
can: hi311x: Use level-triggered interrupt
can: raw: check for CAN FD capable netdev in raw_sendmsg()
can: flexcan: handle tx-complete CAN frames via rx-offload infrastructure
can: flexcan: use can_rx_offload_queue_sorted() for flexcan_irq_bus_*()
can: rx-offload: rename can_rx_offload_irq_queue_err_skb() to 
can_rx_offload_queue_tail()
can: rx-offload: introduce can_rx_offload_get_echo_skb() and 
can_rx_offload_queue_sorted() functions
can: dev: __can_get_echo_skb(): print error message, if trying to echo non 
existing skb
can: dev: __can_get_echo_skb(): Don't crash the kernel if can_priv::echo_skb is 
accessed out of bounds
can: dev: __can_get_echo_skb(): replace struct can_frame by canfd_frame to 
access frame length
can: dev: can_get_echo_skb(): factor out non sending code to 
__can_get_echo_skb()
can: flexcan: Unlock the MB unconditionally
drm/ast: Remove existing framebuffers before loading driver
drm/ast: fixed cursor may disappear sometimes
drm/ast: change resolution may cause screen blurred
drm/i915: Disable LP3 watermarks on all SNB machines
drm/amdgpu: Fix oops when pp_funcs->switch_power_profile is unset
drm/vc4: Set ->legacy_cursor_update to false when doing non-async updates
drm/amdgpu: Add missing firmware entry for HAINAN
drm/fb-helper: Blacklist writeback when adding connectors to fbdev
tcp: do not release socket ownership in tcp_close()
mm/memory.c: recheck page table entry with page table lock held
mm: don't warn about large allocations for slab
llc: do not use sk_eat_skb()
gfs2: Don't leave s_fs_info pointing to freed memory in init_sbd
sctp: clear the transport of some out_chunk_list chunks in sctp_assoc_rm_peer
bfs: add sanity check at bfs_fill_super()
Input: synaptics - avoid using uninitialized variable when probing
selinux: Add __GFP_NOWARN to allocation at str_read()
v9fs_dir_readdir: fix

[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-05 Thread Barry Kolts

Brian,

On Dec 3rd I installed from xenial-proposed version 1.1ubuntu1.18.04.7~16.04.0.
On Dec 4th unattended-upgrades installed new kernel and rebooted, as it should.
Today, Dec 5 unattended-upgrades removed old kernels, which it should do, and 
then rebooted which it shouldn't do. I have attached unattended-upgrades.log 
for the relevant days.

On a side note unattended-upgrades emailed me after it installed the new
kernel on Dec 4th, as it should, but did not email me after removing old
kernels on Dec 5th. It should have.

Let me know if I can provide any other information or do any further
testing. My system is Ubuntu 16.04.5 LTS server.

Barry

** Attachment added: "unattended-upgrades.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/5219447/+files/unattended-upgrades.log

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-05 Thread siyia

Acer has to provide one ;)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  KVM CLX ACPI HMAT table support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ACPI HMAT table support : HMAT is a new ACPI table that records the
  performance parameter of memory, so MCDRAM (or next gen HBM2) can be
  described well by this table. We need to support this table in kernel
  and qemu so that guest can get and parse this table then to find where
  the high-performance memory is.

  Heterogeneous Memory Attribute Table (HMAT) describes the memory attributes, 
such as memory
   side cache attributes and bandwidth and latency details, related to the 
System Physical Address
   (SPA) Memory Ranges. The software is expected to use this information as 
hint for optimization.

  HMAT is defined in ACPI 6.2: 5.2.27 Heterogeneous Memory Attribute Table 
(HMAT).
  http://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
   patches:
  http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg05368.html

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

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

[Kernel-packages] [Bug 1806863] Re: i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy regulator

2018-12-05 Thread Bug Watch Updater

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201899.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-05T11:33:15+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1806863

dmesg:
i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using dummy 
regulator

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806863/comments/3


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, using
  dummy regulator

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

Bug description:
  Hello,

  dmesg:
  [1.685824] i2c_hid i2c-ELAN2514:00: i2c-ELAN2514:00 supply vdd not found, 
using dummy regulator

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2809 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  5 08:19:35 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (2 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1782212] Re: KVM CLX ACPI HMAT table support

2018-12-05 Thread Christian Ehrhardt 

** Package changed: kvm (Ubuntu) => linux (Ubuntu)

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

Title:
  KVM CLX ACPI HMAT table support

Status in linux package in Ubuntu:
  New

Bug description:
  ACPI HMAT table support : HMAT is a new ACPI table that records the
  performance parameter of memory, so MCDRAM (or next gen HBM2) can be
  described well by this table. We need to support this table in kernel
  and qemu so that guest can get and parse this table then to find where
  the high-performance memory is.

  Heterogeneous Memory Attribute Table (HMAT) describes the memory attributes, 
such as memory
   side cache attributes and bandwidth and latency details, related to the 
System Physical Address
   (SPA) Memory Ranges. The software is expected to use this information as 
hint for optimization.

  HMAT is defined in ACPI 6.2: 5.2.27 Heterogeneous Memory Attribute Table 
(HMAT).
  http://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
   patches:
  http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg05368.html

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

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

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

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

Title:
  Increase DVB_MAX_ADAPTERS from 8 to 16 in kernel config

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed 12 dvb adapters in my setup and noticed, that the
  DVB_MAX_ADAPTERS is still limited to 8 instead of 16. This bug has
  been reported and confirmed in earlier versions of Ubuntu.

  ProblemType: Bug
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: 4.15.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64

  :~$ cat lspci-vnvn.log
   
  00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM 
Controller [8086:29c0]
Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [90] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s, Exit 
Latency L0s <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- 
DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ 
Surprise+
Slot #0, PowerLimit 0.000W; Interlock+ NoCompl-
SltCtl: Enable: AttnBtn+ PwrFlt- MRL- PresDet- CmdCplt+ HPIrq+ 
LinkChg-
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
Address: fee0  Data: 4021
Masking: 0002  Pending: 
Capabilities: [40] Subsystem: Intel Corporation 7500/5520/5500/X58 I/O 
Hub PCI Express Root Port 0 [8086:]
Capabilities: [100 v2] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00,

[Kernel-packages] [Bug 1806430] Re: linux: 3.2.0-139.185 -proposed tracker