[Kernel-packages] [Bug 1837567] Re: disco/linux-azure: 5.0.0-1013.13 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1838087 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Monday, 29. July 2019 12:21 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 06. August 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1838087
  variant: debs

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

Title:
  disco/linux-azure: 5.0.0-1013.13 -proposed tracker

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

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

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

  backports: bug 1838087 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1838087
  variant: debs

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Khaled El Mously]

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  SRU justication:
  =
  [Impact]
  Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
  based chroot with the current bionic-proposed kernel (4.15.0-56-generic
  #62-Ubuntu).

  [Fix]
  Fix protential NULL in overlay fs.

  [Test]
  Verified on fs test and dpkg installation on overlayfs.

  [Regression Potential]
  Low, remove regression of previous bionic kernel.

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

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

[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18042

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

Title:
  System crashes on hot adding a core with drmgr command
  (4.15.0-48-generic)

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

Bug description:
  [Impact]
  On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to 
crash. The patches identified to fix these issues disables changing the NUMA 
associations for CPUs and Memory at runtime by default.

  [Test]
  # drmgr -c cpu -r -q 1
  # drmgr -c cpu -a -q 1
  Test kernel available in ppa:ubuntu-power-triage/lp1833716
  Please see comment #2 for before and after results with the patches applied.

  [Fix]
  558f86493df0 powerpc/numa: document topology_updates_enabled, disable by 
default
  2d4d9b308f8f powerpc/numa: improve control of topology updates

  [Regression Potential]
  The two patches relate to powerpc/numa and does not impact other 
architectures or platform code. Regression potential is low.

  [Other Information]
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-07 
13:18:35 ==
  ---Problem Description---
  On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the 
kernel
  with below traces:

  ---
  root@ubuntu:~# drmgr -c cpu -r -q 1
  Validating CPU DLPAR capability...yes.
  CPU 9
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~# drmgr -c cpu -a -q 1
  Validating CPU DLPAR capability...yes.
  [  218.555493] BUG: arch topology borken
  [  218.03]  the DIE domain not a subset of the NODE domain
  [  218.12] BUG: arch topology borken
  [  218.16]  the DIE domain not a subset of the NODE domain
  [  218.23] BUG: arch topology borken
  [  218.28]  the DIE domain not a subset of the NODE domain
  [  218.35] BUG: arch topology borken
  [  218.39]  the DIE domain not a subset of the NODE domain
  [  218.45] BUG: arch topology borken
  [  218.50]  the DIE domain not a subset of the NODE domain
  [  218.56] BUG: arch topology borken
  [  218.60]  the DIE domain not a subset of the NODE domain
  [  218.67] BUG: arch topology borken
  [  218.71]  the DIE domain not a subset of the NODE domain
  [  218.77] BUG: arch topology borken
  [  218.81]  the DIE domain not a subset of the NODE domain
  [  218.555672] Unable to handle kernel paging request for data at address 
0x9332ae80f961139f
  [  218.555679] Faulting instruction address: 0xc01768cc
  [  218.555686] Oops: Kernel access of bad area, sig: 11 [#1]
  [  218.555691] LE SMP NR_CPUS=2048 NUMA pSeries
  [  218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum
  [  218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 
4.15.0-48-generic #51-Ubuntu
  [  218.555757] Workqueue: events cpuset_hotplug_workfn
  [  218.555763] NIP:  c01768cc LR: c01769a8 CTR: 

  [  218.555770] REGS: c001f5f1f530 TRAP: 0380   Not tainted  
(4.15.0-48-generic)
  [  218.555776] MSR:  80009033   CR: 22824228  
XER: 0004
  [  218.555789] CFAR: c0176920 SOFTE: 1
  [  218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 
c001f7bfd200
  [  218.555789] GPR04: 0001  0008 
0010
  [  218.555789] GPR08: 0018  c001f7bfd408 

  [  218.555789] GPR12: 8000 c7a35800 0007 
c001f549d900
  [  218.555789] GPR16: 0040 c1722494 c001f0f29400 
0001
  [  218.555789] GPR20: c001ffb68580 0008 c11d8580 
c171dd78
  [  218.555789] GPR24:  e830 ec30 
12af
  [  218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 
9332ae80f961139f
  [  218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0
  [  218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0
  [  218.555871] Call Trace:
  [  218.555875] [c001f5f1f7b0] [ec30] 0xec30 
(unreliable)
  [  218.555884] [c001f5f1f7f0] [c01769a8] 
destroy_sched_domain+0x38/0xc0
  [  218.555892] [c001f5f1f820] [c0176eb0] 
cpu_attach_domain+0xf0/0x870
  [  218.555900] [c001f5f1f960] [c0178884] 
build_sched_domains+0x1254/0x12f0
  [  

[Kernel-packages] [Bug 1827228] Re: nVidia-340 driver install failed, black screen upon boot and hanging

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  nVidia-340 driver install failed, black screen upon boot and hanging

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  Hello all,
  I was trying to install nVidia driver 340 onto Kbuntu 19.04 (also tried 
Ubuntu 18.04 and Linux mint 19.04)
  ;
   ALL installs failed.  Cannot boot and/or upon booting (Linux Mint 19.04), it 
will hanged hard.

  
  I am a newbie in Linux, please offer help.
  I am using a HP G60 (old laptop) w/ a Nvidia GF8200M G graphics chip.

  Also tried download the specific driver from nVidia's web site, file:
  340.1070 and 340.1060; and installed them, ALL not working and system
  hung.  Using the X-org driver is fine, but no 3D acceleration.

  Any idea??  Please help.

  
  Andrew Cheng - x Windows system engineer.

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

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

[Kernel-packages] [Bug 1838434] Re: linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+

[Khaled El Mously]

Sorry to hear that @Georgi

It's a strange problem to have. That kernel worked fine in all our pre-
release testing. Certainly _booting_ shouldn't be a problem.

Could there be some other root-cause for this problem? (e.g. filesystem
corruption or bad install or changes in /etc/fstab or new hardware
added/removed, etc.)

Are you able to boot the prior kernel again without issues?

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

Title:
  linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on
  Raspberry Pi 3 B+

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I was happily running my Raspberry Pi 3 B+ with linux-
  image-5.0.0-1012-raspi2, then upgraded to linux-
  image-5.0.0-1013-raspi2 and now my system does not boot with the last
  message as:

  ---[ end kernel panic - not syncing: Attempted to kill init! exitcode
  0x0100 ]

  Lots of other errors on the screen, but I am having a hard time
  getting a netconsole or anything to dump these errors somewhere
  readable. All I can do is attach a screenshot, and maybe type up a few
  of them.

  Reverting to 5.0.0-1012 is ok.

  /init: line 263: log_end_msg: not found
  /init: line 265: maybe_break: not found
  /init: line 266: log_begin_msg: not found
  (skip more of this)
  /init: line 299: log_end_msg: not foudn
  mount: mounting /run on /root/run failed: No such file or directory
  run-init: current directory on the same filesystem as the root: error 0
  Target filesystem doesn't have requested /sbin/init
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  (repeat last line three more times)
  /init: line 323: panic: not found
  /init: line 325: maybe_break: not found
  mount: mounting /sys on /root/sys failed: No such file or directory
  mount: mounting /proc on /root/proc failed: No such file or directory
  /init: line 359: can't open /root/dev/console: no such file
  [  36.246460] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [  36.256383] CPU: 0 PID: 1 Comm: init Tainted: G   B 
5.0.0-1013-raspi2 #13-Ubuntu
  [  36.262133] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (D)T
  [  36.278383] Call trace:
  (skip the rest)

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

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

[Kernel-packages] [Bug 1831945] Re: HDMI/DP audio: ELD not updated on hotplug event

[Launchpad Bug Tracker]

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

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

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

Title:
  HDMI/DP audio: ELD not updated on hotplug event

Status in linux package in Ubuntu:
  Expired

Bug description:
  When using HDMI or Displayport audio, the EDID-like Data (ELD) fails
  to update properly when hotplugging or hot-unplugging displays. This
  in turn prevents tools like the GNOME sound settings control panel
  from accurately presenting the system's current audio capabilities.

  
  How reproducible:

  Hot plug and hot unplug an audio-capable display and observe the state
  of the ELDs, either by directly reading the ELD files in
  /proc/asound/card*/eld* or by examining the available audio output
  devices in the GNOME sound settings control panel.

  
  Steps to Reproduce:
  1. Log into a desktop session with no audio-capable displays plugged in
  2. Plug in an audio-capable display
  3. Open the GNOME sound settings control panel

  
  Actual results:

  The audio-capable display is not selectable as an output device.

  
  Expected results:

  The audio-capable display should be selectable as an output device.

  
  Additional info:

  This bug has been fixed upstream with commit
  37a3a98ef601f89100e3bb657fb0e190b857028c. Applying this change alone
  to the bionic 4.18 HWE kernel is sufficient to allow the expected
  behavior to occur. It is likely to be sufficient to fix the same bug,
  assuming it exists, in Cosmic, but neither the presence of the bug nor
  the sufficiency of the patch were tested. The bug is likely not
  present in Disco, but this was not tested.

  This behavior was observed on a system with an NVIDIA GPU running the
  NVIDIA proprietary driver. The particular NVIDIA GPU on the system is
  not currently compatible with Nouveau. It is possible and likely that
  this problem is also reproducible on other systems which do have GPUs
  that are compatible with Nouveau, and even on systems with HDMI or
  Displayport connectors being driven by non-NVIDIA GPUs.

  When the ELD fails to update in response to a hotplug event, an update
  can be forced by accessing the underlying ALSA codec directly. For
  example, playing an audio stream directly via ALSA or even just
  reading from the /proc/asound/cardX/codec#Y file will cause the ELD to
  become updated. This is of course unnecessary if the patch which fixes
  the issue is applied, but it does offer a somewhat simple workaround
  for affected users until the patch can be backported.

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

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

[Kernel-packages] [Bug 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64, arm64

[Po-Hsu Lin]

Hi,
4.18 will reach EOL soon, the HWE stack will move to 5.0 kernel. I will add 
support to this instead.

https://ubuntu.com/about/release-cycle

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64,arm64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
  for arch aarch64(arm64)?

  Related kernel config options:

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

  Cheers,
  Paweł Jarosz

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

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

[Kernel-packages] [Bug 1811819] Re: please include the kernel module VXLAN

[Po-Hsu Lin]

Hello,
can you give the kernel in comment #1 a try?
Thanks

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

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

Title:
  please include the kernel module VXLAN

Status in linux-kvm package in Ubuntu:
  Incomplete
Status in linux-kvm source package in Xenial:
  New

Bug description:
  The kernel built with this packages does have VXLAN compiled.
  It would be nice if this could be fixed since VXLAN is used by Flannel and 
maybe other CNI plugins for Kubernetes.

  $ grep -i vxlan /boot/config-4.4.0-1039-kvm
  # CONFIG_VXLAN is not set

  When running a kubernetes cluster with Flannel with this image:

  $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system 
--kubeconfig=case1-admin.conf 
  I0116 11:35:34.176962   1 main.go:475] Determining IP address of default 
interface
  I0116 11:35:34.177231   1 main.go:488] Using interface with name ens3 and 
address 10.32.192.14
  I0116 11:35:34.177259   1 main.go:505] Defaulting external address to 
interface address (10.32.192.14)
  I0116 11:35:34.191358   1 kube.go:131] Waiting 10m0s for node controller 
to sync
  I0116 11:35:34.273844   1 kube.go:294] Starting kube subnet manager
  I0116 11:35:35.274075   1 kube.go:138] Node controller sync successful
  I0116 11:35:35.274106   1 main.go:235] Created subnet manager: Kubernetes 
Subnet Manager - node-1-case1
  I0116 11:35:35.274113   1 main.go:238] Installing signal handlers
  I0116 11:35:35.274233   1 main.go:353] Found network config - Backend 
type: vxlan
  I0116 11:35:35.274292   1 vxlan.go:120] VXLAN config: VNI=1 Port=0 
GBP=false DirectRouting=false
  E0116 11:35:35.275803   1 main.go:280] Error registering network: 
operation not supported
  I0116 11:35:35.275860   1 main.go:333] Stopping shutdownHandler...

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[AaronMa]

With this regression, Ubuntu can not be installed in OEM image which is using 
current 4.15-56 kernel.
So set it as critical.

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

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

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Status: New => In Progress

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  SRU justication:
  =
  [Impact]
  Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
  based chroot with the current bionic-proposed kernel (4.15.0-56-generic
  #62-Ubuntu).

  [Fix]
  Fix protential NULL in overlay fs.

  [Test]
  Verified on fs test and dpkg installation on overlayfs.

  [Regression Potential]
  Low, remove regression of previous bionic kernel.

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

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

[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]

[Gray]

~ > sudo lspci -s 03:00 -
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe 
Wireless Network Adapter (rev ff)
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
...
ff0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

---
Just that, ff everywhere.

Kernel: 5.0.0-23

Also, I tried the alternative driver on Larry's github, it works, that
is I have connectivity at least but it has some weird issues with
bettercap and the monitor mode.

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

Title:
  No wireless support for Realtek RTL8192EE [10ec:818b]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Utopic:
  Fix Released

Bug description:
  Open this bug to trace device driver RTL8192EE.

  We have seen this wireless card on some laptops, id is [10ec:818b],
  driver is RTL8192EE.

  This bug is only for the initial support of this WiFi adapter, it's
  not working 100% well yet, please report new "not working bug" or
  contact upstream but not keep posting comments, thanks.

  
  Status:

  pull-request for trusty was NAKed because next minor Trusty release
  will use Utopic LTS kernel, which had already fixed this issue.

  please wait it or upgrade your whole distro to Utopic.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [i915] display flickering in perpetual loop while starting ubuntu
  18.04.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  gnome 3.28.2

  Laptop needs to be re-started

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug  5 14:04:47 2019
  DistUpgraded: 2019-03-08 20:01:34,757 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
  InstallationDate: Installed on 2018-02-07 (544 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=74d5e8df-abd0-45c0-a0c6-ca60e2f84b67 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-09 (149 days ago)
  dmi.bios.date: 08/12/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3649
  dmi.board.vendor: Flextronics
  dmi.board.version: 41.3A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Flextronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.01:bd08/12/2009:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr03A01024001011012:rvnFlextronics:rn3649:rvr41.3A:cvnFlextronics:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dm3 Notebook PC
  dmi.product.version: 03A01024001011012
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Mar  8 17:47:08 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Bin Li]

Cool, we also met this issue.

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  SRU justication:
  =
  [Impact]
  Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
  based chroot with the current bionic-proposed kernel (4.15.0-56-generic
  #62-Ubuntu).

  [Fix]
  Fix protential NULL in overlay fs.

  [Test]
  Verified on fs test and dpkg installation on overlayfs.

  [Regression Potential]
  Low, remove regression of previous bionic kernel.

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

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

[Kernel-packages] [Bug 1839024] Re: display flickering in perpetual loop while starting ubuntu 18.04.2

[Daniel van Vugt]

If possible, please also take a video of the problem with a phone and
then attach the video here.

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

** Summary changed:

- display flickering in perpetual loop while starting ubuntu 18.04.2
+ [i915] display flickering in perpetual loop while starting ubuntu 18.04.2

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

Title:
  [i915] display flickering in perpetual loop while starting ubuntu
  18.04.2

Status in linux package in Ubuntu:
  New

Bug description:
  gnome 3.28.2

  Laptop needs to be re-started

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug  5 14:04:47 2019
  DistUpgraded: 2019-03-08 20:01:34,757 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
  InstallationDate: Installed on 2018-02-07 (544 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=74d5e8df-abd0-45c0-a0c6-ca60e2f84b67 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-09 (149 days ago)
  dmi.bios.date: 08/12/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3649
  dmi.board.vendor: Flextronics
  dmi.board.version: 41.3A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Flextronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.01:bd08/12/2009:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr03A01024001011012:rvnFlextronics:rn3649:rvr41.3A:cvnFlextronics:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dm3 Notebook PC
  dmi.product.version: 03A01024001011012
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Fri Mar  8 17:47:08 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Kernel-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself

[Daniel van Vugt]

** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- Mouse cursor left frozen copy of itself
+ [nvidia] Mouse cursor left frozen copy of itself

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [nvidia] Mouse cursor left frozen copy of itself

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1839008] Re: Extra mouse cursor fixed on screen

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1827428, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Extra mouse cursor fixed on screen
+ [nvidia] Extra mouse cursor fixed on screen

** Tags added: nvidia

** This bug has been marked a duplicate of bug 1827428
   Mouse cursor left frozen copy of itself

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

Title:
  [nvidia] Extra mouse cursor fixed on screen

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Inevitably the mouse cursor will become fixated on screen at the
  position it was when the screen was unlocked. When I switch TTY and
  come back the lock screen will change and I'll be able to move the
  fixed mouse cursor to a new location. Only fix is to restart the
  computer and the bug is guaranteed to recur. I am able to move the
  active cursor around the screen but there is a persistent one that I
  am unable to interact with.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 12:30:38 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2229]
  InstallationDate: Installed on 2019-08-02 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20DQ001LUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=51d296e6-a200-427d-8e49-36f04f92967a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N19ET57W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DQ001LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN19ET57W(1.30):bd05/31/2018:svnLENOVO:pn20DQ001LUS:pvrThinkPadS5Yoga15:rvnLENOVO:rn20DQ001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S5 Yoga 15
  dmi.product.name: 20DQ001LUS
  dmi.product.sku: LENOVO_MT_20DQ_BU_Think_FM_ThinkPad S5 Yoga 15
  dmi.product.version: ThinkPad S5 Yoga 15
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Aug  4 18:49:18 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.4-1ubuntu3

To manage notifications 

[Kernel-packages] [Bug 1839024] [NEW] display flickering in perpetual loop while starting ubuntu 18.04.2

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

gnome 3.28.2

Laptop needs to be re-started

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Aug  5 14:04:47 2019
DistUpgraded: 2019-03-08 20:01:34,757 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
   Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3649]
InstallationDate: Installed on 2018-02-07 (544 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=74d5e8df-abd0-45c0-a0c6-ca60e2f84b67 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-03-09 (149 days ago)
dmi.bios.date: 08/12/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3649
dmi.board.vendor: Flextronics
dmi.board.version: 41.3A
dmi.chassis.type: 10
dmi.chassis.vendor: Flextronics
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.01:bd08/12/2009:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr03A01024001011012:rvnFlextronics:rn3649:rvr41.3A:cvnFlextronics:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dm3 Notebook PC
dmi.product.version: 03A01024001011012
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Fri Mar  8 17:47:08 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
display flickering in perpetual loop while starting ubuntu 18.04.2
https://bugs.launchpad.net/bugs/1839024
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 1838848] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Bluetooth controller not detected after resume from suspend [Qualcomm
  Atheros AR9285 Malbec Bluetooth Adapter]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's very familiar to Bug #1788807.
  I'm on 19.04.

  How can I help to solve it?

  1) $lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04

  2) $ apt-cache policy bluez
  bluez:
Установлен: 5.50-0ubuntu2
Кандидат:   5.50-0ubuntu2
Таблица версий:
   *** 5.50-0ubuntu2 500
  500 http://ru.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expectations: work as designed - no issues.
  4) after resume from suspended state device is no longer available
  - if open gnome (UI) bluetooth manager in journal: 
  03 16:35:50 PC-Name tracker-miner-f[1357]: Could not process 
'file:///home/user/%23534117': Error when getting information for file 
“/home/user/#534117”: Нет такого файла или каталога* 

  *translation from russian: File or path does not exist

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network 
Adapter [168c:0032] (rev 01)
Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter 
[103c:1785]
Kernel driver in use: ath9k
Kernel modules: ath9k
  02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE 
PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller [103c:3566]
Kernel driver in use: r8169
Kernel modules: r8169
  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI 
Express Card Reader [10ec:5209] (rev 01)
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 003: ID 05c8:021e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  5.0.0-23-generic
  [0.177448] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [0.198830] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  
[bus 00-3f] only partially covers this bridge
  [3.257474] [Firmware Bug]: Invalid critical threshold (0)
  [4.140519] usb 6-1: Product: Bluetooth USB Host Controller
  [6.610450] Bluetooth: Core ver 2.22
  [6.610478] Bluetooth: HCI device and connection manager initialized
  [6.610485] Bluetooth: HCI socket layer initialized
  [6.610488] Bluetooth: L2CAP socket layer initialized
  [6.610494] Bluetooth: SCO socket layer initialized
  [   16.795026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.795029] Bluetooth: BNEP filters: protocol multicast
  [   16.795036] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  3 16:19:13 2019
  InstallationDate: Installed on 2019-08-03 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: bnep btusb bluetooth
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=670d7b88-4792-45a0-a2d1-b026d4926c27 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.53
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3566
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.3A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 

[Kernel-packages] [Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 30. July 2019 22:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 30. July 2019 22:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837572] Re: disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Signoff
- phase-changed: Thursday, 01. August 2019 19:52 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 06. August 2019 01:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 01:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1838848] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485]

[Daniel van Vugt]

Thanks, apparently idProduct=311d means:

  Atheros AR9285 Malbec Bluetooth Adapter

So if it is on the same board as the AR9485, it's at least a different
chip.

** Summary changed:

- Bluetooth device not detected after resume from suspend [Qualcomm Atheros 
AR9485]
+ Bluetooth device not detected after resume from suspend [Qualcomm Atheros 
AR9285 Malbec Bluetooth Adapter]

** Summary changed:

- Bluetooth device not detected after resume from suspend [Qualcomm Atheros 
AR9285 Malbec Bluetooth Adapter]
+ Bluetooth controller not detected after resume from suspend [Qualcomm Atheros 
AR9285 Malbec Bluetooth Adapter]

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

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

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

Title:
  Bluetooth controller not detected after resume from suspend [Qualcomm
  Atheros AR9285 Malbec Bluetooth Adapter]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It's very familiar to Bug #1788807.
  I'm on 19.04.

  How can I help to solve it?

  1) $lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04

  2) $ apt-cache policy bluez
  bluez:
Установлен: 5.50-0ubuntu2
Кандидат:   5.50-0ubuntu2
Таблица версий:
   *** 5.50-0ubuntu2 500
  500 http://ru.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expectations: work as designed - no issues.
  4) after resume from suspended state device is no longer available
  - if open gnome (UI) bluetooth manager in journal: 
  03 16:35:50 PC-Name tracker-miner-f[1357]: Could not process 
'file:///home/user/%23534117': Error when getting information for file 
“/home/user/#534117”: Нет такого файла или каталога* 

  *translation from russian: File or path does not exist

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network 
Adapter [168c:0032] (rev 01)
Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter 
[103c:1785]
Kernel driver in use: ath9k
Kernel modules: ath9k
  02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE 
PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller [103c:3566]
Kernel driver in use: r8169
Kernel modules: r8169
  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI 
Express Card Reader [10ec:5209] (rev 01)
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 003: ID 05c8:021e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  5.0.0-23-generic
  [0.177448] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [0.198830] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  
[bus 00-3f] only partially covers this bridge
  [3.257474] [Firmware Bug]: Invalid critical threshold (0)
  [4.140519] usb 6-1: Product: Bluetooth USB Host Controller
  [6.610450] Bluetooth: Core ver 2.22
  [6.610478] Bluetooth: HCI device and connection manager initialized
  [6.610485] Bluetooth: HCI socket layer initialized
  [6.610488] Bluetooth: L2CAP socket layer initialized
  [6.610494] Bluetooth: SCO socket layer initialized
  [   16.795026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.795029] Bluetooth: BNEP filters: protocol multicast
  [   16.795036] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  3 16:19:13 2019
  InstallationDate: Installed on 2019-08-03 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: bnep btusb bluetooth
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=670d7b88-4792-45a0-a2d1-b026d4926c27 ro 

[Kernel-packages] [Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

[Steve Beattie]

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

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

Title:
  disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 30. July 2019 22:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837572] Re: disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

[Steve Beattie]

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

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

Title:
  disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 01:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1838959] Re: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

[Daniel van Vugt]

Your system is still using the unsupported 'oibaf' PPA:

version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b

Please try using 'ppa-purge' to remove it from your machine and then
reboot.

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

Title:
  [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in
  use 0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  3rd party PPA Mesaremoved, and problem stil persist in dmesg:
  [   52.313240] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen 
encoder in use 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.2.0-050200-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 12:20:11 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] 
[1002:9495] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP 
[1002:0028]
  InstallationDate: Installed on 2018-12-22 (225 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash 
resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.71
  dmi.board.name: ConRoe865PE
  dmi.board.version: 3.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
  dmi.product.name: ConRoe865PE
  dmi.product.version: 3.00
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.0.1+git1907231930.c7ed12~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1907241930.6f4972~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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

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

[Kernel-packages] [Bug 1838443] Re: No flicker free boot since Ignoring BGRT: invalid version 0 (expected 1)

[Daniel van Vugt]

It's not up to me... You'll need to seek guidance and a code review from
kernel developers.

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

Title:
  No flicker free boot since Ignoring BGRT: invalid version 0 (expected
  1)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On eoan dev here:

  Flicker free booting doesn't work since I get:
  Ignoring BGRT: invalid version 0 (expected 1)
  on dmesg on my Thinkpad x230t i7-3520M (Ivy Bridge).

  Second, if I add:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.fastboot=1"
  to /etc/default/grub then it doesn't show plymouth but displays the text 
Ubuntu loading screen and I need to press ALT+F1 so GDM will show up (see 
video: [1]). If I press escape while it is displaying text Ubuntu loading, it 
loads plymouth (see video: [2]) and shows the spinner (no lenovo word) and I 
don't need to press ALT+F1 since GDM shows after plymouth. So I guess there's a 
bug there, since it should display plymouth and not the Ubuntu loading text and 
boot directly to GDM.

  Now if I patch the kernel:
  diff --git a/drivers/firmware/efi/efi-bgrt.c b/drivers/firmware/efi/efi-bgrt.c
  index b07c17643210..5754e530af9a 100644
  --- a/drivers/firmware/efi/efi-bgrt.c
  +++ b/drivers/firmware/efi/efi-bgrt.c
  @@ -42,7 +42,7 @@ void __init efi_bgrt_init(struct acpi_table_header *table)
  return;
  }
  *bgrt = *(struct acpi_table_bgrt *)table;
  -   if (bgrt->version != 1) {
  +   if (bgrt->version != 1 && false) { /* don't check BGRT version */
  pr_notice("Ignoring BGRT: invalid version %u (expected 1)\n",
     bgrt->version);
  goto out;

  And linux-modules and linux-modules-extra is not installed in that
  kernel, then I have somewhat flicker free boot.  It shows the bgrt
  screen then goes black (probably grub loading), then shows the bgrt
  screen again with the spinner.  Nice! (see video: [3])

  So, I guess my Thinkpad is not setting bgrt version properly.  So can
  we have a kernel parameter to disable checking of bgrt version?

  Then again, if I install linux-modules and linux-modules-extra then I
  get the Ubuntu loading text when booting, but if I press esc I get the
  bgrt screen with spinner.  I think it's it's a bug somewhere in the
  linux-modules package.

  [1] https://youtu.be/tAgRf2c7J4A
  [2] https://youtu.be/1ystyzLhSaw
  [3] https://youtu.be/8AAkUDO2Kt8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic (not installed)
  ProcVersionSignature: Ubuntu 5.2.0-8.9+test1-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp13358 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 30 23:49:49 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (1401 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (4 days ago)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB4WW(2.74):bd06/11/2019:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1838959] Re: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

[Daniel van Vugt]

Your system is still using the unsupported 'oidbaf' PPA:

version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b

Please try using 'ppa-purge' to remove it from your machine and then
reboot.

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

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

Title:
  [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in
  use 0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  3rd party PPA Mesaremoved, and problem stil persist in dmesg:
  [   52.313240] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen 
encoder in use 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.2.0-050200-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 12:20:11 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] 
[1002:9495] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP 
[1002:0028]
  InstallationDate: Installed on 2018-12-22 (225 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash 
resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.71
  dmi.board.name: ConRoe865PE
  dmi.board.version: 3.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
  dmi.product.name: ConRoe865PE
  dmi.product.version: 3.00
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.0.1+git1907231930.c7ed12~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1907241930.6f4972~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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

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

[Kernel-packages] [Bug 1838945] Re: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1838959
   [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

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

Title:
  [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in
  use 0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  How to solve this dmesg:
  [   50.990513] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen 
encoder in use 0

  I use dual port(DVI/HDMI) AGP Radeon HD4650 with DVI port connected to
  LCD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.2.0-050200-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 09:59:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] 
[1002:9495] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP 
[1002:0028]
  InstallationDate: Installed on 2018-12-22 (225 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash 
resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.71
  dmi.board.name: ConRoe865PE
  dmi.board.version: 3.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
  dmi.product.name: ConRoe865PE
  dmi.product.version: 3.00
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.0.1+git1907231930.c7ed12~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1907241930.6f4972~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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

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

[Kernel-packages] [Bug 1838959] [NEW] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

3rd party PPA Mesaremoved, and problem stil persist in dmesg:
[   52.313240] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen 
encoder in use 0

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.2.0-050200-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  5 12:20:11 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] 
[1002:9495] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP 
[1002:0028]
InstallationDate: Installed on 2018-12-22 (225 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash 
resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: L1.71
dmi.board.name: ConRoe865PE
dmi.board.version: 3.00
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
dmi.product.name: ConRoe865PE
dmi.product.version: 3.00
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.0.1+git1907231930.c7ed12~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1907241930.6f4972~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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


** Tags: amd64 apport-bug bionic problem radeon third-party-packages ubuntu
-- 
[drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
https://bugs.launchpad.net/bugs/1838959
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 1798921] Re: sky2 ethernet card don't work after returning from suspension

[ricardovitor]

I'm new to the community, I wanted some guidance on how to report this
bug. I have a Samsung RV510 Notebook, which uses this "sky 2" Driver to
manage the Notebook's Lan network interface. Upon returning from sleep,
the Lan interface stops working and only works when you completely
restart the Notebook. I've read some comments here in the topic,
including that the bugs were fixed in some kernel versions, but for me
the version: 4.15.0-55.57 and 4.18.0-25.26 still have the same bug. I
did some tests on other distros not based on Ubuntu and using newer
Kernel, the problem also happens, very strange this problem. An interim
solution I found in this topic was the "quiet splash pci = nomsi, noaer"
which I believe has temporarily solved the problem. I appreciate the
community response.

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

Title:
  sky2 ethernet card don't work after returning from suspension

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

Bug description:
  [SRU justification]

  == Impact ==
  Ethernet connection using a SKY2 card stops working after suspend.

  == Fix ==
  A fix for this landed in v5.0 upstream and was picked up in Xenial via 
upstream stable but not yet in Bionic and Cosmic. The change simply increases a 
timeout.

  == Testcase ==
  Suspend/resume with affected hardware present.

  == Risk of Regression ==
  Very low as only changing a timeout value in a specific hardware driver.

  ---

  Bug very similar to #1752772
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but
  affecting the sky2 driver instead of r8169.

  After system suspend the ethernet connection stops working. The card
  is still up and the modem can see it is connected, but the card
  doesn't get an ip address. Ifconfig down/up and restarting network-
  manager does not solve the issue. Similarly to the other bug, "sudo
  modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue.

  Relevant: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107
  

  Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
  x86_64 x86_64 x86_64 GNU/Linux

    *-network
     description: Ethernet interface
     product: 88E8040 PCI-E Fast Ethernet Controller
     vendor: Marvell Technology Group Ltd.
     physical id: 0
     bus info: pci@:09:00.0
     logical name: enp9s0
     version: 13
     serial:
     size: 100Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=sky2 
driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted 
pair speed=100Mbit/s
     resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256)

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

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

[Kernel-packages] [Bug 1810215] Re: Smart data works on kernel 4.13 but not on 4.15

[Nathan Stratton Treadway]

@Mike/Robie:

Actually the "uas: Always apply US_FL_NO_ATA_1X quirk to Seagate
devices" patch to the kernel is (part of) the cause of the current
smartmontool failure rather than a fix for it.

The underlying problem is that most Seagate drive enclosures do not
properly handle SAT (= "ATA pass-through") when in UAS mode, and so the
kernel now (after that patch) disables SAT for all Seagate enclosures
when UAS is in use.

That change allows those enclosures to work okay in UAS mode for normal
data access (with the associated increase in performance) ... but since
Smartmontools and other utilities (e.g. "hdparm") require SAT to work,
the change breaks their functionality for those devices.

The current workaround is to use the kernel quirks to disable UAS for a
particular device, so that the kernel falls back to the old usb-storage
mode instead; this lets SAT work again (and thus Smartmontools, etc.
function properly), but only at the expense of losing UAS performance
for normal data access.

So in the long run it would be ideal for the kernel to have some way to
more dynamically deal with these sorts of buggy devices (i.e. switching
modes temporarily to allow SAT to work for special operations such as
Smartmontools but use UAT most of the time)... but I haven't run across
any discussion about such a patch anywhere, so it seems like people with
these devices will be stuck with having to choose between SAT or UAS for
the time being.

Anyway, there's now a Smartmontools Wiki page devoted to this specific
topic:  https://www.smartmontools.org/wiki/SAT-with-UAS-Linux .

** Summary changed:

- Smart data works on kernel 4.13 but not on 4.15
+ for Seagate USB drive enclosures, SAT (e.g. smartmontools)  works on kernel 
4.13 but not on 4.15

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

Title:
  for Seagate USB drive enclosures, SAT (e.g. smartmontools)  works on
  kernel 4.13 but not on 4.15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15.

  Here is data from 16.04
  root@server:~# uname -a
  Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  root@server:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial
  root@server:~# smartctl -d sat -i /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Device Model: ST8000DM004-2CX188
  Serial Number:ZCT07YN6
  LU WWN Device Id: 5 000c50 0b1f2a4d2
  Firmware Version: 0001
  User Capacity:8,001,563,222,016 bytes [8.00 TB]
  Sector Sizes: 512 bytes logical, 4096 bytes physical
  Rotation Rate:5425 rpm
  Form Factor:  3.5 inches
  Device is:Not in smartctl database [for details use: -P showall]
  ATA Version is:   ACS-3 T13/2161-D revision 5
  SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
  Local Time is:Tue Jan  1 16:57:48 2019 EST
  SMART support is: Available - device has SMART capability.
  SMART support is: Enabled

  root@server:~#

  here is data from 18.04:root@mike-desktop:/tmp# uname -a
  Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  root@mike-desktop:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic
  root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd
  smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  Read Device Identity failed: scsi error unsupported field in scsi
  command

  A mandatory SMART command failed: exiting. To continue, add one or
  more '-T permissive' options.

  dmesg on 18.04 showing drive is connected /dev/sdd:
  [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd
  [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, 
idProduct=331a
  [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [6041018.009428] usb 3-2.4: Product: Expansion Desk
  [6041018.009432] usb 3-2.4: Manufacturer: Seagate
  [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG
  [6041018.015808] scsi host5: uas
  [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate  Expansion Desk   
0915 PQ: 0 ANSI: 6
  [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0
  [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 
TB/7.28 TiB)
  [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks
  [6041030.357265] sd 

[Kernel-packages] [Bug 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

[Steve Beattie]

Okay, the reason this test (and bug 1717856) fail sporadically is that
ASLR in precise for i386 has very low number of random values for vdso
and shared library offsets, when ulimits are set such that unlimited
stack sizes are allowed:

  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ uname -a
  Linux sec-precise-i386 3.2.0-142-generic #189-Ubuntu SMP Fri Jul 5 18:40:43 
UTC 2019 i686 i686 i386 GNU/Linux
  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ ulimit -s unlimited
  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ ulimit -s
  unlimited
  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ for ((i=0; i<1; 
i++)) ; do ./kernel-security/aslr/aslr --report vdso ; done | sort | uniq -c
 1273 0x4000
 8662 0x40022000
   65 0x40026000

Yes, all of 3 values, and 86% of the invocations result in one value.
The shared library base values are slightly better, but not much:

  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ for ((i=0; i<1; 
i++)) ; do ./kernel-security/aslr/aslr --report libs ; done | sort | uniq -c
  499 0x40003d80
  285 0x40016d80
  566 0x40025d80
 7608 0x40038d80
  295 0x4003cd80
  250 0x4003dd80
  167 0x4003ed80
  153 0x4003fd80
  177 0x40040d80

Compare this with the 3.13 results:

  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ uname -a
  Linux sec-trusty-i386 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:41:17 
UTC 2019 i686 i686 i686 GNU/Linux
  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ ulimit -s unlimited
  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ ulimit -s
  unlimited
  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ for ((i=0; i<1; 
i++)) ; do ./kernel-security/aslr/aslr --report vdso ; done | sort | uniq -c | 
wc -l
  256

(output is piped into wc -l, because there are 256 distinct results.) So
8 bits of randomisation, which is not great, but better than >2.

The tests were added in response to http://hmarco.org/bugs/CVE-2016-3672
-Unlimiting-the-stack-not-longer-disables-ASLR.html and fixes were
applied for the 3.2.0-104.145 kernel.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-3672

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

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

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

Bug description:
  This issue can be reproduced in 3.2.0-133 in proposed and 3.2.0-131.
  So it should not be considered as a regression.

  We didn't spot this issue before, until I'm testing 3.2 kernel on one
  of the laptop (CID 201307-13930) in Cert lab instead of using our
  regular regression-testing test pool from kernel team this cycle.

    ==
    FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
    ASLR of vdso
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
    self._test_aslr('vdso', expected)
  File "./test-kernel-security.py", line 1795, in _test_aslr
    self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1772, in _test_aslr_all
    self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1765, in _test_aslr_exec
    self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
    self.assertEqual(expected, rc, msg + result + report)
    AssertionError: unlimited stack vdso native:
    Got exit code 1, expected 0
    Command: './aslr', 'vdso', '--verbose'
    Output:
    Checking ASLR of vdso:
     0x40022000
     0x40022000
     0x40022000
    FAIL: ASLR not functional (vdso always at 0x40022000)

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

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

[Kernel-packages] [Bug 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

[Steve Beattie]

That said, at this point, I don't believe we are likely to fix this for
3.2 kernels, so adjusting the QRT test may be in order.

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

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

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

Bug description:
  This issue can be reproduced in 3.2.0-133 in proposed and 3.2.0-131.
  So it should not be considered as a regression.

  We didn't spot this issue before, until I'm testing 3.2 kernel on one
  of the laptop (CID 201307-13930) in Cert lab instead of using our
  regular regression-testing test pool from kernel team this cycle.

    ==
    FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
    ASLR of vdso
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
    self._test_aslr('vdso', expected)
  File "./test-kernel-security.py", line 1795, in _test_aslr
    self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1772, in _test_aslr_all
    self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1765, in _test_aslr_exec
    self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
    self.assertEqual(expected, rc, msg + result + report)
    AssertionError: unlimited stack vdso native:
    Got exit code 1, expected 0
    Command: './aslr', 'vdso', '--verbose'
    Output:
    Checking ASLR of vdso:
     0x40022000
     0x40022000
     0x40022000
    FAIL: ASLR not functional (vdso always at 0x40022000)

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

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

Re: [Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures

[Ryan Harper]

On Mon, Aug 5, 2019 at 1:19 PM Ryan Harper 
wrote:

>
>
> On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi 
> wrote:
>
>> Ryan, I've uploaded a new test kernel with the fix mentioned in the
>> comment before:
>>
>> https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/
>>
>> I've performed over 100 installations using curtin-nvme.sh
>> (install_count = 100), no hung task timeout. I'll run other stress tests
>> to make sure we're not breaking anything else with this fix, but results
>> look promising so far.
>>
>> It'd be great if you could also do a test on your side. Thanks!
>>
>
> Thats excellent news.  I'm starting my tests on this kernel now.
>

I've got 233 consecutive installs successful.


>
>
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1796292
>>
>> Title:
>>   Tight timeout for bcache removal causes spurious failures
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
>>
>

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

Title:
  Tight timeout for bcache removal causes spurious failures

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

Bug description:
  I've had a number of deployment faults where curtin would report
  Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
  deployment of 30+ nodes. Upon retrying the node would usually deploy
  fine. Experimentally I've set the timeout ridiculously high, and it
  seems I'm getting no faults with this. I'm wondering if the timeout
  for removal is set too tight, or might need to be made configurable.

  --- curtin/util.py~ 2018-05-18 18:40:48.0 +
  +++ curtin/util.py  2018-10-05 09:40:06.807390367 +
  @@ -263,7 +263,7 @@
   return _subp(*args, **kwargs)
   
   
  -def wait_for_removal(path, retries=[1, 3, 5, 7]):
  +def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
   if not path:
   raise ValueError('wait_for_removal: missing path parameter')

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

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

[Kernel-packages] [Bug 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375

[Agustin-ferrario]

Hi! Sorry for the delay. I installed the packages in ubuntu 19.04
(Disco):

$ ls
linux-headers-5.3.0-050300rc1_5.3.0-050300rc1.201907212232_all.deb
linux-image-unsigned-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
linux-headers-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
linux-modules-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
crash@crash-Inspiron-7375:~/Downloads$ sudo dpkg -i linux-*

Then rebooted but with the same error. I will try to manually compile
and install the kernel with the sources listed there without the patches
and will confirm.

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

Title:
  Ubuntu won't boot on Dell Inspiron 7375

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, 
with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 
(videos of each unsuccessful boot will be attached).
  I was able to boot using a workaround, by adding to the kernel line:

  amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

  You can see it here:
  https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on-
  dell-inspiron-7375

  I used this workaround to run the apport-bug tool.

  The problem should be in an ubuntu specific vendor patch or configuration 
since I was able to boot successfully in:
  * CentOS 7 (kernel 3.10)
  * OpenSUSE Leap 15.1 (kernel 4.12.14)
  * OpenSUSE tumbleweed (kernel 5.1.16)
  * Fedora 30 (kernel 5.0.9)
  * Manjaro (kernel 4.19)
  * SystemRescueCd (kernel 4.19.34)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2186 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2186 F pulseaudio
  CasperVersion: 1.411
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 23 21:14:36 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  MachineType: Dell Inc. Inspiron 7375
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=00:00.2 ---
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-20-generic N/A
   linux-backports-modules-5.0.0-20-generic  N/A
   linux-firmware1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0GTNWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.5.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7375
  dmi.product.sku: 0884
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1837571] Re: disco/linux-gcp: 5.0.0-1012.12 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1837569 (bionic/linux-gke-5.0), bug 1837570 (bionic
  /linux-gcp-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1837570
bionic/linux-gke-5.0: bug 1837569
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1012.12 -proposed tracker

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

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

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

  backports: bug 1837569 (bionic/linux-gke-5.0), bug 1837570 (bionic
  /linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1837570
bionic/linux-gke-5.0: bug 1837569
  variant: debs

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

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

[Kernel-packages] [Bug 1837571] Re: disco/linux-gcp: 5.0.0-1012.12 -proposed tracker

[Steve Beattie]

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

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

Title:
  disco/linux-gcp: 5.0.0-1012.12 -proposed tracker

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

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

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

  backports: bug 1837569 (bionic/linux-gke-5.0), bug 1837570 (bionic
  /linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1837570
bionic/linux-gke-5.0: bug 1837569
  variant: debs

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1839037

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1839037

Title:
  Stacked onexec transitions fail when under NO NEW PRIVS restrictions

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

Bug description:
  running the apparmor nnp regression tests results in the following
  failure

  Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected
  to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted'

  with a log message of

  [ 1169.863302] audit: type=1400 audit(1565046042.144:280686):
  apparmor="DENIED" operation="exec" info="no new privs" error=-1
  profile="/home/jj/apparmor.git/tests/regression/apparmor/transition"
  name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888
  comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000
  target="/home/jj/apparmor.git/tests/regression/apparmor/open"

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

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

[Kernel-packages] [Bug 1839037] [NEW] Stacked onexec transitions fail when under NO NEW PRIVS restrictions

[John Johansen]

Public bug reported:

running the apparmor nnp regression tests results in the following
failure

Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected
to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted'

with a log message of

[ 1169.863302] audit: type=1400 audit(1565046042.144:280686):
apparmor="DENIED" operation="exec" info="no new privs" error=-1
profile="/home/jj/apparmor.git/tests/regression/apparmor/transition"
name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888
comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000
target="/home/jj/apparmor.git/tests/regression/apparmor/open"

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   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/1839037

Title:
  Stacked onexec transitions fail when under NO NEW PRIVS restrictions

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New

Bug description:
  running the apparmor nnp regression tests results in the following
  failure

  Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected
  to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted'

  with a log message of

  [ 1169.863302] audit: type=1400 audit(1565046042.144:280686):
  apparmor="DENIED" operation="exec" info="no new privs" error=-1
  profile="/home/jj/apparmor.git/tests/regression/apparmor/transition"
  name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888
  comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000
  target="/home/jj/apparmor.git/tests/regression/apparmor/open"

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

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

[Kernel-packages] [Bug 1839036] Re: Bionic update: upstream stable patchset 2019-08-05

[Kamal Mostafa]

** Description changed:

  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:
  
     upstream stable patchset 2019-08-05
  
-Ported from the following upstream stable releases:
-v4.19.59,
- v4.14.134, v4.19.60,
-v4.19.61,
-v4.19.62,
- v4.14.135,
+    Ported from the following upstream stable releases:
+    v4.19.59,
+ v4.14.134, v4.19.60,
+    v4.19.61,
+    v4.19.62,
+ v4.14.135,
  
     from git://git.kernel.org/
+ 
+ e1000e: start network tx queue only when link is up
+ Input: synaptics - enable SMBUS on T480 thinkpad trackpad
+ nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header
+ drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT
+ crypto: talitos - rename alternative AEAD algos.
+ samples, bpf: fix to change the buffer size for read()
+ bpf: sockmap, fix use after free from sleep in psock backlog workqueue
+ staging:iio:ad7150: fix threshold mode config bit
+ mac80211: mesh: fix RCU warning
+ mac80211: free peer keys before vif down in mesh
+ iwlwifi: Fix double-free problems in iwl_req_fw_callback()
+ dt-bindings: can: mcp251x: add mcp25625 support
+ can: mcp251x: add support for mcp25625
+ can: m_can: implement errata "Needless activation of MRAF irq"
+ can: af_can: Fix error path of can_init()
+ ibmvnic: Refresh device multicast list after reset
+ ARM: dts: am335x phytec boards: Fix cd-gpios active level
+ Input: imx_keypad - make sure keyboard can always wake up system
+ KVM: arm/arm64: vgic: Fix kvm_device leak in vgic_its_destroy
+ mlxsw: spectrum: Disallow prio-tagged packets when PVID is removed
+ ARM: davinci: da850-evm: call regulator_has_full_constraints()
+ ARM: davinci: da8xx: specify dma_coherent_mask for lcdc
+ mac80211: only warn once on chanctx_conf being NULL
+ qmi_wwan: add support for QMAP padding in the RX path
+ qmi_wwan: avoid RCU stalls on device disconnect when in QMAP mode
+ qmi_wwan: extend permitted QMAP mux_id value range
+ md: fix for divide error in status_resync
+ bnx2x: Check if transceiver implements DDM before access
+ drm: return -EFAULT if copy_to_user() fails
+ ip6_tunnel: allow not to count pkts on tstats by passing dev as NULL
+ net: lio_core: fix potential sign-extension overflow on large shift
+ quota: fix a problem about transfer quota
+ net: dsa: mv88e6xxx: fix shift of FID bits in mv88e6185_g1_vtu_loadpurge()
+ net :sunrpc :clnt :Fix xps refcount imbalance on the error path
+ fscrypt: don't set policy for a dead directory
+ udf: Fix incorrect final NOT_ALLOCATED (hole) extent length
+ ALSA: hda/realtek - Headphone Mic can't record after S3
+ block, bfq: NULL out the bic when it's no longer valid
+ x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()
+ x86/tls: Fix possible spectre-v1 in do_get_thread_area()
+ Documentation: Add section about CPU vulnerabilities for Spectre
+ mwifiex: Abort at too short BSS descriptor element
+ mwifiex: Don't abort on small, spec-compliant vendor IEs
+ USB: serial: ftdi_sio: add ID for isodebug v1
+ USB: serial: option: add support for GosunCn ME3630 RNDIS mode
+ Revert "serial: 8250: Don't service RX FIFO if interrupts are disabled"
+ p54usb: Fix race between disconnect and firmware loading
+ usb: gadget: ether: Fix race between gether_disconnect and rx_submit
+ usb: renesas_usbhs: add a workaround for a race condition of workqueue
+ staging: comedi: dt282x: fix a null pointer deref on interrupt
+ staging: comedi: amplc_pci230: fix null pointer deref on interrupt
+ binder: fix memory leak in error path
+ carl9170: fix misuse of device driver API
+ VMCI: Fix integer overflow in VMCI handle arrays
+ MIPS: Remove superfluous check for __linux__
+ clk: ti: clkctrl: Fix returning uninitialized data
+ efi/bgrt: Drop BGRT status field reserved bits check
+ perf/core: Fix perf_sample_regs_user() mm check
+ ARM: omap2: remove incorrect __init annotation
+ be2net: fix link failure after ethtool offline test
+ ppp: mppe: Add softdep to arc4
+ sis900: fix TX completion
+ ARM: dts: imx6ul: fix PWM[1-4] interrupts
+ dm verity: use message limit for data block corruption message
+ x86/boot/64: Fix crash if kernel image crosses page table boundary
+ cpu/hotplug: Fix out-of-bounds read when setting fail state
+ linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL
+ ARC: hide unused function unw_hdr_alloc
+ s390: fix stfle zero padding
+ 

[Kernel-packages] [Bug 1795808] Re: Xorg freeze when using nvidia driver 390

[mohammad]

thank you. uncommenting "WaylandEnable=false " worked for me as well.
now I can use android studio emulator with hardware accelerator.

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

Title:
  Xorg freeze when using nvidia driver 390

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

Bug description:
  Hi,

  Since the installation of Ubuntu 18.10, I get the login screen but
  once logged in I get a black screen. It happens only with the
  proprietary nvidia driver 390. If I remove the nvidia driver to use
  nouveau, it works.

  My graphic card is: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti]

  So the automatic report in attachement will show you no nvidia driver
  installed. It's because I am doing this bug report after removing the
  nvidia driver to be able to get a desktop.

  In attachement I add the journalctl of the preview boot which failed
  with nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  3 09:19:03 2018
  DistUpgraded: 2018-10-03 00:59:01,660 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-36-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070 Ti] [1043:8620]
  InstallationDate: Installed on 2017-09-17 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-8-generic 
root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-02 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Wed Oct  3 09:03:39 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.1-3ubuntu1

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

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

[Kernel-packages] [Bug 1839036] [NEW] Bionic update: upstream stable patchset 2019-08-05

[Kamal Mostafa]

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:

   upstream stable patchset 2019-08-05

   Ported from the following upstream stable releases:
   v4.19.59,
v4.14.134, v4.19.60,
   v4.19.61,
   v4.19.62,
v4.14.135,

   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- 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:
  
- 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:
+    upstream stable patchset 2019-08-05
  
-upstream stable patchset 2019-08-05
-from git://git.kernel.org/
+Ported from the following upstream stable releases:
+v4.19.59,
+ v4.14.134, v4.19.60,
+v4.19.61,
+v4.19.62,
+ v4.14.135,
+ 
+    from git://git.kernel.org/

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Bionic update: upstream stable patchset 2019-08-05

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

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

     upstream stable patchset 2019-08-05

 Ported from the following upstream stable releases:
 v4.19.59,
  v4.14.134, v4.19.60,
 v4.19.61,
 v4.19.62,
  v4.14.135,

     from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Promote to Proposed
- phase-changed: Monday, 05. August 2019 20:31 UTC
+ phase: Ready for Testing
+ phase-changed: Monday, 05. August 2019 22:16 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Testing
  phase-changed: Monday, 05. August 2019 22:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

I'll wait for the next SRU for bionic to be in -proposed to provide
Bionic full verification just like I did to Disco. It shall not take too
long and the version currently in -proposed will be superseded by the
one we have in the merge request right now.

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in qemu source package in Bionic:
  Fix Committed
Status in libvirt source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in qemu source package in Cosmic:
  Won't Fix
Status in libvirt source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in qemu source package in Disco:
  Fix Committed
Status in libvirt source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  In Progress
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * QEMU does not support IceLake and CascadeLake CPUs specific features.
   * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR.
   * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations:
 - Rogue Data Cache Load
 - Enhanced IBRS
 - RSB Alternate
 - L1D flush need on VMENTRY
 - speculative Store Bypass
 to guests, as described in document:
 Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf

  [Test Case]

   * From Original Description:

  """
  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

  """

  [Regression Potential]

   * Most changes are related to CPU type definitions and its supported
  features. They are all based in upstream changes but, for obvious
  reasons, backporting and/or cherry-picking those could bring issues.
  Biggest concern is breaking something that currently works. Right now,
  the parts being changed that could affect other CPU types would be
  related to a small refactoring of how the features are organized, and
  that would be seen right away when trying to start a new VM after the
  package is installed.

   * Other tests, related to the features being backported, are being
  done by our KVM regression tests, including migration combinations, to
  reduce chances that a regression is introduced.

  [Other Info]
   
   * N/A

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

# Disco verification:

ubuntu@disco:~$ sudo /usr/bin/qemu-system-x86_64 -name guest="guest"
-machine accel=kvm -cpu host,+arch-capabilities,+ssbd,+md-clear,+rdctl-
no,+ibrs-all,+skip-l1dfl-vmentry,+mds-no -m 2048 -realtime mlock=off
-smp 1,sockets=1,cores=1,threads=1 -uuid 7e55c71a-558f-
412c-8445-db0e95fc549f -display none -no-user-config -nodefaults -rtc
base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-
shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1
-boot strict=on -kernel /var/lib/libvirt/images/guest/vmlinuz -initrd
/var/lib/libvirt/images/guest/initrd.img -append "root=/dev/vda noresume
console=tty0 console=ttyS0,38400n8 apparmor=0 net.ifnames=0
crashkernel=256M" -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive
file=/var/lib/libvirt/images/guest/disk01.ext4.qcow2,format=qcow2,if=none,id
=drive-virtio-disk0 -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on -serial stdio

-> changing "host" to CascadeLake-Server also works the same way.

Provided me:

inaddy@guest:~$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
stepping: 6
microcode   : 0x1
cpu MHz : 2095.076
cache size  : 16384 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm 
constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni 
pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 
3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb ibrs_enhanced 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep 
bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb 
avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves arat umip pku ospke 
avx512_vnni md_clear arch_capabilities
bugs: spectre_v1 spectre_v2 spec_store_bypass
bogomips: 4190.15
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

AND reading the MSR directly:

inaddy@guest:~$ sudo rdmsr 0x10a
2b

We have bits: 0 1 3 and 5 like it should be.

-

Running same QEMU cmd line, enabling +arch-capabilities in CascadeLake-
Server but without specifying any other CPU flags:

flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 syscall nx pdpe1gb rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs 
ibpb fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq 
rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 arat pku ospke avx512_vnni arch_capabilities
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds

inaddy@guest:~$ sudo rdmsr 0x10a
0

We are not enabling any mitigation flag in arch-capabilities MSR by
default, like we planned so. All CPU capabilities are going to be
enabled by hand and/or through libvirt XML definitions as soon as
libvirt gets the capabilities (this same bug).

-

Marking Disco as verified.

Thank you!


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

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in qemu source package in Bionic:
  Fix Committed
Status in libvirt source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in qemu source package in Cosmic:
  Won't Fix
Status in libvirt source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in qemu source package in Disco:
  Fix Committed
Status in libvirt source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  In Progress
Status in qemu source package in Eoan:
  Fix Released

Bug 

[Kernel-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Timo Aaltonen]

Reopening mesa for bionic, because the revert needs to be dropped once
the kernel is fixed, otherwise Ice Lake is broken because it needs
softpin for the DRI driver to work.

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

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release

[Launchpad Bug Tracker]

This bug was fixed in the package thermald - 1.9.0-1

---
thermald (1.9.0-1) unstable; urgency=medium

  * sync with latest upstream release 1.9 (LP: #1838590)
  * Add upstream fix:
- dcdaf523393a Use correct format specifier for size_t
  * Update postinst, postrm, postpreinst rn_conffile package version
  * Update debian/compat to 12

 -- Colin King   Mon, 5 Aug 2019 09:12:15
+0100

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

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

Title:
  Update thermald to 1.9 release

Status in dptfxtract package in Ubuntu:
  New
Status in thermald package in Ubuntu:
  Fix Released

Bug description:
  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
  with kernel 5.3. It would be nice to update eoan to this new release.

  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

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

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

[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Monday, 05. August 2019 20:31 UTC
  reason:
-   promote-signing-to-proposed: Ongoing -- review in progress
+   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
+ sync
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Monday, 05. August 2019 20:31 UTC
  reason:
promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
  sync
  variant: debs

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

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

[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 05. August 2019 10:51 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 05. August 2019 20:31 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Monday, 05. August 2019 20:31 UTC
  reason:
promote-signing-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

[Andy Whitcroft]

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

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

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

Title:
  xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Promote to Proposed
  phase-changed: Monday, 05. August 2019 20:31 UTC
  reason:
promote-signing-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

Okay,

So said in the merge requests, Bionic needed a new version with:

e6891e7... by Rafael David Tinoco  3 minutes ago
changelog

c27fa94... by Rafael David Tinoco  on 2019-08-02
- 0017-target-i386-add-MDS-NO-feature.patch (LP: #1828495):
  target/i386: add MDS-NO feature
  (upstream: 20140a82c674, desc: v4.0.0-721-g20140a82c6)

And the changelog stayed:

qemu (1:2.11+dfsg-1ubuntu7.17) bionic; urgency=medium

  * {Ice,Cascade}Lake IA32_ARCH_CAPABILITIES support (LP: 1828495)
Needed patch is in d/p/u/lp1828495-:
- 0017-target-i386-add-MDS-NO-feature.patch:
  target/i386: add MDS-NO feature

 -- Rafael David Tinoco   Mon, 05 Aug 2019
19:12:08 +

qemu (1:2.11+dfsg-1ubuntu7.16) bionic; urgency=medium

  * {Ice,Cascade}Lake CPUs + IA32_ARCH_CAPABILITIES support (LP: #1828495)
Needed patches are in d/p/u/lp1828495-:
- 0001-guidance-cpu-models.patch:
  docs: add guidance on configuring CPU models for x86
  + d/qemu-system-common.install: include man/man7/qemu-cpu-models.7
- 0002-msr-new-msr-indices.patch:
  i386: Add new MSR indices for IA32_PRED_CMD and IA32_ARCH_CAPABILITIES
- 0003-cpuid-feature-ia32-arch-capabilities.patch:
  i386: Add CPUID bit and feature words for IA32_ARCH_CAPABILITIES MSR
- 0004-cpuid-bit-for-wbnoinvd.patch:
  i386: Add CPUID bit for WBNOINVD
- 0005-new-cpu-model-for-icelake.patch:
  i386: Add new CPU model Icelake-{Server,Client}
- 0006-update-headers-to-4.16-rc5.patch:
  update Linux headers to 4.16-rc5
- 0007-kvm-get-msr-feature-index_list.patch:
  kvm: Add support to KVM_GET_MSR_FEATURE_INDEX_LIST and
- 0008-x86-msr-related-data-structure-changes.patch:
  x86: Data structure changes to support MSR based features
- 0009-feature-wordS-arch-capabilities.patch:
  x86: define a new MSR based feature word -- FEATURE_WORDS_ARCH
- 0010-use-kvm-get-msr-index-list.patch:
  kvm: Use KVM_GET_MSR_INDEX_LIST for MSR_IA32_ARCH_CAPABILITIES support
- 0011-disable-arch-cap-when-no-msr.patch:
  i386: kvm: Disable arch_capabilities if MSR can't be set
- 0012-arch-capabilities-migratable.patch:
  i386: Make arch_capabilities migratable
- 0013-cascadelake-server.patch:
  i386: Add new model of Cascadelake-Server
- 0014-remove-cpuid-pconfig.patch:
  i386: remove the new CPUID 'PCONFIG' from Icelake-Server CPU model
- 0015-remove-cpuid-intel_pt.patch:
  i386: remove the 'INTEL_PT' CPUID bit from named CPU models
- 0016-no-ospke-on-some.patch:
  i386: Disable OSPKE on CPU model definitions

 -- Rafael David Tinoco   Wed, 19 Jun 2019
19:48:48 +

We need the SRU for the last 2 commits (already pushed in the MR).

=

For Disco, we're good because of security maintenance you had already
done previously:

qemu (1:3.1+dfsg-2ubuntu3.1) disco-security; urgency=medium

  * SECURITY UPDATE: Add support for exposing md-clear functionality
to guests
- d/p/ubuntu/enable-md-clear.patch
- d/p/ubuntu/enable-md-no.patch
...

And enable-md-no.patch made the trick for MDS-NO bit.

So all we need is the verification of the package already in -proposed.
I'll do that now.

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in qemu source package in Bionic:
  Fix Committed
Status in libvirt source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in qemu source package in Cosmic:
  Won't Fix
Status in libvirt source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in qemu source package in Disco:
  Fix Committed
Status in libvirt source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  In Progress
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * QEMU does not support IceLake and CascadeLake CPUs specific features.
   * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR.
   * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations:
 - Rogue Data Cache Load
 - Enhanced IBRS
 - RSB Alternate
 - L1D flush need on VMENTRY
 - speculative Store Bypass
 to guests, as described in document:
 Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf

  [Test Case]

   * From Original Description:

  """
  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  

[Kernel-packages] [Bug 1834875] Re: cloud-init growpart race with udev

[Tobias Koch]

Oh, good observation, Dan. Yes, it was happening on Cosmic and later.
But I cannot say when it started. Now in a moment of despair I tried
something very unorthodox: I copied udevadm from Bionic to the Eoan
image and ran the tests again. Look and behold, all pass.

** No longer affects: linux-azure (Ubuntu)

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

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

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

[Kernel-packages] [Bug 1838443] Re: No flicker free boot since Ignoring BGRT: invalid version 0 (expected 1)

[Adolfo Jayme]

** Changed in: linux (Ubuntu)
   Importance: Undecided => 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/1838443

Title:
  No flicker free boot since Ignoring BGRT: invalid version 0 (expected
  1)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On eoan dev here:

  Flicker free booting doesn't work since I get:
  Ignoring BGRT: invalid version 0 (expected 1)
  on dmesg on my Thinkpad x230t i7-3520M (Ivy Bridge).

  Second, if I add:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.fastboot=1"
  to /etc/default/grub then it doesn't show plymouth but displays the text 
Ubuntu loading screen and I need to press ALT+F1 so GDM will show up (see 
video: [1]). If I press escape while it is displaying text Ubuntu loading, it 
loads plymouth (see video: [2]) and shows the spinner (no lenovo word) and I 
don't need to press ALT+F1 since GDM shows after plymouth. So I guess there's a 
bug there, since it should display plymouth and not the Ubuntu loading text and 
boot directly to GDM.

  Now if I patch the kernel:
  diff --git a/drivers/firmware/efi/efi-bgrt.c b/drivers/firmware/efi/efi-bgrt.c
  index b07c17643210..5754e530af9a 100644
  --- a/drivers/firmware/efi/efi-bgrt.c
  +++ b/drivers/firmware/efi/efi-bgrt.c
  @@ -42,7 +42,7 @@ void __init efi_bgrt_init(struct acpi_table_header *table)
  return;
  }
  *bgrt = *(struct acpi_table_bgrt *)table;
  -   if (bgrt->version != 1) {
  +   if (bgrt->version != 1 && false) { /* don't check BGRT version */
  pr_notice("Ignoring BGRT: invalid version %u (expected 1)\n",
     bgrt->version);
  goto out;

  And linux-modules and linux-modules-extra is not installed in that
  kernel, then I have somewhat flicker free boot.  It shows the bgrt
  screen then goes black (probably grub loading), then shows the bgrt
  screen again with the spinner.  Nice! (see video: [3])

  So, I guess my Thinkpad is not setting bgrt version properly.  So can
  we have a kernel parameter to disable checking of bgrt version?

  Then again, if I install linux-modules and linux-modules-extra then I
  get the Ubuntu loading text when booting, but if I press esc I get the
  bgrt screen with spinner.  I think it's it's a bug somewhere in the
  linux-modules package.

  [1] https://youtu.be/tAgRf2c7J4A
  [2] https://youtu.be/1ystyzLhSaw
  [3] https://youtu.be/8AAkUDO2Kt8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic (not installed)
  ProcVersionSignature: Ubuntu 5.2.0-8.9+test1-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp13358 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 30 23:49:49 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (1401 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (4 days ago)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB4WW(2.74):bd06/11/2019:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Kamal Mostafa]

Submitter has verified that the problem is fixed by a test kernel with
these two reverts applied:

Revert "ovl: set I_CREATING on inode being created"
Revert "new primitive: discard_new_inode()"

See kernel-team mailing list thread Subject: [SRU][B/OEM-B][PATCH 0/1]
Fix crash on overlay fs

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  SRU justication:
  =
  [Impact]
  Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
  based chroot with the current bionic-proposed kernel (4.15.0-56-generic
  #62-Ubuntu).

  [Fix]
  Fix protential NULL in overlay fs.

  [Test]
  Verified on fs test and dpkg installation on overlayfs.

  [Regression Potential]
  Low, remove regression of previous bionic kernel.

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

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

[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)

[Mauricio Faria de Oliveira]

Verification done on the new adapter, Solarflare X2542.

The tester reports that iperf3 tests ran solid for 24h-72h.

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

Title:
  Bionic: support for Solarflare X2542 network adapter (sfc driver)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

   * Support for Solarflare X2542 network adapter
     (Medford2 / SFC9250) in the Bionic sfc driver.

   * This network adapter is present on recent hardware,
     at least HP 2019 and Dell PowerEdge R740xd systems.

   * On recent-hardware deployments that would rather use
     the Bionic LTS / GA supported kernel and cannot move
     to HWE kernels this adapter is non functional at all.

  [Test Case]

   * The X2542 adapter has been exercised with iperf3 and nc
     across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
     on both directions, for 1 week.

     Its performance is on par with the Cosmic 4.18 kernel
     (which contains all these patches) and the out-of-tree
     driver from the vendor.

   * The 7000 series adapter (for regression testing an old model,
     supported previously) has been exercised with iperf and netperf
     (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
     host (client/server in different adapter ports isolated with
     network namespaces, so traffic goes through the network switch),
     on 10G link speed on MTUs 1500/9000, for 1 weekend.

     No regressions observed between the original and test kernels.

  [Regression Potential]

   * The patchset touches a lot of the sfc driver, so the potential
     for regression definitely exists. Thus, a lot of consideration
     and testing happened:

   * It has been tested on other adapter which uses the old code,
     and no regressions were found so far (see 7000 series above).

   * The patchset is exclusively cherry-picks, no single backport.

   * The patchset essentially moves the Bionic driver up in the
     upstream 'git log --oneline -- drivers/net/ethernet/sfc/':

     - since commit d4a7a8893d4c ("sfc: pass valid pointers from 
efx_enqueue_unwind")
     - until commit 7f61e6c6279b ("sfc: support FEC configuration through 
ethtool")
     - except for 2 commits (not needed / unrelated)
   - commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple 
filters")
   - commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of 
LOOPBACK_SGMII")
     - plus 2 more recent commits (fixes)
   - commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
   - commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new 
buffers")

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

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

Re: [Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures

[Ryan Harper]

On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi 
wrote:

> Ryan, I've uploaded a new test kernel with the fix mentioned in the
> comment before:
>
> https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/
>
> I've performed over 100 installations using curtin-nvme.sh
> (install_count = 100), no hung task timeout. I'll run other stress tests
> to make sure we're not breaking anything else with this fix, but results
> look promising so far.
>
> It'd be great if you could also do a test on your side. Thanks!
>

Thats excellent news.  I'm starting my tests on this kernel now.


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796292
>
> Title:
>   Tight timeout for bcache removal causes spurious failures
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
>

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

Title:
  Tight timeout for bcache removal causes spurious failures

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

Bug description:
  I've had a number of deployment faults where curtin would report
  Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
  deployment of 30+ nodes. Upon retrying the node would usually deploy
  fine. Experimentally I've set the timeout ridiculously high, and it
  seems I'm getting no faults with this. I'm wondering if the timeout
  for removal is set too tight, or might need to be made configurable.

  --- curtin/util.py~ 2018-05-18 18:40:48.0 +
  +++ curtin/util.py  2018-10-05 09:40:06.807390367 +
  @@ -263,7 +263,7 @@
   return _subp(*args, **kwargs)
   
   
  -def wait_for_removal(path, retries=[1, 3, 5, 7]):
  +def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
   if not path:
   raise ValueError('wait_for_removal: missing path parameter')

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

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

[Kernel-packages] [Bug 1837567] Re: disco/linux-azure: 5.0.0-1013.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1838087 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1838087
  variant: debs

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

Title:
  disco/linux-azure: 5.0.0-1013.13 -proposed tracker

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

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

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

  backports: bug 1838087 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1838087
  variant: debs

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

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

[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS

[Bryce Harrington]

That's too bad it didn't work, but thanks for testing it.  I've read
suggestions that it relates to bluetooth, so am currently testing with
that disabled in bios, but I don't have high hopes.  If it doesn't, I'll
probably just go with the replacement option myself.

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

Title:
  dell xps 9570 killer wifi reconnection issue followed by freeze +
  Ubuntu 18.04.2 LTS

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

Bug description:
  Hello Team,

  Env - Dell XPS 9570
Ubuntu 18.04.2 , HWE kernel

  We are facing intermittently wifi reconnection issue on Ubuntu 18.04.
  Software upgrade is up-to date. Also some time we facing freezing
  issue due to this hard reset required to make machine back to normal.

  Please let me know if there are any known issue with this particular
  model on 18.04 ? Please let me know.

  Thanks
  Jay
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  itops  1579 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-04-25 (17 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:671d Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0HWTMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: IT-07384
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1837567] Re: disco/linux-azure: 5.0.0-1013.13 -proposed tracker

[Steve Beattie]

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

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

Title:
  disco/linux-azure: 5.0.0-1013.13 -proposed tracker

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

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

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

  backports: bug 1838087 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1838087
  variant: debs

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

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

[Kernel-packages] [Bug 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 05. August 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

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

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

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

  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 05. August 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

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

[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Signoff
- phase-changed: Thursday, 01. August 2019 19:51 UTC
+ phase: Ready for Testing
+ phase-changed: Monday, 05. August 2019 17:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Monday, 05. August 2019 17:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837563] Re: disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker

[Steve Beattie]

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

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

Title:
  disco/linux-raspi2: 5.0.0-1014.14 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Monday, 05. August 2019 17:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1837616] Re: bionic/linux-oracle: 4.15.0-1019.21 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1837615 (xenial/linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Testing
- phase-changed: Tuesday, 30. July 2019 22:01 UTC
+ phase: Signoff
+ phase-changed: Monday, 05. August 2019 17:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-oracle: bug 1837615
  variant: debs

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

Title:
  bionic/linux-oracle: 4.15.0-1019.21 -proposed tracker

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

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

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

  backports: bug 1837615 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Signoff
  phase-changed: Monday, 05. August 2019 17:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-oracle: bug 1837615
  variant: debs

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

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

[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release

[Anthony Wong]

I'm going to update it in these few days. The helper script will have to
be adapted to the new conf file directory.

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

Title:
  Update thermald to 1.9 release

Status in dptfxtract package in Ubuntu:
  New
Status in thermald package in Ubuntu:
  New

Bug description:
  The thermald 1.9 release was just tagged, and has potential to help
  quite a bit with platform performance on some newer platforms when run
  with kernel 5.3. It would be nice to update eoan to this new release.

  > - The major change in this version is the active power limits adjustment.
  This will be useful to improve performance on some newer platform. But
  this will will lead to increase in CPU and other temperatures. Hence this
  is important to run dptfxtract version 1.4.1 tool to get performance
  sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1).
  If the default configuration picked up by thermald is not optimal, user
  can select other less aggressive configuration. Refer to the README here
  https://github.com/intel/dptfxtract/blob/master/README.txt

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[AaronMa]

** Tags added: oem-priority originate-from-1838490 sutton

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

** Description changed:

  Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
  based chroot with the current bionic-proposed kernel (4.15.0-56-generic
  #62-Ubuntu).
  
  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
+ 
+ SRU justication:
+ =
+ [Impact]
+ Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
+ based chroot with the current bionic-proposed kernel (4.15.0-56-generic
+ #62-Ubuntu).
+ 
+ [Fix]
+ Fix protential NULL in overlay fs.
+ 
+ [Test]
+ Verified on fs test and dpkg installation on overlayfs.
+ 
+ [Regression Potential]
+ Low, remove regression of previous bionic kernel.

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  SRU justication:
  =
  [Impact]
  Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
  based chroot with the current bionic-proposed kernel (4.15.0-56-generic
  #62-Ubuntu).

  [Fix]
  Fix protential NULL in overlay fs.

  [Test]
  Verified on fs test and dpkg installation on overlayfs.

  [Regression Potential]
  Low, remove regression of previous bionic kernel.

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

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

[Kernel-packages] [Bug 1838045] Update Released

[Adam Conrad]

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Header check ignore --kernelsourcedir

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released

Bug description:
  In Ubuntu 16.04/Xenial the dkms command (2.2.0.3-2ubuntu11.7) ignores
  the provided kernel source directory and then fails by not finding the
  headers.

  This was fixed upstream in 2.2.0.3-5 and landed in 18.04/Bionic.
  Proposing to backport the additional line of code into Xenial.

  +[ ! -z "$ksourcedir_fromcli" ] && DIR=$kernel_source_dir

  Testcase:
  Trying to compile any DKMS module with kernel source (headers) in a 
non-standard location (/usr/src) will fail with an error reporting missing 
headers without the change, even using --kernelsourcedir. With the patch 
applied, this works.

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

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

[Kernel-packages] [Bug 1838045] Re: Header check ignore --kernelsourcedir

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.8

---
dkms (2.2.0.3-2ubuntu11.8) xenial; urgency=medium

  * d/p/fix-kernelsource-check.patch: Take --kernelsourcedir into account
when checking for headers (from 2.2.0.3-5 "Do not ignore
--kernelsourcedir") (LP: #1838045).

 -- Stefan Bader   Fri, 26 Jul 2019 10:16:28
+0200

** Changed in: dkms (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Header check ignore --kernelsourcedir

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released

Bug description:
  In Ubuntu 16.04/Xenial the dkms command (2.2.0.3-2ubuntu11.7) ignores
  the provided kernel source directory and then fails by not finding the
  headers.

  This was fixed upstream in 2.2.0.3-5 and landed in 18.04/Bionic.
  Proposing to backport the additional line of code into Xenial.

  +[ ! -z "$ksourcedir_fromcli" ] && DIR=$kernel_source_dir

  Testcase:
  Trying to compile any DKMS module with kernel source (headers) in a 
non-standard location (/usr/src) will fail with an error reporting missing 
headers without the change, even using --kernelsourcedir. With the patch 
applied, this works.

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

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

[Kernel-packages] [Bug 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1837589 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Testing
- phase-changed: Friday, 02. August 2019 18:41 UTC
+ phase: Signoff
+ phase-changed: Monday, 05. August 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1837589
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker

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

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

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

  derivatives: bug 1837589 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Signoff
  phase-changed: Monday, 05. August 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1837589
  variant: debs

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

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

[Kernel-packages] [Bug 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1837621 (trusty/linux-azure)
  derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Monday, 05. August 2019 12:07 UTC
+ phase: Signoff
+ phase-changed: Monday, 05. August 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1837621
xenial/linux-azure-edge: bug 1837620
xenial/linux-azure/azure-kernel: bug 1837619
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1053.58 -proposed tracker

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

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

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

  backports: bug 1837621 (trusty/linux-azure)
  derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Signoff
  phase-changed: Monday, 05. August 2019 16:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1837621
xenial/linux-azure-edge: bug 1837620
xenial/linux-azure/azure-kernel: bug 1837619
  variant: debs

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

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

[Kernel-packages] [Bug 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 05. August 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

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

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

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

  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 05. August 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

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

[Kernel-packages] [Bug 1822175] Re: i3.metal flavour type fails to respond after a reboot

[Colin Ian King]

** Changed in: linux-aws (Ubuntu)
   Status: In Progress => Won't Fix

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

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

Title:
  i3.metal flavour type fails to respond after a reboot

Status in linux-aws package in Ubuntu:
  Invalid

Bug description:
  Series: Cosmic
  Instance Size: I3.Metal
  Region: (Default) US-WEST-2
  Kernel: linux-aws

  During SRU testing the i3.metal instance flavor type will sometimes
  fail to respond after the instance is rebooted. Usually this has been
  seen at least 2 or 3 times during at test cycle.

  While rebooting an I3.Metal instance on the AWS Cloud. I observed the
  following crash which resulting in tearing down the instance and
  starting over. The instance was only restarted ~4 times at the time of
  this failure.

  
  [[0;32m  OK  [0m] Reached target Shutdown.
  [[0;32m  OK  [0m] Reached target Final Step.
   Starting Reboot...
   Stopping LVM2 metadata daemon...
  [[0;32m  OK  [0m] Stopped LVM2 metadata daemon.
  [  447.340575] INFO: rcu_sched self-detected stall on CPU
  [  447.340577] INFO: rcu_sched self-detected stall on CPU
  [  447.340580] INFO: rcu_sched self-detected stall on CPU
  [  447.340587] INFO: rcu_sched self-detected stall on CPU
  [  447.340590] INFO: rcu_sched self-detected stall on CPU
  [  447.340592] INFO: rcu_sched self-detected stall on CPU
  [  447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0.
  [  447.340599] INFO: rcu_sched self-detected stall on CPU
  [  447.340602] INFO: rcu_sched self-detected stall on CPU
  [  447.340606] INFO: rcu_sched self-detected stall on CPU
  [  447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 
fqs=0 
  [  447.340617] INFO: rcu_sched self-detected stall on CPU
  [  447.340621] Do you have a strange power saving mode enabled?
  [  447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 
fqs=0 
  [  447.340632] INFO: rcu_sched self-detected stall on CPU
  [  447.340634] INFO: rcu_sched self-detected stall on CPU
  [  447.340636] INFO: rcu_sched self-detected stall on CPU
  [  447.340639] INFO: rcu_sched self-detected stall on CPU
  [  447.340641] INFO: rcu_sched self-detected stall on CPU
  [  447.340644] INFO: rcu_sched self-detected stall on CPU
  [  447.340647] INFO: rcu_sched self-detected stall on CPU

  The full log can be seen in the attached file.

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

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

[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured

[Guilherme G. Piccoli]

Eric, thanks for looking into the testing failure.

I was discussing with Cascardo today, and he was able to spot quickly the 
problem.
First, the reason "makedumpfile" test passed in ppc64el before was that the 
test was skipped; Cascardo changed "makedumpfile" to be part of the called "big 
packages"[0], in order the VMs used in the tests have more RAM. Now, the test 
gets executed and fails if kernel version is >= 4.20.

The reason of the failure was that "makedumpfile" couldn't collect a
compressed dump, falling back to 'cp' - this led to the 'if' failure in
the test. The root cause is that kernel patch 4ffe713b7587 ("powerpc/mm:
Increase the max addressable memory to 2PB"), introduced in v4.20,
requires a counterpart in "makedumpfile", in the form of patch [1].
Without that, I was able to reproduce the problem locally:

$ makedumpfile -c -d 31 /proc/vmcore /var/crash/201908051539/dump-incomplete2
get_machdep_info_ppc64: Can't detect max_physmem_bits.
makedumpfile Failed.

When I've used kernel 4.18 in the same VM, I got:

$ makedumpfile -c -d 31 /proc/vmcore core.418
Copying data  : [100.0 %] \   eta: 
0s
The dumpfile is saved to core.418

The plan here according to Cascardo is to push makedumpfile 1.6.6 (already 
containing the fix for the "physmem_bits" issue as well as my fix for this LP, 
the retry/delay mechanism) to Eoan.
After that, in my understanding, we can move on with the SRU for Bionic/Disco.

Cheers,


Guilherme


[0] https://git.launchpad.net/~cascardo/autopkgtest-cloud/commit/?id=346b786925
[1] https://salsa.debian.org/debian/makedumpfile/commit/f349b51f

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

Title:
  kdump is not captured in remote host when kdump over ssh is configured

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Committed
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Bionic:
  In Progress
Status in makedumpfile source package in Cosmic:
  Won't Fix
Status in makedumpfile source package in Disco:
  In Progress
Status in makedumpfile source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  * Kdump over network (like NFS mount or SSH dump) relies on network-
  online target from systemd. Even so, there are some NICs that report
  "Link Up" state but aren't ready to transmit packets. This is a
  generally bad behavior that is credited probably to NIC firmware
  delays, usually not fixable from drivers. Some adapters known to act
  like this are bnx2x, tg3 and ixgbe.

  * Kdump is a mechanism that may be a last resort to debug complex/hard
  to reproduce issues, so it's interesting to increase its reliability /
  resilience. We then propose here a solution/quirk to this issue on
  network dump by adding a retry/delay mechanism; if it's a network
  dump, kdump will retry some times and sleep between the attempts in
  order to exclude the case of NICs that aren't ready yet but will soon
  be able to transmit packets.

  * Although first reported by IBM in PowerPC arch, the scope for this
  issue is the NIC, and it was later reported in x86 arch too.

  [Test case]

  Usually it's difficult to naturally reproduce this issue in a deterministic 
way, but we have an artificial test case on comment #24 of this LP.
  Also, we have a report from this bug in which the user managed to reproduce 
the problem consistently - it's fixed after testing our solution.

  [Regression potential]

  There's not a clear regression potential here since it's just a retry/delay 
mechanism. Some potential problems may come from bad coding in the script.
  The delay between attempts is only 3 sec per iteration, so it shouldn't block 
the kdump progress for a high amount of time at once.

  [Other information]

  Salsa Debian commit:
  
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f

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

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

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

[Scott]

Sorry if I misunderstood the issue you are having, good luck

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Kernel-packages] [Bug 1838993] [NEW] Suspend immediately resumes on Ubuntu 18.04.2

[Tais P. Hansen]

Public bug reported:

Recently my Lenovo ThinkPad W540 laptop has been unable to suspend
correctly. It immediately wakes up after going through all the usual
steps of turning off the screens, USB devices etc.

I'm using the UI to suspend by left-clicking and holding the power off
button until it turns into a pause button, and then I left-click that
button. The laptop is docked with two monitors connected and the lid is
open (although the laptop screen is not used) when I attempt to suspend
it.

This used to work until recently. BIOS has not been touched or upgraded.


Log excerpt:

...
Aug  5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156787] PM: suspend entry 
(deep)
Aug  5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156789] PM: Syncing 
filesystems ... done.
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.015094] rfkill: input 
handler enabled
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.320163] Freezing user space 
processes ... (elapsed 0.003 seconds) done.
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] OOM killer disabled.
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] Freezing remaining 
freezable tasks ... (elapsed 0.001 seconds) done.
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.325130] Suspending 
console(s) (use no_console_suspend to debug)
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469224] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469297] sd 5:0:0:0: [sdb] 
Synchronizing SCSI cache
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469449] sd 5:0:0:0: [sdb] 
Stopping disk
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.470686] sd 0:0:0:0: [sda] 
Stopping disk
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.669512] e1000e: EEE TX LPI 
TIMER: 0011
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24054.969605] ACPI: EC: interrupt 
blocked
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.009441] ACPI: Preparing to 
enter system sleep state S3
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013106] ACPI: EC: event 
blocked
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] ACPI: EC: EC stopped
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] PM: Saving platform 
NVS memory
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013124] Disabling non-boot 
CPUs ...
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.029590] IRQ 30: no longer 
affine to CPU1
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.030620] smpboot: CPU 1 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.054769] smpboot: CPU 2 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077811] IRQ 16: no longer 
affine to CPU3
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077819] IRQ 29: no longer 
affine to CPU3
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.078828] smpboot: CPU 3 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.102970] smpboot: CPU 4 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125889] IRQ 23: no longer 
affine to CPU5
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125901] IRQ 32: no longer 
affine to CPU5
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.126914] smpboot: CPU 5 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.154299] IRQ 27: no longer 
affine to CPU6
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.155323] smpboot: CPU 6 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.181669] IRQ 26: no longer 
affine to CPU7
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.182697] smpboot: CPU 7 is 
now offline
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186538] ACPI: Low-level 
resume complete
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186589] ACPI: EC: EC started
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186590] PM: Restoring 
platform NVS memory
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189175] Enabling non-boot 
CPUs ...
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189259] x86: Booting SMP 
configuration:
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189260] smpboot: Booting 
Node 0 Processor 1 APIC 0x1
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189761]  cache: parent cpu1 
should not be sleeping
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.190157] CPU1 is up
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.190185] smpboot: Booting 
Node 0 Processor 2 APIC 0x2
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.191927]  cache: parent cpu2 
should not be sleeping
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.192148] CPU2 is up
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.192171] smpboot: Booting 
Node 0 Processor 3 APIC 0x3
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.192593]  cache: parent cpu3 
should not be sleeping
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.192828] CPU3 is up
Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: 

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

[Ubuntu Kernel Bot]

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

apport-collect 1838993

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

Title:
  Suspend immediately resumes on Ubuntu 18.04.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently my Lenovo ThinkPad W540 laptop has been unable to suspend
  correctly. It immediately wakes up after going through all the usual
  steps of turning off the screens, USB devices etc.

  I'm using the UI to suspend by left-clicking and holding the power off
  button until it turns into a pause button, and then I left-click that
  button. The laptop is docked with two monitors connected and the lid
  is open (although the laptop screen is not used) when I attempt to
  suspend it.

  This used to work until recently. BIOS has not been touched or
  upgraded.

  
  Log excerpt:

  ...
  Aug  5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156787] PM: suspend entry 
(deep)
  Aug  5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156789] PM: Syncing 
filesystems ... done.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.015094] rfkill: input 
handler enabled
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.320163] Freezing user 
space processes ... (elapsed 0.003 seconds) done.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] OOM killer 
disabled.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] Freezing 
remaining freezable tasks ... (elapsed 0.001 seconds) done.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.325130] Suspending 
console(s) (use no_console_suspend to debug)
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469224] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469297] sd 5:0:0:0: [sdb] 
Synchronizing SCSI cache
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469449] sd 5:0:0:0: [sdb] 
Stopping disk
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.470686] sd 0:0:0:0: [sda] 
Stopping disk
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.669512] e1000e: EEE TX 
LPI TIMER: 0011
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24054.969605] ACPI: EC: 
interrupt blocked
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.009441] ACPI: Preparing 
to enter system sleep state S3
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013106] ACPI: EC: event 
blocked
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] ACPI: EC: EC 
stopped
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] PM: Saving 
platform NVS memory
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013124] Disabling 
non-boot CPUs ...
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.029590] IRQ 30: no longer 
affine to CPU1
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.030620] smpboot: CPU 1 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.054769] smpboot: CPU 2 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077811] IRQ 16: no longer 
affine to CPU3
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077819] IRQ 29: no longer 
affine to CPU3
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.078828] smpboot: CPU 3 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.102970] smpboot: CPU 4 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125889] IRQ 23: no longer 
affine to CPU5
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125901] IRQ 32: no longer 
affine to CPU5
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.126914] smpboot: CPU 5 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.154299] IRQ 27: no longer 
affine to CPU6
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.155323] smpboot: CPU 6 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.181669] IRQ 26: no longer 
affine to CPU7
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.182697] smpboot: CPU 7 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186538] ACPI: Low-level 
resume complete
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186589] ACPI: EC: EC 
started
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186590] PM: Restoring 
platform NVS memory
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189175] Enabling non-boot 
CPUs ...

[Kernel-packages] [Bug 1838993] Re: Suspend immediately resumes on Ubuntu 18.04.2

[Tais P. Hansen]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838993/+attachment/5280972/+files/lspci-vnvn.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/1838993

Title:
  Suspend immediately resumes on Ubuntu 18.04.2

Status in linux package in Ubuntu:
  New

Bug description:
  Recently my Lenovo ThinkPad W540 laptop has been unable to suspend
  correctly. It immediately wakes up after going through all the usual
  steps of turning off the screens, USB devices etc.

  I'm using the UI to suspend by left-clicking and holding the power off
  button until it turns into a pause button, and then I left-click that
  button. The laptop is docked with two monitors connected and the lid
  is open (although the laptop screen is not used) when I attempt to
  suspend it.

  This used to work until recently. BIOS has not been touched or
  upgraded.

  
  Log excerpt:

  ...
  Aug  5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156787] PM: suspend entry 
(deep)
  Aug  5 16:53:10 taisph-ThinkPad-W540 kernel: [24052.156789] PM: Syncing 
filesystems ... done.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.015094] rfkill: input 
handler enabled
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.320163] Freezing user 
space processes ... (elapsed 0.003 seconds) done.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] OOM killer 
disabled.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.323453] Freezing 
remaining freezable tasks ... (elapsed 0.001 seconds) done.
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.325130] Suspending 
console(s) (use no_console_suspend to debug)
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469224] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469297] sd 5:0:0:0: [sdb] 
Synchronizing SCSI cache
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.469449] sd 5:0:0:0: [sdb] 
Stopping disk
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.470686] sd 0:0:0:0: [sda] 
Stopping disk
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24053.669512] e1000e: EEE TX 
LPI TIMER: 0011
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24054.969605] ACPI: EC: 
interrupt blocked
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.009441] ACPI: Preparing 
to enter system sleep state S3
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013106] ACPI: EC: event 
blocked
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] ACPI: EC: EC 
stopped
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013107] PM: Saving 
platform NVS memory
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.013124] Disabling 
non-boot CPUs ...
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.029590] IRQ 30: no longer 
affine to CPU1
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.030620] smpboot: CPU 1 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.054769] smpboot: CPU 2 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077811] IRQ 16: no longer 
affine to CPU3
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.077819] IRQ 29: no longer 
affine to CPU3
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.078828] smpboot: CPU 3 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.102970] smpboot: CPU 4 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125889] IRQ 23: no longer 
affine to CPU5
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.125901] IRQ 32: no longer 
affine to CPU5
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.126914] smpboot: CPU 5 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.154299] IRQ 27: no longer 
affine to CPU6
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.155323] smpboot: CPU 6 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.181669] IRQ 26: no longer 
affine to CPU7
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.182697] smpboot: CPU 7 is 
now offline
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186538] ACPI: Low-level 
resume complete
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186589] ACPI: EC: EC 
started
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.186590] PM: Restoring 
platform NVS memory
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189175] Enabling non-boot 
CPUs ...
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189259] x86: Booting SMP 
configuration:
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189260] smpboot: Booting 
Node 0 Processor 1 APIC 0x1
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.189761]  cache: parent 
cpu1 should not be sleeping
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.190157] CPU1 is up
  Aug  5 16:53:23 taisph-ThinkPad-W540 kernel: [24055.190185] smpboot: Booting 
Node 0 Processor 2 APIC 0x2

[Kernel-packages] [Bug 1830116] Re: linux-generic: missing module intel_pmc_core

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc3/

Which contains the following commit:
commit b02f6a2ef0a14af5c19780521370673f55c1476d
Author: Rajat Jain 
Date:   Thu Jun 27 20:34:13 2019 -0700

platform/x86: intel_pmc_core: Attach using APCI HID "INT33A1"

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

Title:
  linux-generic: missing module intel_pmc_core

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:

  linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device:
  00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC 
[8086:9d21] (rev 21)

  Similar bug #1730770 ?

  Release: 19.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1887 F pulseaudio
  CasperVersion: 1.405
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  LiveMediaBuild: Ubuntu 19.04 (Disco Dingo) - amd64 (20190523.21)
  MachineType: Dell Inc. Latitude E7270
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz noprompt boot=casper 
persistent persistent-path= iso-scan/filename=/disco-desktop-amd64.iso splash 
toram
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  Tags:  disco
  Uname: Linux 5.0.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/20/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 027I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn027I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7270
  dmi.product.sku: 06DB
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  eoan
  Uname: Linux 5.2.0-050200rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  eoan
  Uname: Linux 5.2.0-050200rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 1186 F pulseaudio
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  MachineType: Dell Inc. Latitude E7270
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=bcc7-cd87-42d3-b789-d5de5ca73c24 ro toram quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Rafael David Tinoco]

Alright, working on it.

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in qemu source package in Bionic:
  Fix Committed
Status in libvirt source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in qemu source package in Cosmic:
  Won't Fix
Status in libvirt source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in qemu source package in Disco:
  Fix Committed
Status in libvirt source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  In Progress
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * QEMU does not support IceLake and CascadeLake CPUs specific features.
   * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR.
   * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations:
 - Rogue Data Cache Load
 - Enhanced IBRS
 - RSB Alternate
 - L1D flush need on VMENTRY
 - speculative Store Bypass
 to guests, as described in document:
 Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf

  [Test Case]

   * From Original Description:

  """
  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

  """

  [Regression Potential]

   * Most changes are related to CPU type definitions and its supported
  features. They are all based in upstream changes but, for obvious
  reasons, backporting and/or cherry-picking those could bring issues.
  Biggest concern is breaking something that currently works. Right now,
  the parts being changed that could affect other CPU types would be
  related to a small refactoring of how the features are organized, and
  that would be seen right away when trying to start a new VM after the
  package is installed.

   * Other tests, related to the features being backported, are being
  done by our KVM regression tests, including migration combinations, to
  reduce chances that a regression is introduced.

  [Other Info]
   
   * N/A

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Stefan Bader]

I confirmed this in a VM which was doing a dist-upgrade inside an
overlay chroot ok with the 4.15.0-55 kernel and did the crash doing the
same on 4.15.0-56.

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Stefan Bader]

** Attachment added: "current-dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838982/+attachment/5280970/+files/current-dmesg

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

[Kernel-packages] [Bug 1838921] Re: priority of OBSOLETE_BY should higher than "force"

[Timo Aaltonen]

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

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

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

Title:
  priority of OBSOLETE_BY should higher than "force"

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  New
Status in dkms source package in Bionic:
  New
Status in dkms source package in Disco:
  New

Bug description:
  [Impact]
  the priority of OBSOLETE_BY should higher than "force". #89 
https://github.com/dell/dkms/issues/89

  [Test case]
  1. install the dkms package which already patched (also can be found from my 
test ppa[1])
  2. install a DKMS which has OBSOLETE_BY and FORCE
  e.g.ath10k of my testing ppa : [2]
   - the target dkms defined OBSOLETE_BY and FORCE
   - user install dkms on a system which installed kernel version less than 
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
   - the dkms can be installed well.

  [Regression potential]
  medium as it touched the version sanity. This change land a change from 
upstream.

  [1]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89
  [2]:https://code.launchpad.net/~alextu/+recipe/2.3-3ubuntu9.5-closes89-dkms

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1838921/+subscriptions

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

[Kernel-packages] [Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Stefan Bader]

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

[Kernel-packages] [Bug 1835072] Re: vm related hang on Eoan 5.2.0-7-generic

[Colin Ian King]

Fresh install, running 5.2.0-8-generic, can't trip this anymore. Closing
this bug report.

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1835072

Title:
  vm related hang on Eoan 5.2.0-7-generic

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When exercising several VMs that are large enough to start causing
  swapping I occasionally get the following hang:

  [21751.030907] INFO: task CPU 2/KVM:16977 blocked for more than 120 seconds.
  [21751.031268]   Tainted: P   OE 5.2.0-7-generic #8
  [21751.031624] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [21751.032005] CPU 2/KVM   D0 16977  1 0x0100
  [21751.032007] Call Trace:
  [21751.032014]  __schedule+0x2ba/0x650
  [21751.032016]  schedule+0x31/0xa0
  [21751.032018]  rwsem_down_read_failed+0xec/0x180
  [21751.032021]  ? hrtimer_try_to_cancel+0x2e/0x110
  [21751.032023]  down_read+0x45/0x50
  [21751.032049]  kvm_host_page_size+0x42/0x90 [kvm]
  [21751.032064]  mapping_level+0x60/0x130 [kvm]
  [21751.032078]  tdp_page_fault+0xb6/0x280 [kvm]
  [21751.032084]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032088]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032102]  kvm_mmu_page_fault+0x79/0x640 [kvm]
  [21751.032106]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032109]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032112]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032115]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032118]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032121]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032124]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032127]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032130]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032133]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032136]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032139]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032142]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032145]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032148]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032151]  ? vmx_vmexit+0x1b/0x30 [kvm_intel]
  [21751.032154]  ? vmx_vmexit+0xf/0x30 [kvm_intel]
  [21751.032157]  handle_ept_violation+0xcf/0x220 [kvm_intel]
  [21751.032161]  vmx_handle_exit+0xab/0x7d0 [kvm_intel]
  [21751.032174]  vcpu_enter_guest+0x2db/0x1500 [kvm]
  [21751.032178]  ? skip_emulated_instruction+0x75/0xb0 [kvm_intel]
  [21751.032191]  ? kvm_skip_emulated_instruction+0x59/0xa0 [kvm]
  [21751.032205]  kvm_arch_vcpu_ioctl_run+0xd5/0x580 [kvm]
  [21751.032217]  kvm_vcpu_ioctl+0x24f/0x620 [kvm]
  [21751.032219]  ? __seccomp_filter+0x7e/0x6c0
  [21751.032221]  ? __switch_to_asm+0x40/0x70
  [21751.03]  ? __switch_to_asm+0x34/0x70
  [21751.032224]  ? __switch_to_asm+0x40/0x70
  [21751.032225]  ? __switch_to_asm+0x34/0x70
  [21751.032227]  ? __switch_to_asm+0x40/0x70
  [21751.032228]  ? __switch_to_asm+0x34/0x70
  [21751.032230]  ? __switch_to_asm+0x40/0x70
  [21751.032232]  ? __switch_to_asm+0x34/0x70
  [21751.032234]  do_vfs_ioctl+0xad/0x640
  [21751.032236]  ? __secure_computing+0x42/0xd0
  [21751.032238]  ksys_ioctl+0x6b/0xa0
  [21751.032239]  __x64_sys_ioctl+0x1e/0x30
  [21751.032242]  do_syscall_64+0x5e/0x140
  [21751.032244]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [21751.032245] RIP: 0033:0x7f64a3fb0417
  [21751.032250] Code: Bad RIP value.
  [21751.032251] RSP: 002b:7f64937fd578 EFLAGS: 0246 ORIG_RAX: 
0010
  [21751.032252] RAX: ffda RBX: ae80 RCX: 
7f64a3fb0417
  [21751.032253] RDX:  RSI: ae80 RDI: 
0014
  [21751.032254] RBP:  R08: 5589927145d0 R09: 
3b9aca00
  [21751.032255] R10: 0001 R11: 0246 R12: 
5589935ff710
  [21751.032255] R13: 7f64a199d000 R14:  R15: 
5589935ff710

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

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

[Kernel-packages] [Bug 1838443] Re: No flicker free boot since Ignoring BGRT: invalid version 0 (expected 1)

[shemgp]

Want me to cook up a patch or a debdiff?  If what you said should be done, I 
think it can be solved by removing the:
 goto out;
and changing the wording of: Ignoring BGRT: invalid version %u (expected 1)

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

Title:
  No flicker free boot since Ignoring BGRT: invalid version 0 (expected
  1)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On eoan dev here:

  Flicker free booting doesn't work since I get:
  Ignoring BGRT: invalid version 0 (expected 1)
  on dmesg on my Thinkpad x230t i7-3520M (Ivy Bridge).

  Second, if I add:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.fastboot=1"
  to /etc/default/grub then it doesn't show plymouth but displays the text 
Ubuntu loading screen and I need to press ALT+F1 so GDM will show up (see 
video: [1]). If I press escape while it is displaying text Ubuntu loading, it 
loads plymouth (see video: [2]) and shows the spinner (no lenovo word) and I 
don't need to press ALT+F1 since GDM shows after plymouth. So I guess there's a 
bug there, since it should display plymouth and not the Ubuntu loading text and 
boot directly to GDM.

  Now if I patch the kernel:
  diff --git a/drivers/firmware/efi/efi-bgrt.c b/drivers/firmware/efi/efi-bgrt.c
  index b07c17643210..5754e530af9a 100644
  --- a/drivers/firmware/efi/efi-bgrt.c
  +++ b/drivers/firmware/efi/efi-bgrt.c
  @@ -42,7 +42,7 @@ void __init efi_bgrt_init(struct acpi_table_header *table)
  return;
  }
  *bgrt = *(struct acpi_table_bgrt *)table;
  -   if (bgrt->version != 1) {
  +   if (bgrt->version != 1 && false) { /* don't check BGRT version */
  pr_notice("Ignoring BGRT: invalid version %u (expected 1)\n",
     bgrt->version);
  goto out;

  And linux-modules and linux-modules-extra is not installed in that
  kernel, then I have somewhat flicker free boot.  It shows the bgrt
  screen then goes black (probably grub loading), then shows the bgrt
  screen again with the spinner.  Nice! (see video: [3])

  So, I guess my Thinkpad is not setting bgrt version properly.  So can
  we have a kernel parameter to disable checking of bgrt version?

  Then again, if I install linux-modules and linux-modules-extra then I
  get the Ubuntu loading text when booting, but if I press esc I get the
  bgrt screen with spinner.  I think it's it's a bug somewhere in the
  linux-modules package.

  [1] https://youtu.be/tAgRf2c7J4A
  [2] https://youtu.be/1ystyzLhSaw
  [3] https://youtu.be/8AAkUDO2Kt8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic (not installed)
  ProcVersionSignature: Ubuntu 5.2.0-8.9+test1-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp13358 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Jul 30 23:49:49 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (1401 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash i915.fastboot=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (4 days ago)
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB4WW(2.74):bd06/11/2019:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  System crashes on hot adding a core with drmgr command
  (4.15.0-48-generic)

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

Bug description:
  [Impact]
  On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to 
crash. The patches identified to fix these issues disables changing the NUMA 
associations for CPUs and Memory at runtime by default.

  [Test]
  # drmgr -c cpu -r -q 1
  # drmgr -c cpu -a -q 1
  Test kernel available in ppa:ubuntu-power-triage/lp1833716
  Please see comment #2 for before and after results with the patches applied.

  [Fix]
  558f86493df0 powerpc/numa: document topology_updates_enabled, disable by 
default
  2d4d9b308f8f powerpc/numa: improve control of topology updates

  [Regression Potential]
  The two patches relate to powerpc/numa and does not impact other 
architectures or platform code. Regression potential is low.

  [Other Information]
  == Comment: #0 - Hari Krishna Bathini  - 2019-05-07 
13:18:35 ==
  ---Problem Description---
  On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the 
kernel
  with below traces:

  ---
  root@ubuntu:~# drmgr -c cpu -r -q 1
  Validating CPU DLPAR capability...yes.
  CPU 9
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~#
  root@ubuntu:~# drmgr -c cpu -a -q 1
  Validating CPU DLPAR capability...yes.
  [  218.555493] BUG: arch topology borken
  [  218.03]  the DIE domain not a subset of the NODE domain
  [  218.12] BUG: arch topology borken
  [  218.16]  the DIE domain not a subset of the NODE domain
  [  218.23] BUG: arch topology borken
  [  218.28]  the DIE domain not a subset of the NODE domain
  [  218.35] BUG: arch topology borken
  [  218.39]  the DIE domain not a subset of the NODE domain
  [  218.45] BUG: arch topology borken
  [  218.50]  the DIE domain not a subset of the NODE domain
  [  218.56] BUG: arch topology borken
  [  218.60]  the DIE domain not a subset of the NODE domain
  [  218.67] BUG: arch topology borken
  [  218.71]  the DIE domain not a subset of the NODE domain
  [  218.77] BUG: arch topology borken
  [  218.81]  the DIE domain not a subset of the NODE domain
  [  218.555672] Unable to handle kernel paging request for data at address 
0x9332ae80f961139f
  [  218.555679] Faulting instruction address: 0xc01768cc
  [  218.555686] Oops: Kernel access of bad area, sig: 11 [#1]
  [  218.555691] LE SMP NR_CPUS=2048 NUMA pSeries
  [  218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum
  [  218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 
4.15.0-48-generic #51-Ubuntu
  [  218.555757] Workqueue: events cpuset_hotplug_workfn
  [  218.555763] NIP:  c01768cc LR: c01769a8 CTR: 

  [  218.555770] REGS: c001f5f1f530 TRAP: 0380   Not tainted  
(4.15.0-48-generic)
  [  218.555776] MSR:  80009033   CR: 22824228  
XER: 0004
  [  218.555789] CFAR: c0176920 SOFTE: 1
  [  218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 
c001f7bfd200
  [  218.555789] GPR04: 0001  0008 
0010
  [  218.555789] GPR08: 0018  c001f7bfd408 

  [  218.555789] GPR12: 8000 c7a35800 0007 
c001f549d900
  [  218.555789] GPR16: 0040 c1722494 c001f0f29400 
0001
  [  218.555789] GPR20: c001ffb68580 0008 c11d8580 
c171dd78
  [  218.555789] GPR24:  e830 ec30 
12af
  [  218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 
9332ae80f961139f
  [  218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0
  [  218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0
  [  218.555871] Call Trace:
  [  218.555875] [c001f5f1f7b0] [ec30] 0xec30 
(unreliable)
  [  218.555884] [c001f5f1f7f0] [c01769a8] 
destroy_sched_domain+0x38/0xc0
  [  218.555892] [c001f5f1f820] [c0176eb0] 
cpu_attach_domain+0xf0/0x870
  [  218.555900] [c001f5f1f960] [c0178884] 
build_sched_domains+0x1254/0x12f0
  [  

[Kernel-packages] [Bug 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Friday, 02. August 2019 15:10 UTC
+ phase: Testing
+ phase-changed: Monday, 05. August 2019 13:31 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

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

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

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

  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 05. August 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

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

[Kernel-packages] [Bug 1838982] [NEW] unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

[Stefan Bader]

Public bug reported:

Crash happens during the setup (dpkg) phase of sbuild using a overlayfs
based chroot with the current bionic-proposed kernel (4.15.0-56-generic
#62-Ubuntu).

[25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
[25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
[25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
[25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
[25553.379401]  ovl_lookup+0x275/0x760 [overlay]
[25553.379406]  lookup_slow+0xab/0x170
[25553.379409]  ? lookup_slow+0xab/0x170
[25553.379413]  walk_component+0x1c3/0x470
[25553.379416]  ? path_init+0x177/0x2f0
[25553.379419]  path_lookupat+0x84/0x1f0
[25553.379423]  ? __put_cred+0x3d/0x50
[25553.379426]  ? revert_creds+0x2f/0x40
[25553.379429]  filename_lookup+0xb6/0x190
[25553.379434]  ? __check_object_size+0xaf/0x1b0
[25553.379438]  user_path_at_empty+0x36/0x40
[25553.379441]  ? user_path_at_empty+0x36/0x40
[25553.379444]  SyS_chown+0x4d/0xe0
[25553.379449]  do_syscall_64+0x73/0x130
[25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Status: Confirmed


** Tags: bionic

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

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

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

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

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1838982

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

Bug description:
  Crash happens during the setup (dpkg) phase of sbuild using a
  overlayfs based chroot with the current bionic-proposed kernel
  (4.15.0-56-generic #62-Ubuntu).

  [25553.379381]  ? ovl_get_origin_fh+0x23/0x150 [overlay]
  [25553.379386]  ? ovl_inode_test+0x20/0x20 [overlay]
  [25553.379390]  ? ovl_lock_rename_workdir+0x50/0x50 [overlay]
  [25553.379396]  ovl_get_inode+0xa2/0x450 [overlay]
  [25553.379401]  ovl_lookup+0x275/0x760 [overlay]
  [25553.379406]  lookup_slow+0xab/0x170
  [25553.379409]  ? lookup_slow+0xab/0x170
  [25553.379413]  walk_component+0x1c3/0x470
  [25553.379416]  ? path_init+0x177/0x2f0
  [25553.379419]  path_lookupat+0x84/0x1f0
  [25553.379423]  ? __put_cred+0x3d/0x50
  [25553.379426]  ? revert_creds+0x2f/0x40
  [25553.379429]  filename_lookup+0xb6/0x190
  [25553.379434]  ? __check_object_size+0xaf/0x1b0
  [25553.379438]  user_path_at_empty+0x36/0x40
  [25553.379441]  ? user_path_at_empty+0x36/0x40
  [25553.379444]  SyS_chown+0x4d/0xe0
  [25553.379449]  do_syscall_64+0x73/0x130
  [25553.379453]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

Re: [Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader

[Uwe Schindler]

Ok, I will try newer kernel on the weekend. Until then I can't check it.
Sorry.

Uwe

Am August 5, 2019 12:55:30 PM UTC schrieb Kai-Heng Feng 
:
>I asked that because I've observed that on my machine if I reboot the
>system from older kernel.
>New kernels have a fix for USB2 LPM shutdown, exactly for issues like
>this one.
>
>-- 
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1838886
>
>Title:
>  New ID in ums-realtek module breaks cardreader
>
>Status in linux package in Ubuntu:
>  Confirmed
>
>Bug description:
>  When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the
> Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly.
>
>  Previously it accepted SD cards all the time. Now it looks like you
>  have to insert the card on booting or shortly after booting to access
>  it. If you wait longer, it no longer detects the card. The reason for
> this can be found in the kernel log (dmes). On boot it seems to detect
>  a card in the reader, although there is none. After a while it says
>  "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead
>  device" and then resets the device. It tries this 3 times and then
>  gives up completely. After that any real device plugged is no longer
>  detected.
>
>  The device is:  idVendor=0bda, idProduct=0153, bcdDevice=57.13
>
>  Support for this was added in mainline kernel:
>https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577
>
>  And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE
>  stack.
>
>  Full log on boot (no card inserted):
>
>[3.689559] usb 1-5.1: new high-speed USB device number 4 using
>xhci_hcd
>[3.898312] usb 1-5.1: New USB device found, idVendor=0bda,
>idProduct=0153, bcdDevice=57.13
>[3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2,
>SerialNumber=3
>  [3.898319] usb 1-5.1: Product: USB2.0-CRW
>  [3.898322] usb 1-5.1: Manufacturer: Generic
>  [3.898324] usb 1-5.1: SerialNumber: 2012092657120
>  [3.911571] usbcore: registered new interface driver usb-storage
>  [3.914796] usbcore: registered new interface driver uas
> [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
>  [3.924478] scsi host2: usb-storage 1-5.1:1.0
>  [3.924649] usbcore: registered new interface driver ums-realtek
>  [...]
> [   13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
>  [   13.509592] scsi host2: usb-storage 1-5.1:1.0
>[   14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO  
> 1.00 PQ: 0 ANSI: 4
>  [   14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0
>  [   14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk
>  [  170.961728] scsi 2:0:0:0: rejecting I/O to dead device
>[  170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result:
>hostbyte=DID_OK driverbyte=DRIVER_ERROR
>  [  170.962073] scsi 2:0:0:0: [sdb] Sense not available.
>[  171.985846] usb 1-5.1: new high-speed USB device number 8 using
>xhci_hcd
>[  172.194299] usb 1-5.1: New USB device found, idVendor=0bda,
>idProduct=0153, bcdDevice=57.13
>[  172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2,
>SerialNumber=3
>  [  172.194327] usb 1-5.1: Product: USB2.0-CRW
>  [  172.194338] usb 1-5.1: Manufacturer: Generic
>  [  172.194346] usb 1-5.1: SerialNumber: 2012092657120
> [  172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
>  [  172.212503] scsi host2: usb-storage 1-5.1:1.0
>[  173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO  
> 1.00 PQ: 0 ANSI: 4
>  [  173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0
>  [  173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk
>  [  329.654468] usb 1-5.1: USB disconnect, device number 8
>  [  329.665905] scsi 2:0:0:0: rejecting I/O to dead device
>[  329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result:
>hostbyte=DID_OK driverbyte=DRIVER_ERROR
>  [  329.665976] scsi 2:0:0:0: [sdb] Sense not available.
>[  330.701685] usb 1-5.1: new high-speed USB device number 9 using
>xhci_hcd
>[  330.910415] usb 1-5.1: New USB device found, idVendor=0bda,
>idProduct=0153, bcdDevice=57.13
>[  330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2,
>SerialNumber=3
>  [  330.910444] usb 1-5.1: Product: USB2.0-CRW
>  [  330.910455] usb 1-5.1: Manufacturer: Generic
>  [  330.910463] usb 1-5.1: SerialNumber: 2012092657120
> [  330.917013] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
>  [  330.932295] scsi host2: usb-storage 1-5.1:1.0
>[  331.952829] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO  
> 1.00 PQ: 0 ANSI: 4
>  [  331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0
>  [  331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk
>  [  488.343981] usb 1-5.1: USB disconnect, device number 9
>  [  488.354292] scsi 2:0:0:0: rejecting I/O to dead device
>[  488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: 

[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures

[Andrea Righi]

Ryan, I've uploaded a new test kernel with the fix mentioned in the
comment before:

https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/

I've performed over 100 installations using curtin-nvme.sh
(install_count = 100), no hung task timeout. I'll run other stress tests
to make sure we're not breaking anything else with this fix, but results
look promising so far.

It'd be great if you could also do a test on your side. Thanks!

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

Title:
  Tight timeout for bcache removal causes spurious failures

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

Bug description:
  I've had a number of deployment faults where curtin would report
  Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
  deployment of 30+ nodes. Upon retrying the node would usually deploy
  fine. Experimentally I've set the timeout ridiculously high, and it
  seems I'm getting no faults with this. I'm wondering if the timeout
  for removal is set too tight, or might need to be made configurable.

  --- curtin/util.py~ 2018-05-18 18:40:48.0 +
  +++ curtin/util.py  2018-10-05 09:40:06.807390367 +
  @@ -263,7 +263,7 @@
   return _subp(*args, **kwargs)
   
   
  -def wait_for_removal(path, retries=[1, 3, 5, 7]):
  +def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
   if not path:
   raise ValueError('wait_for_removal: missing path parameter')

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

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

[Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader

[Kai-Heng Feng]

I asked that because I've observed that on my machine if I reboot the system 
from older kernel.
New kernels have a fix for USB2 LPM shutdown, exactly for issues like this one.

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

Title:
  New ID in ums-realtek module breaks cardreader

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the
  Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly.

  Previously it accepted SD cards all the time. Now it looks like you
  have to insert the card on booting or shortly after booting to access
  it. If you wait longer, it no longer detects the card. The reason for
  this can be found in the kernel log (dmes). On boot it seems to detect
  a card in the reader, although there is none. After a while it says
  "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead
  device" and then resets the device. It tries this 3 times and then
  gives up completely. After that any real device plugged is no longer
  detected.

  The device is:  idVendor=0bda, idProduct=0153, bcdDevice=57.13

  Support for this was added in mainline kernel:
  
https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577

  And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE
  stack.

  Full log on boot (no card inserted):

  [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd
  [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [3.898319] usb 1-5.1: Product: USB2.0-CRW
  [3.898322] usb 1-5.1: Manufacturer: Generic
  [3.898324] usb 1-5.1: SerialNumber: 2012092657120
  [3.911571] usbcore: registered new interface driver usb-storage
  [3.914796] usbcore: registered new interface driver uas
  [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [3.924478] scsi host2: usb-storage 1-5.1:1.0
  [3.924649] usbcore: registered new interface driver ums-realtek
  [...]
  [   13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [   13.509592] scsi host2: usb-storage 1-5.1:1.0
  [   14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [   14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [   14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  170.961728] scsi 2:0:0:0: rejecting I/O to dead device
  [  170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  170.962073] scsi 2:0:0:0: [sdb] Sense not available.
  [  171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd
  [  172.194299] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [  172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  172.194327] usb 1-5.1: Product: USB2.0-CRW
  [  172.194338] usb 1-5.1: Manufacturer: Generic
  [  172.194346] usb 1-5.1: SerialNumber: 2012092657120
  [  172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [  172.212503] scsi host2: usb-storage 1-5.1:1.0
  [  173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [  173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [  173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  329.654468] usb 1-5.1: USB disconnect, device number 8
  [  329.665905] scsi 2:0:0:0: rejecting I/O to dead device
  [  329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  329.665976] scsi 2:0:0:0: [sdb] Sense not available.
  [  330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd
  [  330.910415] usb 1-5.1: New USB device found, idVendor=0bda, 
idProduct=0153, bcdDevice=57.13
  [  330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  330.910444] usb 1-5.1: Product: USB2.0-CRW
  [  330.910455] usb 1-5.1: Manufacturer: Generic
  [  330.910463] usb 1-5.1: SerialNumber: 2012092657120
  [  330.917013] ums-realtek 1-5.1:1.0: USB Mass Storage device detected
  [  330.932295] scsi host2: usb-storage 1-5.1:1.0
  [  331.952829] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 
PQ: 0 ANSI: 4
  [  331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0
  [  331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk
  [  488.343981] usb 1-5.1: USB disconnect, device number 9
  [  488.354292] scsi 2:0:0:0: rejecting I/O to dead device
  [  488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: 
hostbyte=DID_OK driverbyte=DRIVER_ERROR
  [  488.356458] scsi 2:0:0:0: [sdb] Sense not available.

  After time 488, any SD card inserted is no longer 

[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL

[Timo Aaltonen]

looks like a patch to disable softpin on mesa (to fix bug #1836721)
actually regressed ICL which needs softpin... so now softpin needs to be
backported to bionic kernel (4.15) so that the mesa revert can be
dropped

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

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

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based 
on 18.04.3 graphics stack with linux-oem-osp1 kernel.

  
  [Test case]
  The usual desktop usage, graphics tests etc.

  
  [Regression potential]
  Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and 
it can't regress any currently running system.

  Mesa backports are limited to ICL, so they shouldn't regress earlier
  generations either.

  --

  Original description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.2
  Target Mesa: 19.1

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

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

[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL

[Timo Aaltonen]

eoan has 5.2

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

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

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based 
on 18.04.3 graphics stack with linux-oem-osp1 kernel.

  
  [Test case]
  The usual desktop usage, graphics tests etc.

  
  [Regression potential]
  Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and 
it can't regress any currently running system.

  Mesa backports are limited to ICL, so they shouldn't regress earlier
  generations either.

  --

  Original description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.2
  Target Mesa: 19.1

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

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

[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Christian Ehrhardt ]

@Ai Lim, it would be great to get your testing on the PPA asap.

@Rafael - we already have the fixup. I have provided feedback on the MP,
I think we can quickly sponsor something new. That means we don't need
to go the full verification-failed, reject, new upload path - instead we
will ask to accept the new version with the minor fixup that was needed.

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in qemu source package in Bionic:
  Fix Committed
Status in libvirt source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in qemu source package in Cosmic:
  Won't Fix
Status in libvirt source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in qemu source package in Disco:
  Fix Committed
Status in libvirt source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  In Progress
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * QEMU does not support IceLake and CascadeLake CPUs specific features.
   * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR.
   * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations:
 - Rogue Data Cache Load
 - Enhanced IBRS
 - RSB Alternate
 - L1D flush need on VMENTRY
 - speculative Store Bypass
 to guests, as described in document:
 Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf

  [Test Case]

   * From Original Description:

  """
  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

  """

  [Regression Potential]

   * Most changes are related to CPU type definitions and its supported
  features. They are all based in upstream changes but, for obvious
  reasons, backporting and/or cherry-picking those could bring issues.
  Biggest concern is breaking something that currently works. Right now,
  the parts being changed that could affect other CPU types would be
  related to a small refactoring of how the features are organized, and
  that would be seen right away when trying to start a new VM after the
  package is installed.

   * Other tests, related to the features being backported, are being
  done by our KVM regression tests, including migration combinations, to
  reduce chances that a regression is introduced.

  [Other Info]
   
   * N/A

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

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

[Kernel-packages] [Bug 1831700] Re: Mesa 19.0.8 stable release

[Timo Aaltonen]

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

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Disco)

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

Title:
  Mesa 19.0.8 stable release

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  19.04 released with mesa 19.0.2. We need the last point release of the
  19.0.x series in disco and backported for 18.04.3 in order to have the
  most robust base for the image.

  [Test case]

  Check on intel/radeon hw that things still work fine.

  [Regression potential]

  this is the last update of the series, all regressions should be
  shaken off at this point by upstream CI/community

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

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

[Kernel-packages] [Bug 1837622] Re: xenial/linux-azure: 4.15.0-1053.58 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

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

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1837621 (trusty/linux-azure)
  derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Monday, 05. August 2019 07:55 UTC
+ phase: Testing
+ phase-changed: Monday, 05. August 2019 12:07 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1837621
xenial/linux-azure-edge: bug 1837620
xenial/linux-azure/azure-kernel: bug 1837619
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1053.58 -proposed tracker

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

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

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

  backports: bug 1837621 (trusty/linux-azure)
  derivatives: bug 1837619 (azure-kernel), bug 1837620 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837626
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Monday, 05. August 2019 12:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1837621
xenial/linux-azure-edge: bug 1837620
xenial/linux-azure/azure-kernel: bug 1837619
  variant: debs

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

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

[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

[Andrea Righi]

** Description changed:

- $ cat /proc/version_signature 
+ [Impact]
+ 
+ bcache_allocator() can call the following:
+ 
+  bch_allocator_thread()
+   -> bch_prio_write()
+  -> bch_bucket_alloc()
+ -> wait on >set->bucket_wait
+ 
+ But the wake up event on bucket_wait is supposed to come from 
bch_allocator_thread() itself causing a deadlock.
+ 
+ [Test Case]
+ 
+ This is a simple script that can easily trigger the deadlock condition:
+ https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh
+ 
+ A better test case has been also provided in bug 1796292 (duplicate of this 
bug):
+ 
https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh
+ 
+ [Fix]
+ 
+ Fix by making the call to bch_prio_write() non-blocking, so that
+ bch_allocator_thread() never waits on itself. Moreover, make sure to
+ wake up the garbage collector thread when bch_prio_write() is failing to
+ allocate buckets to increase the chance of freeing up more buckets.
+ 
+ In addition to that it would be safe to also import other upstream
+ bcache fixes (all clean cherry picks):
+ 
+ 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in 
cached_def_free()
+ 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock 
later in cached_dev_free()
+ ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace 
bch_read_string_list() by __sysfs_match_string()
+ ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to 
sysfs.c
+ 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays 
to sysfs.c
+ 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in 
bcache_device_init()
+ 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse 
complaints about lock imbalances
+ 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about 
set-but-not-used variables
+ f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable
+ 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings
+ 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through
+ 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to 
__bch_check_keys()
+ fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation
+ ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable 
in memory shrink
+ f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in 
memory shrink
+ 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output 
value of strip size
+ 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform 
duplicated CACHE_SET_IO_DISABLE set
+ c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy 
during journal
+ a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic
+ 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on 
large devices
+ 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set 
BCACHE_DEV_WB_RUNNING when cached device attached
+ eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot()
+ 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard 
operation
+ 
+ [Regression Potential]
+ 
+ The upstream fixes are all clean cherry picks from stable (most of them
+ are small cleanups), so regression potential is minimal.
+ 
+ The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in
+ bcache_allocator()" that is addressing the main deadlock bug (that seems
+ to be a mainline bug - not fixed yet). We should spend more time trying
+ to reproduce this deadlock with a mainline kernel and post the patch to
+ the LKML for review / feedback.
+ 
+ However, considering that this patch seems to fix/prevent the specific
+ deadlock problem reported in this bug (tested on the affected platform)
+ it can be considered safe to apply it.
+ 
+ [Original Bug Report]
+ 
+ $ cat /proc/version_signature
  Ubuntu 4.15.0-29.31-generic 4.15.18
  
  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10
  
  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
-   Installed: 4.15.0-29.31
-   Candidate: 4.15.0-29.31
-   Version table:
-  *** 4.15.0-29.31 500
- 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 4.15.0-29.31
+   Candidate: 4.15.0-29.31
+   Version table:
+  *** 4.15.0-29.31 500
+ 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
- 
- 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device
+ 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem
+ on top of a bcache device
  
  4) mkfs.ext4 doesn't return and kernel prints hung process info
  
  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

[Thadeu Lima de Souza Cascardo]

It was implemented, but the upload did not build on that ppa, because I
used different versions. I am still catching up after vacation time, so
will post some updates as soon as I have them.

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Incomplete
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  New
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  After a CPU add/hotplug operation on Power systems, kdump will fail after a 
crash. The kdump kernel needs to be reloaded after a CPU add/hotplug.

  [Test case]
  Do CPU add/hotplug, trigger a crash, and check for a successful kdump.

  [Regression potential]
  Multiple reloads caused by multiple sequential CPU adds may cause spurious 
log results, and systemd may fail to properly reload the kdump kernel. This has 
been handled by resetting the failure counter when doing such reloads.

  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.

  Machine Type = na

  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim

  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---

  ---uname output---
  na

  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-
  restart kdump-tools.service"

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

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

[Kernel-packages] [Bug 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Friday, 02. August 2019 15:10 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

Title:
  bionic/linux-azure: 5.0.0-1013.13~18.04.2 -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:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

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

  derivatives: bug 1838086 (azure-kernel), bug 1837566 (bionic/linux-
  azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837567
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Promote to Proposed
  phase-changed: Friday, 02. August 2019 15:10 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  trackers:
bionic/linux-azure-edge: bug 1837566
bionic/linux-azure/azure-kernel: bug 1838086
  variant: debs

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

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

[Kernel-packages] [Bug 1832795] Re: Race in aufs leads to use-after-free

[Seth Forshee]

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

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

Title:
  Race in aufs leads to use-after-free

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification

  Impact: A race in aufs can result in use of a DYNOP object which is
  being freed after its reference count reaches 0, leading to an oops.

  Fix: Upstream fix to aufs to ignore objects whose reference count is
  0.

  Regression Potential: Low, limited to aufs and confirmed in testing to
  fix the issue.

  ---

  I have found and reported a critical bug in aufs (as shipped with the
  latest Ubuntu kernels, both on Bionic and Xenial), which potentially
  affects anyone running Docker on Ubuntu using aufs graph driver. The
  fix has been developed, tested at least by me to fix the issue, and
  committed into upstream aufs git repos

  The nature of the bug is, in case of multiple parallels aufs mounts
  and unmounts, the kernel can screw up krefs, and once that happens,
  the only remedy is to reboot it (as commands like mount/umount or cat
  /proc/mounts are all stuck in syscalls).

  I would appreciate syncing aufs with the latest upstream release from
  git, as it was done a few times already, or at least taking the below
  fix (whatever suits maintainers better).

  The fixed versions are the ones marked with 20190610, and from what I
  see they are available for all kernel versions since 4.14 (for
  example, 4.15 tree is here:
  https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4,
  a backport might be needed, but it should be trivial.

  Original bug report:
  https://sourceforge.net/p/aufs/mailman/message/36680389/

  Fix:
  
https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3

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

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

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

[Christian Ehrhardt ]

Per [1] this means "In Progress" until such a seed/dependency change is
done.

[1]: https://wiki.ubuntu.com/MIRTeam#Process_states

** Changed in: thunderbolt-tools (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  In Progress

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

[Christian Ehrhardt ]

@cking - yes the comments by Seth and the later update of Doko a year ago are 
clear.
This is ready to land just someone needs to add a dependency or seed change to 
pull it in.

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

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  In Progress

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

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

-- 
Mailing list: