[Kernel-packages] [Bug 1856813] Re: Touchpad on X1 Carbon G6 is slow and sloppy

2019-12-17 Thread Daniel van Vugt
** Tags added: patch

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

Title:
  Touchpad on X1 Carbon G6 is slow and sloppy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on X1 Carbon G6 is slow and sloppy

  Because:
  [2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 
PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not 
used, you might want to try setting psmouse.synaptics_intertouch to 1 and 
report this to linux-in...@vger.kernel.org.

  Adding kernel parameter psmouse.synaptics_intertouch=1 indeed fixes
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 18 14:09:51 2019
  InstallationDate: Installed on 2019-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20KGS4XY00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=204dc145-c221-45e3-99f4-45107dc1b8d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS4XY00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS4XY00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS4XY00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS4XY00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection

2019-12-17 Thread Aleksei
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection

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

Bug description:
  [SRU Justification]

  == Impact ==

  An upstream change in v4.11 made xfrm loose memory (8 pages per ipsec 
connection). This was fixed in v5.4 by:
commit 86c6739eda7d "xfrm: Fix memleak on xfrm state destroy"

  == Fix ==

  Pick the upstream fix into all affected series.

  == Testcase ==

  see below

  == Risk of Regression ==

  Low, the change adds a single memory release case in one driver. The
  effect can be verified.

  ---

  Ubuntu linux distro, 4.15.0-62 kernel, server platform.
  This OS is used as an IPSec VPN gateway.  It serves up to several hundred 
concurrent connections

  In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed
  that VPN gateway VMs were running out of physical memory after 12-48
  hours, depending on load.

  Attachments from a server machine in this state in attached leakinfo.txt
  output of free -t
  output of /proc/meminfo in out of memory condition
  output of /slabtop -o -sc
  /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 
hrs and ran out of memory
  Patches for 4.15 and 5.4

  Highlight from page_owner, we can see the leak is a buffer associated
  with the ipsec impelementation.  Each connection leaks 32k of memory
  via alloc_page with order=3

  100960 times:
  Page allocated via order 3, mask 
0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP)
   get_page_from_freelist+0xd64/0x1250
   __alloc_pages_nodemask+0x11c/0x2e0
   alloc_pages_current+0x6a/0xe0
   skb_page_frag_refill+0x71/0x100
   esp_output_head+0x265/0x3e0 [esp4]
   esp_output+0xbc/0x180 [esp4]
   xfrm_output_resume+0x179/0x530
   xfrm_output+0x8e/0x230
   xfrm4_output_finish+0x2b/0x30
   __xfrm4_output+0x3a/0x50
   xfrm4_output+0x43/0xc0
   ip_forward_finish+0x51/0x80
   ip_forward+0x38a/0x480
   ip_rcv_finish+0x122/0x410
   ip_rcv+0x292/0x360
   __netif_receive_skb_core+0x815/0xbd0

  Patch to fix this issue in 4.15 (tested and verified on same server 
exhibiting above leak):
  diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
  index 728272f..7842f83 100644
  --- a/net/xfrm/xfrm_state.c
  +++ b/net/xfrm/xfrm_state.c
  @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x)
  }
  xfrm_dev_state_free(x);
  security_xfrm_state_free(x);
  +
  +   if(x->xfrag.page)
  +   put_page(x->xfrag.page);
  +
  kfree(x);
  }

  Patch for master branch (5.4 I believe) from Paul Wouters
  (p...@nohats.ca)

  diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
  index c6f3c4a1bd99..f3423562d933 100644
  --- a/net/xfrm/xfrm_state.c
  +++ b/net/xfrm/xfrm_state.c
  @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x)
  x->type->destructor(x);
  xfrm_put_type(x->type);
  }
  + if (x->xfrag.page)
  + put_page(x->xfrag.page);
  xfrm_dev_state_free(x);
  security_xfrm_state_free(x);
  xfrm_state_free(x);

  Severity:  Critical - we are unable to use any kernel later than 4.11,
  and are sticking with 4.4 in production.

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

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


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

2019-12-17 Thread 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/1856813

Title:
  Touchpad on X1 Carbon G6 is slow and sloppy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on X1 Carbon G6 is slow and sloppy

  Because:
  [2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 
PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not 
used, you might want to try setting psmouse.synaptics_intertouch to 1 and 
report this to linux-in...@vger.kernel.org.

  Adding kernel parameter psmouse.synaptics_intertouch=1 indeed fixes
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 18 14:09:51 2019
  InstallationDate: Installed on 2019-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20KGS4XY00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=204dc145-c221-45e3-99f4-45107dc1b8d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS4XY00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS4XY00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS4XY00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS4XY00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1856813] [NEW] Touchpad on X1 Carbon G6 is slow and sloppy

2019-12-17 Thread Daniel van Vugt
Public bug reported:

Touchpad on X1 Carbon G6 is slow and sloppy

Because:
[2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 PNP0f13) 
says it can support a different bus. If i2c-hid and hid-rmi are not used, you 
might want to try setting psmouse.synaptics_intertouch to 1 and report this to 
linux-in...@vger.kernel.org.

Adding kernel parameter psmouse.synaptics_intertouch=1 indeed fixes it.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Wed Dec 18 14:09:51 2019
InstallationDate: Installed on 2019-12-18 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20KGS4XY00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=204dc145-c221-45e3-99f4-45107dc1b8d9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-24-generic N/A
 linux-backports-modules-5.3.0-24-generic  N/A
 linux-firmware1.183.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET68W (1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KGS4XY00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS4XY00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS4XY00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KGS4XY00
dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug eoan performance

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

Title:
  Touchpad on X1 Carbon G6 is slow and sloppy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on X1 Carbon G6 is slow and sloppy

  Because:
  [2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 
PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not 
used, you might want to try setting psmouse.synaptics_intertouch to 1 and 
report this to linux-in...@vger.kernel.org.

  Adding kernel parameter psmouse.synaptics_intertouch=1 indeed fixes
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 18 14:09:51 2019
  InstallationDate: Installed on 2019-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20KGS4XY00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=204dc145-c221-45e3-99f4-45107dc1b8d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS4XY00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS4XY00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS4XY00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS4XY00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 

[Kernel-packages] [Bug 1856813] Re: Touchpad on X1 Carbon G6 is slow and sloppy

2019-12-17 Thread Daniel van Vugt
Here's the upstream fix:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.4=2a8e38a8b9b7fcce4b0b0bc7ca4f2d74cc7c1529

Mine is a LEN0091 but we should make sure we also have the fix for
LEN0092.

** Tags added: performance

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

Title:
  Touchpad on X1 Carbon G6 is slow and sloppy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad on X1 Carbon G6 is slow and sloppy

  Because:
  [2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 
PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not 
used, you might want to try setting psmouse.synaptics_intertouch to 1 and 
report this to linux-in...@vger.kernel.org.

  Adding kernel parameter psmouse.synaptics_intertouch=1 indeed fixes
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-24-generic 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Dec 18 14:09:51 2019
  InstallationDate: Installed on 2019-12-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20KGS4XY00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=204dc145-c221-45e3-99f4-45107dc1b8d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS4XY00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS4XY00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS4XY00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS4XY00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1799066] Re: Trackpoint/trackpad unusable when trying to install 18.10 on X1 Carbon 6th

2019-12-17 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.

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

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Trackpoint/trackpad unusable when trying to install 18.10 on X1 Carbon
  6th

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  When running the live CD iso from a USB stick on Lenovo X1 Carbon 6th,
  both the trackpad and trackpoint are unresponsive.

  xinput reports what seems to be proper input devices:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 Elan TrackPoint  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=10   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=12   [slave  
keyboard (3)]

  After some time of swiping my finger on the trackpad and trying to use
  the trackpoint, they sometimes start working. The xinput output is
  then slighly different:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ PS/2 Generic Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=10   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=12   [slave  
keyboard (3)]

  I will include the dmesg output in the comment. I will also see if
  trackpad and trackpoint survive a suspend (which is an issue in
  18.04). I assume it's still an issue, even with 18.10's kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2224 F pulseaudio
  CasperVersion: 1.399
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 16:07:43 2018
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 05:08 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   prepare-package: Ongoing -- {} package not yet fully built
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  replaces: bug 1854762
  trackers:
eoan/linux/pc-kernel: bug 1856805
eoan/linux/pc-lowlatency-kernel: bug 1856806
  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/1856807

Title:
  eoan/linux: 5.3.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 05:08 UTC
  reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  replaces: bug 1854762
  trackers:
eoan/linux/pc-kernel: bug 1856805
eoan/linux/pc-lowlatency-kernel: bug 1856806
  variant: debs

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

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


[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

2019-12-17 Thread 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 17:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  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/1854808

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 17:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

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

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


[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

2019-12-17 Thread Khaled El Mously
** Changed in: linux-restricted-modules (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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


[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ packages:
+   lrm: linux-restricted-modules
+   main: linux
+   meta: linux-meta
+   signed: linux-signed
+ phase: Packaging
+ phase-changed: Wednesday, 18. December 2019 05:08 UTC
+ reason:
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1854762
+ trackers:
+   eoan/linux/pc-kernel: bug 1856805
+   eoan/linux/pc-lowlatency-kernel: bug 1856806
  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/1856807

Title:
  eoan/linux: 5.3.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Eoan:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 05:08 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1854762
  trackers:
eoan/linux/pc-kernel: bug 1856805
eoan/linux/pc-lowlatency-kernel: bug 1856806
  variant: debs

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

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


[Kernel-packages] [Bug 1856807] [NEW] eoan/linux: 5.3.0-26.28 -proposed tracker

2019-12-17 Thread Khaled El Mously
Public bug reported:

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 --
packages:
  lrm: linux-restricted-modules
  main: linux
  meta: linux-meta
  signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 18. December 2019 05:08 UTC
reason:
  prepare-package: Pending -- package not yet uploaded
  prepare-package-lrm: Pending -- package not yet uploaded
  prepare-package-meta: Pending -- package not yet uploaded
  prepare-package-signed: Pending -- package not yet uploaded
replaces: bug 1854762
trackers:
  eoan/linux/pc-kernel: bug 1856805
  eoan/linux/pc-lowlatency-kernel: bug 1856806
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-lrm
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Status: Confirmed


** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.12.02-9

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lrm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: eoan kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => 

[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 04:06 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   prepare-package: Ongoing -- {} package not yet fully built
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
+   xenial/linux-hwe: bug 1856804
  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/1856749

Title:
  bionic/linux: 4.15.0-74.83 -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 04:06 UTC
  reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
xenial/linux-hwe: bug 1856804
  variant: debs

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

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


[Kernel-packages] [Bug 1854207] Re: Unrevert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2"

2019-12-17 Thread 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/1854207

Title:
  Unrevert "arm64: Use firmware to detect CPUs that are not affected by
  Spectre-v2"

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

Bug description:
  We reverted a couple changes in 4.15.0-72.81 because they were causing
  a regression (bug 1853326) that was not understood at press time:

  b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"
  5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not 
affected by Spectre-v2"

  This bug is to track the reapplication of these patches, once we've
  figured out the underlying issue.

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

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


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

2019-12-17 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

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

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

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

  Test Case: See comment #15.

  ---

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1855059] Re: [Regression] 4.15.0-73.82 Can not boot ThunderX

2019-12-17 Thread 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/1855059

Title:
  [Regression] 4.15.0-73.82 Can not boot ThunderX

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

Bug description:
  On ThunderX 1socket system. The kernel output log

  https://pastebin.ubuntu.com/p/35DGgPz5N4/

  On ThunderX 2socket system, The kernel output log

  https://pastebin.ubuntu.com/p/T3fVzwxhmt/

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

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


[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2019-12-17 Thread Lucas Zanella
Hi trong luu, for me the error happened every day, which is why I ended
up using Qubes. It's the only way that I could find except for Windows

You can try older kernels but it didn't work for me. Remember that
downloading older ubuntus will still give you a recent kernel, you have
to downgrade by yourself. However ni Ubuntu or Debian kernels fixed the
problem for me

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: 

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

2019-12-17 Thread trong luu
The error still happens.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=0ca062da-7e8f-425a-88b1-1f784fb40346 ro quiet 

[Kernel-packages] [Bug 1856077] Re: Fix latency issue on Realtek Bluetooth

2019-12-17 Thread Woodrow Shen
After installing linux-oem-osp1 (5.0.0-1033.38) bionic in -proposed and
linux-firmware (1.173.14) bionic in -proposed, the test result is good
for me.

** Tags added: verification-done-bionic

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

Title:
  Fix latency issue on Realtek Bluetooth

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  When multiple Bluetooth devices are connected to Realtek Bluetooth 
controller, the BT latency becomes really high, e.g. audio stutters, mouse lags.

  [Fix]
  The new Realtek Bluetooth firmware can fix the issue.

  [Test]
  Cold boot the system to reload the new firmware, and the issue is gone.

  [Regression Potential]
  Low. The firmware is already in Eoan. We also tested it on Bionic and haven't 
found any regression so far.

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

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


[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Packaging
- phase-changed: Tuesday, 17. December 2019 19:22 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 18. December 2019 04:06 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
  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/1856749

Title:
  bionic/linux: 4.15.0-74.83 -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 04:06 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
  variant: debs

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

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


[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -proposed tracker

2019-12-17 Thread Khaled El Mously
** Summary changed:

- bionic/linux:  -proposed tracker
+ bionic/linux: 4.15.0-74.83 -proposed tracker

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

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

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

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

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

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

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

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

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

Title:
  bionic/linux: 4.15.0-74.83 -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 04:06 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
  variant: debs

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

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


[Kernel-packages] [Bug 1854680] Re: Wireless mouse stops working after closing lid and using external monitor

2019-12-17 Thread Alexander Biniam
If I remove the evdi or DisplayLink driver then the dock won't work. I
began using this dock and laptop almost 3 months ago with no issues so I
am not use what happened. Also, I tried removing and reinstall the
driver with no success. The weird thing is the bluetooth keyboard works
but the mouse doesn't.

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

Title:
  Wireless mouse stops working after closing lid and using external
  monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Lenovo Thinkpad i7 runs Ubuntu 5.3.0-23 with ease however I noticed
  that when I close the lid on my computer all usb mouses act up (new or
  old). After the lid is closed the mouse seems to "pressed" thus not
  working as normal -- oddly the same keyboard or any keyboard is fine
  though.

  I have uploaded the two log files in addition to a desktop screen-
  record of how the mouse acts up when I used it after and before
  closing the lid.

  Docking Station: Dell D3100
  Monitors: 3 Dell U2415

  Ubuntu kernel 5.3.0-23
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexander  12914 F pulseaudio
   /dev/snd/controlC0:  alexander  12914 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux Mint 19.2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-11-09 (32 days ago)
  InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190729
  MachineType: LENOVO 2355CE9
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.173.12
  Tags:  tina
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETB5WW (2.75 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2355CE9
  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:bvrG7ETB5WW(2.75):bd06/10/2019:svnLENOVO:pn2355CE9:pvrThinkPadT430s:rvnLENOVO:rn2355CE9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2355CE9
  dmi.product.sku: LENOVO_MT_2355
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)

2019-12-17 Thread Cyrus Lien
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840239/comments/17

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

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

Title:
  System won't enter suspend after idle over 20 minutes (TSC unstable)

Status in OEM Priority Project:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released

Bug description:
  Summary: System won't enter suspend after idle over 20 minutes

  Steps to reproduce:
  1. install manifest and boot into OS
  2. idle system for 20 mins

  Expected result:
  System could enter suspend after idle over 20 minutes

  Actual result:
  System won't enter suspend after idle over 20 minutes

  Failure rate: 3/3

  Dmesg:
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: 
timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the 
skew is too large:
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' 
wd_now: e336cfbb wd_last: e2e9b5c5 mask: 
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' 
cs_now: 6299ac5acc cs_last: 6250285866 mask: 
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC 
unstable due to clocksource watchdog
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable 
after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking 
unstable (158972862012, 149405080)<-(159105581047, 17903053)
  Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched 
to clocksource hpet

  Upstream bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=203183
  lkml patch:
  https://lkml.org/lkml/2019/4/10/167

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1839818/+subscriptions

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


[Kernel-packages] [Bug 1856103] Re: [CML] New device IDs for CMP-V

2019-12-17 Thread quanxian
** Description changed:

  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.
  
  ControllerIn intel-next   Kernel Version  Commit  Approved to be
  published Comments
- GPIO  
+ GPIO
  SPI NOR   0xa3a4
- NPK   0xa3a6
+ NPK   0xa3a6   e4de2a5d51f9
  HS UART   0xa3a7 0xa3a8 0xa3e6
  SPI   0xa3a9 0xa3aa
  I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3
  SMBus 0xa3a3
  
  Target Kernel: 5.5
  Target Release: 20.04

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

Title:
  [CML] New device IDs for CMP-V

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

Bug description:
  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.

  ControllerIn intel-next   Kernel Version  Commit  Approved to be
  published Comments
  GPIO
  SPI NOR   0xa3a4
  NPK   0xa3a6   e4de2a5d51f9
  HS UART   0xa3a7 0xa3a8 0xa3e6
  SPI   0xa3a9 0xa3aa
  I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3
  SMBus 0xa3a3

  Target Kernel: 5.5
  Target Release: 20.04

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

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


[Kernel-packages] [Bug 1856507] Re: [nvidia] Login screen doesn't show up after installing the Nvidia driver, on a desktop with only an Nvidia GPU

2019-12-17 Thread Daniel van Vugt
Thanks. This appears likely to be the problem; the Nvidia driver can't
find a monitor!?

Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): Validated MetaModes:
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): "NULL"
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): Virtual screen size determined to be 640 x 480
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (WW) 
NVIDIA(0): Unable to get display device for DPI computation.
...
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): Setting mode "NULL"


** No longer affects: gdm3 (Ubuntu)

** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: Incomplete => New

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

Title:
  [nvidia] Login screen doesn't show up after installing the Nvidia
  driver, on a desktop with only an Nvidia GPU

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  Attempting to boot after installing nvidia-driver-435, the login
  screen does not show up.

  I tried editing /etc/gdm3/custom.conf and uncommenting the line:

#WaylandEnable=false

  And then rebooting. No apparent change. Still no login screen.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-driver-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 10:46:58 2019
  InstallationDate: Installed on 2010-10-12 (3351 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: nvidia-graphics-drivers-435
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (53 days ago)

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

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


[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

2019-12-17 Thread Kedar Patankar
@Norbert

The "deep" mem_sleep approach works for me. I also downgraded to
vanialla 19.10 kernel before trying this. Not sure if it also works with
5.4 kernel. Will try this weekend.

Earlier I was making a mistake in writing "deep" into mem_sleep. Just
sudo echo deep > /sys/power/mem_sleep does not work. I had to get a
superuser shell by "sudo su" first and then do the rest. After
correcting this, the laptop works perfectly and I am super happy with
this sweet machine.

WIll also try the 5.5rc1 kernel this weekend & report back.

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1856694] Re: my touchpad is not working since last software update

2019-12-17 Thread Chris Guiver
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798

** This bug has been marked a duplicate of bug 1854798
   Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

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

Title:
  my touchpad is not working since last software update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my touchpad is not working since last update. it just freezes on
  startup.the touchpad works fine on windows

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  naman  1389 F pulseaudio
   /dev/snd/controlC0:  naman  1389 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 17:47:40 2019
  HibernationDevice: RESUME=UUID=53cdac06-44c5-49ba-aa07-20b890659c5c
  InstallationDate: Installed on 2019-01-31 (320 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Vostro 3446
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=ce44f511-99b3-48a0-b2c5-391868309035 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0JKRPT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3446
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1854784] Re: disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- 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/1854784

Title:
  disco/linux-snapdragon: 5.0.0-1028.30 -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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1854788
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1854796] Re: bionic/linux-snapdragon: 4.15.0-1070.77 -proposed tracker

2019-12-17 Thread Gavin Lin
Hardware Certification have begun testing this -proposed kernel.

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 15:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1854795
  variant: debs

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

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


[Kernel-packages] [Bug 1854831] Re: xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

2019-12-17 Thread Gavin Lin
Hardware Certification have begun testing this -proposed kernel.

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

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

Title:
  xenial/linux-snapdragon: 4.4.0-1131.139 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 15:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1854830
  variant: debs

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

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


[Kernel-packages] [Bug 1854784] Re: disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker

2019-12-17 Thread Gavin Lin
Image is not ready.

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

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

Title:
  disco/linux-snapdragon: 5.0.0-1028.30 -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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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: 1854788
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 17. December 2019 21:07 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
  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/1856701

Title:
  focal/linux: 5.4.0-9.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 17. December 2019 21:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1854793] Re: bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker

2019-12-17 Thread 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Tuesday, 03. December 2019 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1854792
unknown/unknown: bug 1854792
  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/1854793

Title:
  bionic/linux-raspi2: 4.15.0-1053.57 -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:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Tuesday, 03. December 2019 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1854792
unknown/unknown: bug 1854792
  variant: debs

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

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


[Kernel-packages] [Bug 1854774] Re: bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854777
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1854773
  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/1854774

Title:
  bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854777
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1854773
  variant: debs

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

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


[Kernel-packages] [Bug 1854826] Re: xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 15:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- 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/1854826

Title:
  xenial/linux-kvm: 4.4.0-1064.71 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 15:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1854770] Re: bionic/linux-azure: 5.0.0-1028.30~18.04.1 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854771
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 06. December 2019 22:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1854769
  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/1854770

Title:
  bionic/linux-azure: 5.0.0-1028.30~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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:
  In Progress
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:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854771
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 06. December 2019 22:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure/azure-kernel: bug 1854769
  variant: debs

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

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


[Kernel-packages] [Bug 1854805] Re: bionic/linux-kvm: 4.15.0-1052.52 -proposed tracker

2019-12-17 Thread 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 05. December 2019 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- 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/1854805

Title:
  bionic/linux-kvm: 4.15.0-1052.52 -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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 05. December 2019 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1854816] Re: xenial/linux-gcp: 4.15.0-1051.54 -proposed tracker

2019-12-17 Thread 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1854814
xenial/linux-gcp/gke-kernel: bug 1854815
  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/1854816

Title:
  xenial/linux-gcp: 4.15.0-1051.54 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1854814
xenial/linux-gcp/gke-kernel: bug 1854815
  variant: debs

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

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


[Kernel-packages] [Bug 1854797] Re: bionic/linux-oem: 4.15.0-1066.76 -proposed tracker

2019-12-17 Thread 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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Friday, 06. December 2019 22:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1854797

Title:
  bionic/linux-oem: 4.15.0-1066.76 -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-lrm 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Friday, 06. December 2019 22:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 17. December 2019 18:56 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 18. December 2019 00:28 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
+   promote-to-proposed: Pending -- ready for review
  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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 18. December 2019 00:28 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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


[Kernel-packages] [Bug 1854835] Re: xenial/linux: 4.4.0-171.200 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1854833
trusty/linux-lts-xenial: bug 1854834
unknown/unknown: bug 1854820
xenial/linux-aws: bug 1854824
xenial/linux-cascade: bug 1854825
xenial/linux-fips: bug 1854832
xenial/linux-kvm: bug 1854826
xenial/linux-raspi2: bug 1854829
xenial/linux-snapdragon: bug 1854831
xenial/linux/caracalla-kernel: bug 1854820
xenial/linux/pc-kernel: bug 1854821
xenial/linux/stlouis-kernel: bug 1854822
  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/1854835

Title:
  xenial/linux: 4.4.0-171.200 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1854833
trusty/linux-lts-xenial: bug 1854834
unknown/unknown: bug 1854820
xenial/linux-aws: bug 1854824
xenial/linux-cascade: bug 1854825
xenial/linux-fips: bug 1854832
xenial/linux-kvm: bug 1854826
xenial/linux-raspi2: bug 1854829
xenial/linux-snapdragon: bug 1854831
xenial/linux/caracalla-kernel: bug 1854820
xenial/linux/pc-kernel: bug 1854821
xenial/linux/stlouis-kernel: bug 1854822
  variant: debs

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

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


[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown

2019-12-17 Thread Guillaume Michaud
I believe this fix causes a regression with NoteBook Fan Control (NBFC) as 
lifting the kernel lockdown was used as a workaround to enable NBFC to control 
fan speed.
See https://github.com/hirschmann/nbfc/issues/414#issuecomment-354274657 and 
https://github.com/hirschmann/nbfc/issues/472 

Would there be another workaround than "simply" disable UEFI secure
boot?

** Bug watch added: github.com/hirschmann/nbfc/issues #414
   https://github.com/hirschmann/nbfc/issues/414

** Bug watch added: github.com/hirschmann/nbfc/issues #472
   https://github.com/hirschmann/nbfc/issues/472

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

Title:
  root can lift kernel lockdown

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification

  Impact: The kernel lockdown support adds a sysrq to allow a physically
  present user to disable lockdown from the keyboard. A bug in the
  implementation makes it possible to also lift lockdown by writing to
  /proc/sysrq-trigger.

  Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
  trigger.

  Test Case: Write "x" to /proc/sysrq-trigger. When working properly
  there should be no messages in dmesg about lifting lockdown, and
  lockdown restrictions (e.g. loading unsigned modules) should remain in
  effect.

  Regression Potential: Anyone using /proc/sysrq-trigger to disable
  lockdown will no longer be able to do so. Implementation bugs could
  prevent use of the sysrq from the keyboard from disabling lockdown,
  but this has been confrimed to still work with the fix in place.

  ---

  Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
  though it shouldn't.

  If I'm not mistaken, kernel lockdown is meant to create a barrier
  between root and the kernel that can only be broken with physical
  access to the system. It is automatically enabled when the system is
  booted with UEFI Secure Boot, which is the case for me.

  This should show the bug:

  # echo "x" > /proc/sysrq-trigger
  Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
  Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from 
userspace.
  Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
  Nov 05 14:58:15 panzersperre kernel: Lifting lockdown

  Note that it first says that the operation is disabled and then performs this 
operation.
  This should only be possible by physically pressing sysrq+x on an attached 
keyboard.

  I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
  I have kernel.sysrq set to 1 - this is important to be able to trigger this 
bug. (But I don't think it disqualifies this issue as non-security relevant 
because root can trivially execute `sysctl kernel.sysrq=1`.)

  I first learned about this by reading a blog post
  (https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
  lifting-the-kernel-lockdown/), so I'm not the first to notice this
  behavior (even though this post doesn't say it's a bug).

  Looking through drivers/tty/sysrq.c, I guess the problem is caused by
  this if condition in __handle_sysrq:

   554   │ /* Ban synthetic events from some sysrq functionality */
   555   │ if ((from == SYSRQ_FROM_PROC || from == 
SYSRQ_FROM_SYNTHETIC) &&
   556   │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
   557   │ printk("This sysrq operation is disabled from 
userspace.\n");
   558   │ /*
   559   │  * Should we check for enabled operations 
(/proc/sysrq-trigger
   560   │  * should not) and is the invoked operation enabled?
   561   │  */
   562   │ if (from == SYSRQ_FROM_KERNEL || 
sysrq_on_mask(op_p->enable_mask)) {
   563   │ pr_cont("%s\n", op_p->action_msg);
   564   │ console_loglevel = orig_log_level;
   565   │ op_p->handler(key);
   566   │ } else {
   567   │ pr_cont("This sysrq operation is disabled.\n");
   568   │ }

  Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
  printk and no change of behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-68-generic 4.15.0-68.77
  ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
  Uname: Linux 4.15.0-68-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niklas 2442 F pulseaudio
   /dev/snd/controlC0:  niklas 2442 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Nov  5 14:58:33 2019
  InstallationDate: 

[Kernel-packages] [Bug 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7

2019-12-17 Thread Jan
Nevermind this bug tracker works differently than github issues :)

(my first bug here as you can probably tell)

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10

2019-12-17 Thread Wayne Schroeder
Just following up to note that this still reproduces (cpu core hang and
backtrace) on Eoan with the backport-iwlwifi-dkms package removed.

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

Title:
  Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating from 18.04 to 19.10, the entire system will freeze and
  eventually recover with many dmesg errors with backtraces and all
  sorts of errors around the iwlwifi module.  I eventually restored to
  an 18.04 backup, but not before logging a lot of information and also
  validating that it reproduces with the 19.10 "Try Ubuntu" from the
  iso, so it certainly isn't an artifact of the upgrade (although
  ubuntu-drivers does appear a bit confused about iwlwifi when I did an
  upgrade, but that appears to be unrelated).

  It is worth noting that I also use the bluetooth module in this card,
  but it is connected via a cable to an internal USB 2 header to the
  system board and I believe it uses another driver entirely.

  I have additional external drives I can install test bed systems on to
  test fixes if need be, but it is worth noting that this is rock solid
  on 18.04.3 and the issue will reproduce within 15 minutes of watching
  youtube videos on 19.10.

  DMESG output from start of issues is attached.

  Wayne
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. Z97-HD3
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


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

2019-12-17 Thread Jamie Redmond
Happening to me too. Full details available on this issue:
https://github.com/brave/brave-browser/issues/7439

** Bug watch added: github.com/brave/brave-browser/issues #7439
   https://github.com/brave/brave-browser/issues/7439

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1785207] Re: openat03 in ubuntu_ltp_syscall failed with Trusty

2019-12-17 Thread Sean Feole
4.15.0-1066.71~14.04.1  linux-azure

9384.   12/14 04:45:22 DEBUG| utils:0153| [stdout] startup='Sat Dec 14 04:00:32 
2019'
9385.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : creating 
a file with O_TMPFILE flag
9386.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : writing 
data to the file
9387.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : file size 
is '4096'
9388.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : looking 
for the file in '.'
9389.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : file not 
found, OK
9390.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : renaming 
'/tmp/ltp-AU7RWwSEJ6/opeERQyaw/#272670 (deleted)' -> 'tmpfile'
9391.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : found a 
file: tmpfile
9392.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 1 TPASS : single 
file tests passed
9393.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : create 
files in multiple directories
9394.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : removing 
test directories
9395.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : 
writing/reading temporary files
9396.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : closing 
temporary files
9397.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 2 TPASS : multiple 
files tests passed
9398.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : create 
multiple directories, link files into them
9399.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 0 TINFO : and check 
file permissions
9400.   12/14 04:45:22 DEBUG| utils:0153| [stdout] openat03 3 TFAIL : 
openat03.c:223: file mode read 0, but expected 
9401.   12/14 04:45:22 DEBUG| utils:0153| [stdout] tag=openat03 
stime=1576296032 dur=0 exit=exited stat=1 core=no cu=0 cs=1
9402.   12/14 04:45:22 DEBUG| utils:0153| [stdout] startup='Sat Dec 14 04:00:34 
2019'

** Tags added: sru-20191202

** Changed in: ubuntu-kernel-tests
   Status: Confirmed => Triaged

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

Title:
  openat03 in ubuntu_ltp_syscall failed with Trusty

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  <<>>
  tag=openat03 stime=1533289807
  cmdline="openat03"
  contacts=""
  analysis=exit
  <<>>
  openat030  TINFO  :  creating a file with O_TMPFILE flag
  incrementing stop
  openat030  TINFO  :  writing data to the file
  openat030  TINFO  :  file size is '4096'
  openat030  TINFO  :  looking for the file in '.'
  openat030  TINFO  :  file not found, OK
  openat030  TINFO  :  renaming '/tmp/ltp-5saSOZV2Gx/opea7u155/#286254 
(deleted)' -> 'tmpfile'
  openat030  TINFO  :  found a file: tmpfile
  openat031  TPASS  :  single file tests passed
  openat030  TINFO  :  create files in multiple directories
  openat030  TINFO  :  removing test directories
  openat030  TINFO  :  writing/reading temporary files
  openat030  TINFO  :  closing temporary files
  openat032  TPASS  :  multiple files tests passed
  openat030  TINFO  :  create multiple directories, link files into them
  openat030  TINFO  :  and check file permissions
  openat033  TFAIL  :  openat03.c:223: file mode read 0, but expected 
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-153-generic 3.13.0-153.203
  ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-153-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  3 07:50 seq
   crw-rw 1 root audio 116, 33 Aug  3 07:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Aug  3 09:49:41 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic 
root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-153-generic N/A
   linux-backports-modules-3.13.0-153-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1813878] Re: lxc test failed on Azure T-4.15

2019-12-17 Thread Sean Feole
** Changed in: ubuntu-kernel-tests
   Status: New => Triaged

** Tags added: sru-20191202

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

Title:
  lxc test failed on Azure T-4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  There are multiple failures in the lxc test for Azure T-4.15

   FAIL: lxc-tests: /usr/bin/lxc-test-autostart
   FAIL: lxc-tests: /usr/bin/lxc-test-cgpath
   FAIL: lxc-tests: /usr/bin/lxc-test-concurrent
   FAIL: lxc-tests: /usr/bin/lxc-test-createtest
   FAIL: lxc-tests: /usr/bin/lxc-test-destroytest
   FAIL: lxc-tests: /usr/bin/lxc-test-device-add-remove
   FAIL: lxc-tests: /usr/bin/lxc-test-ubuntu
   FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
   FAIL: lxc-tests: /usr/bin/lxc-test-usernic
   FAIL: python3: API

  * lxc-test-autostart
   ---
   Setting up the GPG keyring
   Downloading the image index
   Downloading the rootfs
   Downloading the metadata
   The image cache is now ready
   Unpacking the rootfs
   
   ---
   You just created an Ubuntu trusty amd64 (20190129_07:43) container.
   
   To enable SSH, run: apt install openssh-server
   No default root or user password are set by LXC.
   Error starting container: lxc-test-auto
   Container didn't start
   FAIL

  * lxc-test-cgpath
   setting root password to "root"
   Password for 'root' changed
   cgpath.c:69 lxc_cmd_get_cgroup_path returned NULL
   lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container 
"lxctest1": Operation not permitted.

  
  * lxc-test-concurrent
   Iteration 1/1 maxfd:18
   Executing (create) for 5 containers...
   Executing (start) for 5 containers...
   lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container 
"lxc-test-concurrent-3": Operation not permitted.
   Stopping the container (lxc-test-concurrent-3) failed...
   lxc_container: lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop 
container "lxc-test-concurrent-1": Operation not permitted.
   Stopping the container (lxc-test-concurrent-1) failed...
   lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container 
"lxc-test-concurrent-0": Operation not permitted.
   Stopping the container (lxc-test-concurrent-0) failed...
   thread returned error 1

  * /lxc-test-destroytest
  75: lxctest1 thought it was defined

  * lxc-test-device-add-remove
   lxc_container: lxccontainer.c: add_remove_device_node: 3260 set_cgroup_item 
failed while adding the device node
   Adding /dev/network_latency to the container (device_add_remove_test) 
failed...

  * lxc-test-ubuntu
   lxc-start: lxc_start.c: main: 341 The container failed to start.
   lxc-start: lxc_start.c: main: 343 To get more details, run the container in 
foreground mode.
   lxc-start: lxc_start.c: main: 345 Additional information can be obtained by 
setting the --logfile and --logpriority options.
   Failed starting ubuntu container

  * lxc-test-unpriv
  see bug 1803686

  * lxc-test-usernic
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   /usr/sbin/deluser: The user `usernic-user' does not exist.
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   sent invalidate(passwd) request, exiting
   sent invalidate(group) request, exiting
   Failed to open connection to "unix:path=/sys/fs/cgroup/cgmanager/sock" 
message bus: Failed to connect to socket /sys/fs/cgroup/cgmanager/sock: 
Connection refused
   FAIL

  * python3: API
   Using image from local cache
   Unpacking the rootfs
   
   ---
   You just created an Ubuntu trusty amd64 (20190129_07:43) container.
   
   To enable SSH, run: apt install openssh-server
   No default root or user password are set by LXC.
   Getting instance for 'f13fde32-245e-11e9-8017-000d3a942bc7'
   Creating rootfs using 'download', arch=amd64
   Testing the configuration
   Testing the networking
   Starting the container
   Traceback (most recent call last):
 File "/tmp/tmp.Y8MLapGtid", line 102, in 
   assert(container.init_pid > 1)
   AssertionError

  Please see the attachment for the complete test log

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.15.0-1036-azure 4.15.0-1036.38~14.04.2
  ProcVersionSignature: User Name 4.15.0-1036.38~14.04.2-username 4.15.18
  Uname: Linux 4.15.0-1036-azure x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Jan 30 07:04:25 2019
  SourcePackage: linux-signed-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1855448] Re: focal/linux: 5.4.0-8.11 -proposed tracker

2019-12-17 Thread Seth Forshee
*** This bug is a duplicate of bug 1856701 ***
https://bugs.launchpad.net/bugs/1856701

** This bug has been marked a duplicate of bug 1856701
   focal/linux: 5.4.0-9.12 -proposed tracker

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

Title:
  focal/linux: 5.4.0-8.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 13. December 2019 11:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1803686] Re: lxc-test-unpriv failed with Trusty Azure 4.15

2019-12-17 Thread Sean Feole
*** This bug is a duplicate of bug 1813878 ***
https://bugs.launchpad.net/bugs/1813878

** This bug has been marked a duplicate of bug 1813878
   lxc test failed on Azure T-4.15

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

Title:
  lxc-test-unpriv failed with Trusty Azure 4.15

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-signed-azure package in Ubuntu:
  New

Bug description:
  The overlayfs is complaining about "No such device" here.

  
FAIL: lxc-tests: /usr/bin/lxc-test-unpriv
---
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
/usr/sbin/deluser: The user `lxcunpriv' does not exist.
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu trusty amd64 (20181101_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.
Name:   c1
State:  RUNNING
PID:14280
CPU use:0.32 seconds
BlkIO use:  0 bytes
Memory use: 3.68 MiB
KMem use:   1.77 MiB
Link:   veth0TEM5A
 TX bytes:  0 bytes
 RX bytes:  0 bytes
 Total bytes:   0 bytes
lxc_container: bdev.c: overlayfs_mount: 2320 No such device - overlayfs: 
error mounting /home/lxcunpriv/.local/share/lxc/c1/rootfs onto 
/usr/lib/x86_64-linux-gnu/lxc options 
upperdir=/home/lxcunpriv/.local/share/lxc/c2/delta0,lowerdir=/home/lxcunpriv/.local/share/lxc/c1/rootfs,workdir=/home/lxcunpriv/.local/share/lxc/c2/olwork
clone failed
c2 is not running
c1 is not running
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Removing user `lxcunpriv' ...
Warning: group `lxcunpriv' has no more members.
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
sent invalidate(passwd) request, exiting
sent invalidate(group) request, exiting
Done.
FAIL

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.15.0-1032-azure 4.15.0-1032.33~14.04.2
  ProcVersionSignature: User Name 4.15.0-1032.33~14.04.2-username 4.15.18
  Uname: Linux 4.15.0-1032-azure x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Fri Nov 16 09:27:43 2018
  SourcePackage: linux-signed-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1856202] Re: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1856203
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 13. December 2019 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1856202

Title:
  trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1856203
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 13. December 2019 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1856202] Re: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker

2019-12-17 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  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: 1856203
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 13. December 2019 17:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker

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

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

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

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

** Changed in: kernel-sru-workflow/regression-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
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Tuesday, 17. December 2019 14:11 UTC
+ phase: Testing
+ phase-changed: Tuesday, 17. December 2019 21:07 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
  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/1856701

Title:
  focal/linux: 5.4.0-9.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 17. December 2019 21:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1856583] Re: Focal update: v5.4.3 upstream stable release

2019-12-17 Thread Seth Forshee
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Focal update: v5.4.3 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

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:

     v5.4.3 upstream stable release
     from git://git.kernel.org/

  Linux 5.4.3
  kselftest: Fix NULL INSTALL_PATH for TARGETS runlist
  perf script: Fix invalid LBR/binary mismatch error
  EDAC/ghes: Fix locking and memory barrier issues
  watchdog: aspeed: Fix clock behaviour for ast2600
  drm/mcde: Fix an error handling path in 'mcde_probe()'
  md/raid0: Fix an error message in raid0_make_request()
  cpufreq: imx-cpufreq-dt: Correct i.MX8MN's default speed grade value
  ALSA: hda - Fix pending unsol events at shutdown
  KVM: x86: fix out-of-bounds write in KVM_GET_EMULATED_CPUID (CVE-2019-19332)
  binder: Handle start==NULL in binder_update_page_range()
  binder: Prevent repeated use of ->mmap() via NULL mapping
  binder: Fix race between mmap() and binder_alloc_print_pages()
  Revert "serial/8250: Add support for NI-Serial PXI/PXIe+485 devices"
  vcs: prevent write access to vcsu devices
  thermal: Fix deadlock in thermal thermal_zone_device_check
  iomap: Fix pipe page leakage during splicing
  bdev: Refresh bdev size for disks without partitioning
  bdev: Factor out bdev revalidation into a common helper
  rfkill: allocate static minor
  RDMA/qib: Validate ->show()/store() callbacks before calling them
  can: ucan: fix non-atomic allocation in completion handler
  spi: Fix NULL pointer when setting SPI_CS_HIGH for GPIO CS
  spi: Fix SPI_CS_HIGH setting when using native and GPIO CS
  spi: atmel: Fix CS high support
  spi: stm32-qspi: Fix kernel oops when unbinding driver
  spi: spi-fsl-qspi: Clear TDH bits in FLSHCR register
  crypto: user - fix memory leak in crypto_report
  crypto: ecdh - fix big endian bug in ECC library
  crypto: ccp - fix uninitialized list head
  crypto: geode-aes - switch to skcipher for cbc(aes) fallback
  crypto: af_alg - cast ki_complete ternary op to int
  crypto: atmel-aes - Fix IV handling when req->nbytes < ivsize
  crypto: crypto4xx - fix double-free in crypto4xx_destroy_sdr
  KVM: x86: Grab KVM's srcu lock when setting nested state
  KVM: x86: Remove a spurious export of a static function
  KVM: x86: fix presentation of TSX feature in ARCH_CAPABILITIES
  KVM: x86: do not modify masked bits of shared MSRs
  KVM: arm/arm64: vgic: Don't rely on the wrong pending table
  KVM: nVMX: Always write vmcs02.GUEST_CR3 during nested VM-Enter
  KVM: PPC: Book3S HV: XIVE: Set kvm->arch.xive when VPs are allocated
  KVM: PPC: Book3S HV: XIVE: Fix potential page leak on error path
  KVM: PPC: Book3S HV: XIVE: Free previous EQ page when setting up a new one
  arm64: dts: exynos: Revert "Remove unneeded address space mapping for soc 
node"
  arm64: Validate tagged addresses in access_ok() called from kernel threads
  drm/i810: Prevent underflow in ioctl
  drm: damage_helper: Fix race checking plane->state->fb
  drm/msm: fix memleak on release
  jbd2: Fix possible overflow in jbd2_log_space_left()
  kernfs: fix ino wrap-around detection
  nfsd: restore NFSv3 ACL support
  nfsd: Ensure CLONE persists data and metadata changes to the target file
  can: slcan: Fix use-after-free Read in slcan_open
  tty: vt: keyboard: reject invalid keycodes
  CIFS: Fix SMB2 oplock break processing
  CIFS: Fix NULL-pointer dereference in smb2_push_mandatory_locks
  x86/mm/32: Sync only to VMALLOC_END in vmalloc_sync_all()
  media: rc: mark input device as pointing stick
  Input: Fix memory leak in psxpad_spi_probe
  coresight: etm4x: Fix input validation for sysfs.
  Input: goodix - add upside-down quirk for Teclast X89 tablet
  Input: synaptics-rmi4 - don't increment rmiaddr for SMBus transfers
  Input: synaptics-rmi4 - re-enable IRQs in f34v7_do_reflash
  Input: synaptics - switch another X1 Carbon 6 to RMI/SMbus
  soc: mediatek: cmdq: fixup wrong input order of write api
  ALSA: hda: Modify stream stripe mask only when needed
  ALSA: hda - Add mute led support for HP ProBook 645 G4
  ALSA: pcm: oss: Avoid potential buffer overflows
  ALSA: hda/realtek - Fix inverted bass GPIO pin on Acer 8951G
  ALSA: hda/realtek - Enable the headset-mic on a Xiaomi's laptop
  ALSA: hda/realtek - Enable internal speaker of ASUS 

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

2019-12-17 Thread Seth Forshee
I don't think any updates to nvidia-graphics-drivers-435 are necessary.
I don't know whether ubuntu-drivers-common needs to be updated.

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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


[Kernel-packages] [Bug 1727290] Re: ubuntu_unionmount_overlayfs_suite failed on Azure

2019-12-17 Thread Sean Feole
marking fix released On 8/21/2019, the git repo was updated for this
test. It properly uses the upstream version now. Since then this test
has been passing on Azure.

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

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Fix Released

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

Title:
  ubuntu_unionmount_overlayfs_suite failed on Azure

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released

Bug description:
  Kernel 4.15.0-1022.23 azure
  This test has failed on all the azure instances this cycle, it looks like it 
has stopped at the "rename-empty-dir" test:

TEST rename-file.py:110: Rename file over a dir
./run --rename /mnt/a/foo108/ /mnt/a/empty108/ -E ENOTDIR
./run --rename /mnt/a/foo108/ /mnt/a/dir108/ -E ENOTDIR
./run --open-file /mnt/a/foo108/ -r -R :xxx:yyy:zzz -E ENOTDIR
TEST rename-file.py:121: Rename file over parent dir
./run --rename /mnt/a/foo109/ /mnt/a -E ENOTDIR
./run --open-file /mnt/a/foo109/ -r -R :xxx:yyy:zzz -E ENOTDIR
***
*** ./run --ov --ts=0 rename-empty-dir
***
TEST rename-empty-dir.py:10: Rename empty dir and rename back
./run --rename /mnt/a/empty100 /mnt/a/no_dir100 -E EXDEV
/mnt/a/empty100: Expected error (Invalid cross-device link) was not 
produced

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

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


[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip

2019-12-17 Thread Matt Zuba
I had this problem occur recently and was able to work with one of my
System Administrators to narrow it down.  I saw the floppy text in the
output so I asked my Sys Admin to connect the Floppy Drive in VCenter to
the VMs that were having this issue (3 new 18.04 installs) and the issue
is now resolved on all of them.  blkid, mdadm, nor fdisk hang anymore;
they all work as they should.  Not sure where the issue exactly lies,
but connecting a floppy helped resolve it for now.  I have a lot of
other 16.04 servers that do not have this issue, for what it's worth.

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

Title:
  mdadm, mkfs, other io commands hang, stuck task, bad rip

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  1. disco
  2. # apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
   *** 5.0.0.13.14 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3. installation completes sucessfully
  4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the kernel throws an 
oops and bad rip value.

  [  967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds.
  [  967.811787]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.815500] mdadm   D0 12213  12207 0x
  [  967.815503] Call Trace:
  [  967.815509]  __schedule+0x2d0/0x840
  [  967.815511]  ? __switch_to_asm+0x40/0x70
  [  967.815512]  ? __switch_to_asm+0x34/0x70
  [  967.815514]  schedule+0x2c/0x70
  [  967.815516]  schedule_preempt_disabled+0xe/0x10
  [  967.815518]  __mutex_lock.isra.10+0x2e4/0x4c0
  [  967.815522]  ? exact_lock+0x11/0x20
  [  967.815524]  __mutex_lock_slowpath+0x13/0x20
  [  967.815528]  mutex_lock+0x2c/0x30
  [  967.815530]  __blkdev_get+0x7b/0x550
  [  967.815532]  ? bd_acquire+0xd0/0xd0
  [  967.815533]  blkdev_get+0x10c/0x330
  [  967.815535]  ? bd_acquire+0xd0/0xd0
  [  967.815537]  blkdev_open+0x92/0x100
  [  967.815539]  do_dentry_open+0x143/0x3a0
  [  967.815540]  vfs_open+0x2d/0x30
  [  967.815542]  path_openat+0x2d4/0x16d0
  [  967.815547]  ? put_device+0x17/0x20
  [  967.815552]  ? scsi_device_put+0x2b/0x30
  [  967.815553]  do_filp_open+0x93/0x100
  [  967.81]  ? strncpy_from_user+0x56/0x1b0
  [  967.815558]  ? __alloc_fd+0x46/0x140
  [  967.815560]  do_sys_open+0x177/0x280
  [  967.815561]  ? _cond_resched+0x19/0x30
  [  967.815563]  __x64_sys_openat+0x20/0x30
  [  967.815566]  do_syscall_64+0x5a/0x110
  [  967.815567]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.815568] RIP: 0033:0x7faa36406cce
  [  967.815572] Code: Bad RIP value.
  [  967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 
0101
  [  967.815574] RAX: ffda RBX: 4000 RCX: 
7faa36406cce
  [  967.815575] RDX: 4000 RSI: 564df70257b0 RDI: 
ff9c
  [  967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: 

  [  967.815576] R10:  R11: 0246 R12: 
7ffedb664240
  [  967.815577] R13:  R14: 0001 R15: 
564df7023e00

  [  967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds.
  [  967.803509]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.810235] mkfs.btrfs  D0  3767   1866 0x
  [  967.810239] Call Trace:
  [  967.810251]  __schedule+0x2d0/0x840
  [  967.810254]  ? __switch_to_asm+0x34/0x70
  [  967.810256]  ? __switch_to_asm+0x40/0x70
  [  967.810258]  schedule+0x2c/0x70
  [  967.810260]  schedule_timeout+0x258/0x360
  [  967.810277]  wait_for_completion+0xb7/0x140
  [  967.810281]  ? wake_up_q+0x80/0x80
  [  967.810293]  __floppy_read_block_0+0x138/0x190 [floppy]
  [  967.810298]  ? floppy_cmos_show+0x30/0x30 [floppy]
  [  967.810302]  floppy_revalidate+0xf8/0x230 [floppy]
  [  967.810307]  check_disk_change+0x62/0x70
  [  967.810309]  floppy_open+0x2ae/0x380 [floppy]
  [  967.810311]  __blkdev_get+0xe5/0x550
  [  967.810313]  ? bd_acquire+0xd0/0xd0
  [  967.810315]  blkdev_get+0x10c/0x330
  [  967.810316]  ? bd_acquire+0xd0/0xd0
  [  967.810318]  blkdev_open+0x92/0x100
  [  967.810321]  do_dentry_open+0x143/0x3a0
  [  967.810323]  vfs_open+0x2d/0x30
  [  967.810326]  path_openat+0x2d4/0x16d0
  [  967.810328]  ? filename_lookup.part.60+0xe0/0x170
  [  967.810332]  ? strncpy_from_user+0x56/0x1b0
  [  967.810333]  do_filp_open+0x93/0x100
  [  967.810353]  ? strncpy_from_user+0x56/0x1b0
  [  967.810358]  ? __alloc_fd+0x46/0x140
  [  967.810360]  

[Kernel-packages] [Bug 1856754] [NEW] Disco update: upstream stable patchset 2019-12-17

2019-12-17 Thread 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-12-17

Ported from the following upstream stable releases:
v4.19.89, v5.3.16

   from git://git.kernel.org/

rsi: release skb if rsi_prepare_beacon fails
arm64: tegra: Fix 'active-low' warning for Jetson TX1 regulator
sparc64: implement ioremap_uc
lp: fix sparc64 LPSETTIMEOUT ioctl
usb: gadget: u_serial: add missing port entry locking
tty: serial: fsl_lpuart: use the sg count from dma_map_sg
tty: serial: msm_serial: Fix flow control
serial: pl011: Fix DMA ->flush_buffer()
serial: serial_core: Perform NULL checks for break_ctl ops
serial: ifx6x60: add missed pm_runtime_disable
autofs: fix a leak in autofs_expire_indirect()
RDMA/hns: Correct the value of HNS_ROCE_HEM_CHUNK_LEN
iwlwifi: pcie: don't consider IV len in A-MSDU
exportfs_decode_fh(): negative pinned may become positive without the parent 
locked
audit_get_nd(): don't unlock parent too early
NFC: nxp-nci: Fix NULL pointer dereference after I2C communication error
xfrm: release device reference for invalid state
Input: cyttsp4_core - fix use after free bug
sched/core: Avoid spurious lock dependencies
perf/core: Consistently fail fork on allocation failures
ALSA: pcm: Fix stream lock usage in snd_pcm_period_elapsed()
drm/sun4i: tcon: Set min division of TCON0_DCLK to 1.
selftests: kvm: fix build with glibc >= 2.30
rsxx: add missed destroy_workqueue calls in remove
net: ep93xx_eth: fix mismatch of request_mem_region in remove
i2c: core: fix use after free in of_i2c_notify
fuse: verify nlink
fuse: verify attributes
ALSA: hda/realtek - Enable internal speaker of ASUS UX431FLC
ALSA: hda/realtek - Enable the headset-mic on a Xiaomi's laptop
ALSA: pcm: oss: Avoid potential buffer overflows
ALSA: hda - Add mute led support for HP ProBook 645 G4
Input: synaptics - switch another X1 Carbon 6 to RMI/SMbus
Input: synaptics-rmi4 - re-enable IRQs in f34v7_do_reflash
Input: synaptics-rmi4 - don't increment rmiaddr for SMBus transfers
Input: goodix - add upside-down quirk for Teclast X89 tablet
coresight: etm4x: Fix input validation for sysfs.
Input: Fix memory leak in psxpad_spi_probe
x86/mm/32: Sync only to VMALLOC_END in vmalloc_sync_all()
CIFS: Fix NULL-pointer dereference in smb2_push_mandatory_locks
CIFS: Fix SMB2 oplock break processing
tty: vt: keyboard: reject invalid keycodes
can: slcan: Fix use-after-free Read in slcan_open
kernfs: fix ino wrap-around detection
jbd2: Fix possible overflow in jbd2_log_space_left()
drm/msm: fix memleak on release
drm/i810: Prevent underflow in ioctl
arm64: dts: exynos: Revert "Remove unneeded address space mapping for soc node"
KVM: arm/arm64: vgic: Don't rely on the wrong pending table
KVM: x86: do not modify masked bits of shared MSRs
KVM: x86: fix presentation of TSX feature in ARCH_CAPABILITIES
KVM: x86: Grab KVM's srcu lock when setting nested state
crypto: crypto4xx - fix double-free in crypto4xx_destroy_sdr
crypto: atmel-aes - Fix IV handling when req->nbytes < ivsize
crypto: af_alg - cast ki_complete ternary op to int
crypto: ccp - fix uninitialized list head
crypto: ecdh - fix big endian bug in ECC library
crypto: user - fix memory leak in crypto_report
spi: atmel: Fix CS high support
mwifiex: update set_mac_address logic
can: ucan: fix non-atomic allocation in completion handler
RDMA/qib: Validate ->show()/store() callbacks before calling them
iomap: Fix pipe page leakage during splicing
thermal: Fix deadlock in thermal thermal_zone_device_check
vcs: prevent write access to vcsu devices
binder: Fix race between mmap() and binder_alloc_print_pages()
binder: Handle start==NULL in binder_update_page_range()
ALSA: hda - Fix pending unsol events at shutdown
watchdog: aspeed: Fix clock behaviour for ast2600
perf script: Fix invalid LBR/binary mismatch error
xfs: add missing error check in xfs_prepare_shift()
KVM: x86: fix out-of-bounds write in KVM_GET_EMULATED_CPUID (CVE-2019-19332)
net: qrtr: fix memort leak in qrtr_tun_write_iter
appletalk: Fix potential NULL pointer dereference in unregister_snap_client
appletalk: Set error code if register_snap_client failed
time: Zero the upper 32-bits in __kernel_timespec on 32-bit
RDMA/hns: Correct the value of srq_desc_size
ecryptfs: fix unlink and rmdir in face of underlying fs modifications
x86/resctrl: Fix potential lockdep warning
ravb: implement MTU change while device is up
net: hns3: reallocate SSU' buffer size when pfc_en changes
net: hns3: fix ETS bandwidth validation bug
media: rc: mark input device as pointing stick
nfsd: 

[Kernel-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

2019-12-17 Thread Jamie Strandboge
This was fixed upstream in 61c27d8808f0589beb6a319cc04073e8bb32d860

** Changed in: apparmor
   Status: Triaged => 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/1824812

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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


[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 18:56 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
  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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 18:56 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

2019-12-17 Thread Pushpendra Kumar
I am facing same issue while re-connecting to my TunnelBear VPN. TunnelBear VPN 
uses open-vpn service. I have configured VPN as per instructions by TunnelBear. 
And it works fine when connect first time, but after that when choose "Turn 
Off" from Netowrok-Manager then choose "Connect" again, then I see this same 
error. See snapshot from syslog:
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]:   [1576611925.5171] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: state changed: starting (3)
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]:   [1576611925.5172] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN connection: (ConnectInteractive) reply received
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --keysize is DEPRECATED and 
will be removed in OpenVPN 2.6
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: OpenVPN 2.4.4 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 
14 2019
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: library versions: OpenSSL 1.1.1  11 
Sep 2018, LZO 2.08
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --ns-cert-type is 
DEPRECATED.  Use --remote-cert-tls instead.
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link local: (not bound)
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link remote: 
[AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: chroot will be delayed because 
of --client, --pull, or --up-delay
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
Dec 17 20:45:27 KUMAR-PC nm-openvpn[6237]: [9563/server] Peer Connection 
Initiated with [AF_INET]103.228.153.233:443
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Option 'explicit-exit-notify' in 
[PUSH-OPTIONS]:3 is ignored by previous  blocks
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Note: option tun-ipv6 is ignored 
because modern operating systems do not need special IPv6 tun handling anymore.
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: ERROR: Cannot ioctl TUNSETIFF tun0: 
Device or resource busy (errno=16)
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Exiting due to fatal error
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9900] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9901] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9902] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: state changed: stopping (5)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9903] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: state changed: stopped (6)

If someone needs, then I can reproduce this with additional traces. But as much 
I could learn from this problem is that, while "Turn Off" from Netowrk-Manager, 
Network-Manager is not able to stop openvpn process.
If I stop this openvpn process manually, then try to "Connect" from 
Network-Manager menu, it works fine.

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

Title:
  "Activation of network connection failed" popup shows incessantly

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

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 

[Kernel-packages] [Bug 1841313] Re: Asus X451MA does not boot with linux > 4.15.0-55

2019-12-17 Thread Yvan Masson
I am sorry I just saw your message, it seems I have never received a
notification about it, strange.

I don't know yet if I will be able to test this kernel but I will do if
I can.

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

Title:
  Asus X451MA does not boot with linux > 4.15.0-55

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  On an Asus X451MA running Linux Mint 18.3 (Ubuntu 16.04.3), last
  kernel update from 4.15.0-55 to 4.15.0-58 prevents it from booting: it
  hangs at the beginning of boot.

  I tested with kernel 4.15.0-59 from "xenial-proposed" and with a live
  image of Ubuntu 18.04.2 and the issue remains. I could not test with a
  more recent kernel on this same install because it requires libssl1.1
  that is not available in the Xenial repositories. I suppose it does
  not help, but a picture from live Ubuntu 18.04.2 is attached.

  I will provide more information with apport very soon.

  Do not hesitate to ask if I can provide other details or test other
  versions / parameters.

  Regards,
  Yvan
  --- 
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marie-claude   1541 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=d93009cf-a1ab-47ec-811c-d76dfbc4926d
  InstallationDate: Installed on 2017-04-08 (868 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  IwConfig:
   enp3s0f2  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b404 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 04ca:2006 Lite-On Technology Corp. Broadcom 
BCM43142A0 Bluetooth Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X451MA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic 
root=UUID=a34dd005-da91-42c3-95c6-b25185f3ee21 ro intel_idle.max_cstate=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-55-generic N/A
   linux-backports-modules-4.15.0-55-generic  N/A
   linux-firmware 1.157.22
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  sylvia sylvia
  Uname: Linux 4.15.0-55-generic x86_64
  UnreportableReason: Le rapport fait référence à un paquet non installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X451MA.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X451MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX451MA.216:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX451MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X451MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash

2019-12-17 Thread Stephen Warren
** Bug watch added: Debian Bug tracker #946911
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946911

** Also affects: dmidecode (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946911
   Importance: Unknown
   Status: Unknown

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

Title:
  dmidecode causing system crash

Status in dmidecode package in Ubuntu:
  Confirmed
Status in dmidecode package in Debian:
  Unknown

Bug description:
  Please let me know what other information I can provide. Some basic
  info I've captured below.

  root@jetson-0423318029481:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic
  root@jetson-0423318029481:~# uname -a
  Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21 
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
  root@jetson-0423318029481:~# apt-cache madison dmidecode
   dmidecode |  3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main 
arm64 Packages
  root@jetson-0423318029481:~# dmidecode -V
  3.1
  root@jetson-0423318029481:~# strace dmidecode
  execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
  brk(NULL)   = 0x559651a000
  faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
  faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
  mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
  close(3)= 0
  faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0 
\10\2\0\0\0\0\0"..., 832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f8050a000
  mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f80369000
  mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
  mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
  mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
  close(3)= 0
  mprotect(0x7f804b8000, 16384, PROT_READ) = 0
  mprotect(0x55932d9000, 12288, PROT_READ) = 0
  mprotect(0x7f8050e000, 4096, PROT_READ) = 0
  munmap(0x7f804c2000, 130516)= 0
  fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
  brk(NULL)   = 0x559651a000
  brk(0x559653b000)   = 0x559653b000
  write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
  )   = 16
  openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) = 
-1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such 
file or directory)
  openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or 
directory)
  write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry 
point.
  ) = 35
  openat(AT_FDCWD, "/dev/mem", O_RDONLY)  = 3
  fstat(3, 

  # System hangs and reboots here.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dmidecode 3.1-1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 25 12:15:53 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  InstallationDate: Installed on 2019-02-28 (24 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dmidecode
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 18:56 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait
  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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 18:56 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   promote-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/1856701

Title:
  focal/linux: 5.4.0-9.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
promote-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/1856701/+subscriptions

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


[Kernel-packages] [Bug 1856749] Re: bionic/linux: -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Summary changed:

- linux:  -proposed tracker
+ bionic/linux:  -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ packages:
+   lrm: linux-restricted-modules
+   main: linux
+   meta: linux-meta
+   signed: linux-signed
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 17. December 2019 19:22 UTC
+ reason:
+   prepare-package: Pending -- version not specified
  replaces: bug 1854819
+ trackers:
+   bionic/linux/pc-kernel: bug 1856747
+   bionic/linux/pc-lowlatency-kernel: bug 1856748
  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/1856749

Title:
  bionic/linux:  -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Ready for Packaging
  phase-changed: Tuesday, 17. December 2019 19:22 UTC
  reason:
prepare-package: Pending -- version not specified
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
  variant: debs

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

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


[Kernel-packages] [Bug 1856749] [NEW] bionic/linux: -proposed tracker

2019-12-17 Thread Khaled El Mously
Public bug reported:

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 --
packages:
  lrm: linux-restricted-modules
  main: linux
  meta: linux-meta
  signed: linux-signed
phase: Ready for Packaging
phase-changed: Tuesday, 17. December 2019 19:22 UTC
reason:
  prepare-package: Pending -- version not specified
replaces: bug 1854819
trackers:
  bionic/linux/pc-kernel: bug 1856747
  bionic/linux/pc-lowlatency-kernel: bug 1856748
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-lrm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.12.02-8

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lrm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: bionic kernel-release-tracking-bug

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team 

[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04

2019-12-17 Thread Kai-Heng Feng
I think matching exact "Lenovo ideapad S130-11IGM" can avoid regress
other Lenovo systems.

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

Title:
  (Lenovo S130-11IGM) emmc not working in 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and I'll 
happily get any other requested logging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1434 F pulseaudio
  CasperVersion: 1.405
  DistroRelease: Ubuntu 19.04
  IwConfig:
   enp0s21f0u1  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81J1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32802WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S130-11IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM:
  dmi.product.family: ideapad S130-11IGM
  dmi.product.name: 81J1
  dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM
  dmi.product.version: Lenovo ideapad S130-11IGM
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation

2019-12-17 Thread Jamie Strandboge
*** This bug is a duplicate of bug 1848567 ***
https://bugs.launchpad.net/bugs/1848567

I'm going to mark the linux task as Invalid and then mark as a dupe of
bug 1848567

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

** This bug has been marked a duplicate of bug 1848567
   autogenerated per-snap snap-update-ns apparmor profile may contain many 
duplicate mount rules causing excessive parser memory usage

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

Title:
  kernel is out of memory and killed during a kernel sys_write operation

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  This error is being reproduced on i386 arch when using the pc-kernel
  snap from beta or candidate.

  > sudo snap install test-snapd-tools
  > dmesg

  [15131.806107] audit: type=1400 audit(1559585825.240:93): 
apparmor="STATUS" operation="profile_replace" profile="unconfined" 
name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser"
  [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to 
increase size.
  [15131.871614] vmalloc: allocation failure: 68481 bytes
  [15131.871616] apparmor_parser: page allocation failure: order:0, 
mode:0x24000c2
  [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 
4.4.0-150-generic #176-Ubuntu
  [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [15131.871622]  c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 
0001 cfee9e30
  [15131.871625]  c11821b6 c1a1b220 f40ba700  024000c2 cfee9e44 
c1a1ce6c cfee9e18
  [15131.871629]  5ed07e43 00010b81  cfee9e60 c11ba86f 024000c2 
 c1a1ce6c
  [15131.871632] Call Trace:
  [15131.871637]  [] dump_stack+0x58/0x79
  [15131.871640]  [] warn_alloc_failed+0xd6/0x110
  [15131.871643]  [] __vmalloc_node_range+0x1ef/0x210
  [15131.871645]  [] __vmalloc_node+0x66/0x70
  [15131.871648]  [] ? __aa_kvmalloc+0x28/0x60
  [15131.871650]  [] vmalloc+0x38/0x40
  [15131.871652]  [] ? __aa_kvmalloc+0x28/0x60
  [15131.871654]  [] __aa_kvmalloc+0x28/0x60
  [15131.871656]  [] aa_simple_write_to_buffer+0x34/0x90
  [15131.871658]  [] policy_update+0x73/0x230
  [15131.871660]  [] ? security_file_permission+0x3e/0xd0
  [15131.871662]  [] profile_replace+0x98/0xe0
  [15131.871664]  [] ? policy_update+0x230/0x230
  [15131.871666]  [] __vfs_write+0x22/0x50
  [15131.871668]  [] vfs_write+0x8c/0x1b0
  [15131.871669]  [] SyS_write+0x51/0xb0
  [15131.871672]  [] do_fast_syscall_32+0x9f/0x190
  [15131.871675]  [] sysenter_past_esp+0x3d/0x61
  [15131.871676] Mem-Info:
  [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0
  active_file:84472 inactive_file:25195 isolated_file:0
  unevictable:0 dirty:34 writeback:0 unstable:0
  slab_reclaimable:7222 slab_unreclaimable:14030
  mapped:8431 shmem:5785 pagetables:204 bounce:0
  free:289381 free_pcp:659 free_cma:0
  [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB 
active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB 
slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB 
unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [15131.871686] lowmem_reserve[]: 0 834 1942 1942
  [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB 
active_anon:30164kB inactive_anon:2776kB active_file:158404kB 
inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB 
mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB 
kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB 
local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
  [15131.871693] lowmem_reserve[]: 0 0 8863 8863
  [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB 
active_anon:36408kB inactive_anon:5496kB active_file:176764kB 
inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB 
present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB 
mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB 
kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB 
local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
  [15131.871699] lowmem_reserve[]: 0 0 0 0
  [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 

[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
- phase: Packaging
- phase-changed: Thursday, 12. December 2019 19:46 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 17. December 2019 18:56 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 18:56 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait
  variant: debs

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

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


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

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

apport-collect 1856743

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

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

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

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

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

Title:
  Occassional Touchpad  freeze after wake up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It does not always happens. But it did occure once in past 4 days.

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

-- 
Mailing list: https://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 1833617] Re: [amdgpu] screen freeze after suspend

2019-12-17 Thread Meir Levi
Done bug report sentThanksLevi

On Tuesday, December 17, 2019, 1:20:45 AM PST, Kai-Heng Feng 
 wrote:  
 
 Can you please file a new bug report so it can be tracked separately?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1833617

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Eoan:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Screen freeze after S3 on AMD Stoney Ridge.

  [Fix]
  Pin the VRAM so it won't contain garbage data after S3.

  [Test]
  After applying this patch I can confirm the issue is gone on Dell
  Inspiron 3180, a Stoney Ridge laptop.

  [Regression Potential]
  Low. This patch only touched a small subset of amdgpu.

  === Original Bug Report ===
  It's most likely amdgup driver needs an upgrade. Problem occurs since kernel 
upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
     Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  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.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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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/1833617

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Eoan:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Screen freeze after S3 on AMD Stoney Ridge.

  [Fix]
  Pin the VRAM so it won't contain garbage data after S3.

  [Test]
  After applying this patch I can confirm the issue is gone on Dell
  Inspiron 3180, a Stoney Ridge laptop.

  [Regression Potential]
  Low. This patch only touched a small subset of amdgpu.

  === Original Bug Report ===
  It's most likely amdgup driver needs an upgrade. Problem occurs since kernel 
upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
     Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
 

[Kernel-packages] [Bug 1856743] [NEW] Occassional Touchpad freeze after wake up

2019-12-17 Thread Meir Levi
Public bug reported:

It does not always happens. But it did occure once in past 4 days.

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

Title:
  Occassional Touchpad  freeze after wake up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It does not always happens. But it did occure once in past 4 days.

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

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


[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 17:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  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/1854808

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 17:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

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

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


[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

2019-12-17 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -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-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 17:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

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

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


[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed

2019-12-17 Thread Sean Feole
https://lore.kernel.org/kvm/875zkh1830@vitty.brq.redhat.com/

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

Title:
  apic test in kvm-unit-test failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load

2019-12-17 Thread Guilherme G. Piccoli
The kernel commit 9adebac37e7d ("qede: Handle infinite driver spinning
for Tx timestamp.") is present in kernels 5.3 and subsequent ones, and
after some preliminary results from @phausman, seems the commit properly
fixes the issue.

Hence, we will start the SRU process for Bionic/Disco.
Cheers,


Guilherme

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

Title:
  qede driver causes 100% CPU load

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  This bug is similar to #1832082 (bnx2x driver causes 100% CPU load)
  but applies for qede driver instead of bnx2x. The symptoms are the
  same:

  With chrony installed, and configured with "hwtimestamp *", I observe
  100% CPU load on 2 CPU cores.

  Running perf report shows that kernel is busy executing qede_ptp_task
  function in qede driver.

  A workaround is to disable "hwtimestamp *" in chrony configuration.

  ---

  $ modinfo qede
  filename:   
/lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko
  version:8.10.10.21
  license:GPL
  description:QLogic FastLinQ 4 Ethernet Driver
  srcversion: D5EC89D815FC81B973EE9F0
  alias:  pci:v1077d8090sv*sd*bc*sc*i*
  alias:  pci:v1077d8070sv*sd*bc*sc*i*
  alias:  pci:v1077d1664sv*sd*bc*sc*i*
  alias:  pci:v1077d1656sv*sd*bc*sc*i*
  alias:  pci:v1077d1654sv*sd*bc*sc*i*
  alias:  pci:v1077d1644sv*sd*bc*sc*i*
  alias:  pci:v1077d1636sv*sd*bc*sc*i*
  alias:  pci:v1077d1666sv*sd*bc*sc*i*
  alias:  pci:v1077d1634sv*sd*bc*sc*i*
  depends:ptp,qed
  retpoline:  Y
  intree: Y
  name:   qede
  vermagic:   4.15.0-72-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   debug: Default debug msglevel (uint)

  
  $ uname -a
  Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  
  $ lspci | grep -i ether
  19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)
  19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)
  19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)
  19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)

  
  # perf report snippet:

Children  Self  Command  Shared Object
  -   44.76% 0.00%  kworker/16:5 [kernel.kallsyms]
   ret_from_fork
 - kthread
- 44.74% worker_thread
   - 44.57% process_one_work
  - 42.67% qede_ptp_task
 - 38.86% qed_ptp_hw_read_tx_ts
  qed_rd
 - 3.03% queue_work_on
- 2.06% __queue_work
   - 0.68% get_work_pool
  - 0.61% radix_tree_lookup
   __radix_tree_lookup
0.50% set_work_pool_and_clear_pending

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

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


[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load

2019-12-17 Thread Guilherme G. Piccoli
** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => Fix Released

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

Title:
  qede driver causes 100% CPU load

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  This bug is similar to #1832082 (bnx2x driver causes 100% CPU load)
  but applies for qede driver instead of bnx2x. The symptoms are the
  same:

  With chrony installed, and configured with "hwtimestamp *", I observe
  100% CPU load on 2 CPU cores.

  Running perf report shows that kernel is busy executing qede_ptp_task
  function in qede driver.

  A workaround is to disable "hwtimestamp *" in chrony configuration.

  ---

  $ modinfo qede
  filename:   
/lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko
  version:8.10.10.21
  license:GPL
  description:QLogic FastLinQ 4 Ethernet Driver
  srcversion: D5EC89D815FC81B973EE9F0
  alias:  pci:v1077d8090sv*sd*bc*sc*i*
  alias:  pci:v1077d8070sv*sd*bc*sc*i*
  alias:  pci:v1077d1664sv*sd*bc*sc*i*
  alias:  pci:v1077d1656sv*sd*bc*sc*i*
  alias:  pci:v1077d1654sv*sd*bc*sc*i*
  alias:  pci:v1077d1644sv*sd*bc*sc*i*
  alias:  pci:v1077d1636sv*sd*bc*sc*i*
  alias:  pci:v1077d1666sv*sd*bc*sc*i*
  alias:  pci:v1077d1634sv*sd*bc*sc*i*
  depends:ptp,qed
  retpoline:  Y
  intree: Y
  name:   qede
  vermagic:   4.15.0-72-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   debug: Default debug msglevel (uint)

  
  $ uname -a
  Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  
  $ lspci | grep -i ether
  19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)
  19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)
  19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)
  19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 
10/25/40/50GbE Controller (rev 02)

  
  # perf report snippet:

Children  Self  Command  Shared Object
  -   44.76% 0.00%  kworker/16:5 [kernel.kallsyms]
   ret_from_fork
 - kthread
- 44.74% worker_thread
   - 44.57% process_one_work
  - 42.67% qede_ptp_task
 - 38.86% qed_ptp_hw_read_tx_ts
  qed_rd
 - 3.03% queue_work_on
- 2.06% __queue_work
   - 0.68% get_work_pool
  - 0.61% radix_tree_lookup
   __radix_tree_lookup
0.50% set_work_pool_and_clear_pending

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

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


[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Packaging
  phase-changed: Thursday, 12. December 2019 19:46 UTC
  reason:
-   prepare-package: Stalled -- package tag not yet published
prepare-package-meta: Pending -- package not yet uploaded
  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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Packaging
  phase-changed: Thursday, 12. December 2019 19:46 UTC
  reason:
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Pending -- package copied to Proposed signed:queued
  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/1856701

Title:
  focal/linux: 5.4.0-9.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
promote-to-proposed: Pending -- package copied to Proposed signed:queued
  variant: debs

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

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


[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests failed with 4 unexpected failures on D-Oracle

2019-12-17 Thread Sean Feole
Seen on Oracle, SRU 12.12.02   5.0.0-1009.14~18.04.1linux-oracle-5.0

12/06 08:07:38 DEBUG| utils:0116| Running 'kvm-ok'
12/06 08:07:38 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists
12/06 08:07:38 DEBUG| utils:0153| [stdout] KVM acceleration can be used
12/06 08:07:38 DEBUG| utils:0116| Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu'
12/06 08:07:38 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4
12/06 08:07:39 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s 
/usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device 
isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device 
pci-testdev -machine accel=kvm -kernel /tmp/tmp.F8JKNMI5XU -smp 1 -cpu host # 
-initrd /tmp/tmp.35bJmDIgMF
12/06 08:07:39 DEBUG| utils:0153| [stdout] enabling apic
12/06 08:07:39 DEBUG| utils:0153| [stdout] paging enabled
12/06 08:07:39 DEBUG| utils:0153| [stdout] cr0 = 80010011
12/06 08:07:39 DEBUG| utils:0153| [stdout] cr3 = 45a000
12/06 08:07:39 DEBUG| utils:0153| [stdout] cr4 = 20
12/06 08:07:39 DEBUG| utils:0153| [stdout] PMU version: 2
12/06 08:07:39 DEBUG| utils:0153| [stdout] GP counters: 4
12/06 08:07:39 DEBUG| utils:0153| [stdout] GP counter width:48
12/06 08:07:39 DEBUG| utils:0153| [stdout] Mask length: 7
12/06 08:07:39 DEBUG| utils:0153| [stdout] Fixed counters:  3
12/06 08:07:39 DEBUG| utils:0153| [stdout] Fixed counter width: 48
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: core cycles-0
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: core cycles-1
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: core cycles-2
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: core cycles-3
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: instructions-0
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: instructions-1
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: instructions-2
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: instructions-3
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: ref cycles-0
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: ref cycles-1
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: ref cycles-2
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: ref cycles-3
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc refference-0
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc refference-1
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc refference-2
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc refference-3
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc misses-0
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc misses-1
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc misses-2
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: llc misses-3
12/06 08:07:39 DEBUG| utils:0153| [stdout] PASS: branches-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branches-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branches-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branches-3
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branch misses-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branch misses-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branch misses-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: branch misses-3
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: fixed-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: fixed-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: fixed-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: cntr-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fast-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: cntr-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fast-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: cntr-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fast-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: cntr-3
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fast-3
12/06 08:07:40 DEBUG| utils:0153| [stdout] FAIL: rdpmc: fixed cntr-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fixed fast-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] FAIL: rdpmc: fixed cntr-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fixed fast-1
12/06 08:07:40 DEBUG| utils:0153| [stdout] FAIL: rdpmc: fixed cntr-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: rdpmc: fixed fast-2
12/06 08:07:40 DEBUG| utils:0153| [stdout] FAIL: all counters
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: overflow: cntr-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: overflow: status-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: overflow: status clear-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: overflow: irq-0
12/06 08:07:40 DEBUG| utils:0153| [stdout] PASS: overflow: cntr-1
12/06 08:07:40 

[Kernel-packages] [Bug 1790825] Re: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server

2019-12-17 Thread Sean Feole
** Changed in: ubuntu-kernel-tests
   Status: In Progress => Invalid

** Changed in: ubuntu-kernel-tests
 Assignee: Sean Feole (sfeole) => (unassigned)

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

Title:
  gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64  server

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  These two test will fail on a Moonshot node, with Bionic installed.

  $ sudo ./run_tests.sh  -v
  SKIP selftest-setup (qemu-system-aarch64: Unable to determine GIC version 
supported by host)
  SKIP selftest-vectors-kernel (qemu-system-aarch64: Unable to determine GIC 
version supported by host)
  SKIP selftest-vectors-user (qemu-system-aarch64: Unable to determine GIC 
version supported by host)
  SKIP selftest-smp (qemu-system-aarch64: Unable to determine GIC version 
supported by host)
  SKIP pci-test (qemu-system-aarch64: Unable to determine GIC version supported 
by host)
  SKIP pmu (qemu-system-aarch64: Unable to determine GIC version supported by 
host)
  TESTNAME=gicv2-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 
$((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'ipi'
  PASS gicv2-ipi (3 tests)
  TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP 
-machine gic-version=3 -append 'ipi'
  FAIL gicv3-ipi
  TESTNAME=gicv2-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 
$((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'active'
  PASS gicv2-active (1 tests)
  TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP 
-machine gic-version=3 -append 'active'
  FAIL gicv3-active
  SKIP psci (qemu-system-aarch64: Unable to determine GIC version supported by 
host)
  SKIP timer (qemu-system-aarch64: Unable to determine GIC version supported by 
host)

  Further check with these two failed test case, they are complaining
  the same issue:

  
root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP 
-machine gic-version=3 -append 'ipi'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 
-append ipi # -initrd /tmp/tmp.oWkFeTiIeQ
  qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number

  
root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
 TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP 
-machine gic-version=3 -append 'active'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 
-append active # -initrd /tmp/tmp.1X2ud5gyAh
  qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: User Name 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  5 08:09 seq
   crw-rw 1 root audio 116, 33 Sep  5 08:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Wed Sep  5 08:56:52 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1828165] Re: gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot

2019-12-17 Thread Sean Feole
** Changed in: ubuntu-kernel-tests
   Status: Triaged => Invalid

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

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

Title:
  gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This test passed with X-HWE on ARM64 Moonshot:
  TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 
$((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio'
  PASS gicv2-mmio (17 tests, 1 skipped)

  So this feels like a kernel issue to me.

  # MAX_SMP=8
  # TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp 
$((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults 
-machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device 
-device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev 
-display none -serial stdio -kernel arm/gic.flat -smp 8 -machine gic-version=2 
-append mmio # -initrd /tmp/tmp.OlzPYOZSZn
  INFO: gicv2: mmio: number of implemented SPIs: 256
  PASS: gicv2: mmio: all 8 CPUs have interrupts
  INFO: gicv2: mmio: IIDR: 0x4b00043b
  PASS: gicv2: mmio: GICD_TYPER is read-only
  PASS: gicv2: mmio: GICD_IIDR is read-only
  PASS: gicv2: mmio: ICPIDR2 is read-only (0x)
  PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x)
  PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8)
  PASS: gicv2: mmio: IPRIORITYR: clearing priorities
  PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI
  PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs
  PASS: gicv2: mmio: IPRIORITYR: priorities are preserved
  PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf)
  PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f)
  SKIP: gicv2: mmio: ITARGETSR: CPU masking (all CPUs implemented)
  PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI
  FAIL: gicv2: mmio: ITARGETSR: register content preserved (0103020f => 
01010201)
  PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x0103020f => 0x02)
  FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x01010201)
  SUMMARY: 17 tests, 2 unexpected failures, 1 skipped

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-146-generic 4.4.0-146.172
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  Uname: Linux 4.4.0-146-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  8 02:17 seq
   crw-rw 1 root audio 116, 33 May  8 02:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed May  8 06:36:49 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-146-generic N/A
   linux-backports-modules-4.4.0-146-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed

2019-12-17 Thread Sean Feole
** Tags added: bionic

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

Title:
  apic test in kvm-unit-test failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-edge source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New

Bug description:
  With Joshua's comment in bug 1719524: "Nested KVM can only be tried on
  instance sizes with nested Hypervisor support: Ev3 and Dv3.", although
  the instance name is E4v3 here but I can start a KVM on it.

  Test apic will timeout on it.

  Steps:
  1. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests; ./configure; make
  3. Run the apic test as root:
   
  # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline
  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  FAIL: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: Local apic enabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  PASS: nmi-after-sti
  qemu-system-x86_64: terminating on signal 15 from pid 7246

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4
  ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14
  Uname: Linux 4.14.0-1004-azure-edge x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb  8 06:00:55 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: linux-azure-edge
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-1009-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev 
sudo video
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1853433] Re: 2 failures reported in apic test from ubuntu_kvm_unit_tests on X-4.15 AWS i3.metal

2019-12-17 Thread Sean Feole
*** This bug is a duplicate of bug 1748103 ***
https://bugs.launchpad.net/bugs/1748103

Lets move all of the APIC Failures to LP# 1748103  This is baremetal on
the clouds also, so we should have similar failures in the labs.

Both of these failures have been recorded in lab hardware:

  FAIL: x2apic id matches cpuid
  FAIL: PV IPIs testing

** This bug has been marked a duplicate of bug 1748103
   apic test in kvm-unit-test failed

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

Title:
  2 failures reported in apic test from ubuntu_kvm_unit_tests on X-4.15
  AWS i3.metal

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

Bug description:
  Failed on i3.metal with 4.15 AWS kernel on Xenial

  Failed with:
FAIL: x2apic id matches cpuid
FAIL: PV IPIs testing

   Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/apic'
   BUILD_HEAD=e2c275c4
   timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.DZ9WFN5d5D -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd 
/tmp/tmp.2CKCPKuiPX
   enabling apic
   enabling apic
   paging enabled
   cr0 = 80010011
   cr3 = 45a000
   cr4 = 20
   apic version: 50014
   PASS: apic existence
   PASS: xapic id matches cpuid
   PASS: writeable xapic id
   PASS: non-writeable x2apic id
   PASS: sane x2apic id
   FAIL: x2apic id matches cpuid
   PASS: correct xapic id after reset
   PASS: apic_disable: Local apic disabled
   PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
   PASS: apic_disable: *0xfee00030: 
   PASS: apic_disable: CR8: 0
   PASS: apic_disable: CR8: f
   PASS: apic_disable: *0xfee00080: 
   PASS: apic_disable: Local apic enabled in xAPIC mode
   PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
   PASS: apic_disable: *0xfee00030: 50014
   PASS: apic_disable: *0xfee00080: 0
   PASS: apic_disable: *0xfee00080: f0
   PASS: apic_disable: Local apic enabled in x2APIC mode
   PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
   PASS: apic_disable: *0xfee00030: 
   PASS: apic_disable: CR8: 0
   PASS: apic_disable: CR8: f
   PASS: apic_disable: *0xfee00080: 
   x2apic enabled
   PASS: x2apic enabled to invalid state
   PASS: x2apic enabled to apic enabled
   PASS: x2apic enabled to disabled state
   PASS: disabled to invalid state
   PASS: disabled to x2apic enabled
   PASS: apic enabled to invalid state
   PASS: apicbase: relocate apic
   PASS: apicbase: reserved physaddr bits
   PASS: apicbase: reserved low bits
   PASS: self ipi
   starting broadcast (x2apic)
   PASS: APIC physical broadcast address
   PASS: APIC physical broadcast shorthand
   FAIL: PV IPIs testing
   PASS: nmi-after-sti
   PASS: multiple nmi
   PASS: APIC LVT timer one shot
   starting apic change mode
   PASS: TMICT value reset
   PASS: TMCCT should have a non-zero value
   PASS: TMCCT should have reached 0
   PASS: TMCCT should have a non-zero value
   PASS: TMCCT should not be reset to TMICT value
   PASS: TMCCT should be reset to the initial-count
   PASS: TMCCT should not be reset to init
   PASS: TMCCT should have reach zero
   PASS: TMCCT should stay at zero
   PASS: tsc deadline timer
   PASS: tsc deadline timer clearing
   SUMMARY: 51 tests, 2 unexpected failures
   FAIL apic (51 tests, 2 unexpected failures)

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

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


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

2019-12-17 Thread Sean Feole
SRU 2019.12.02 Bionic linux-oracle, Kernel:5.0.0-1009.14~18.04.1

Failure seen in apic-split..

12/06 08:07:06 DEBUG| utils:0153| [stdout] FAIL: TMCCT should not be
reset to TMICT value

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

Title:
  apic-split will fail in kvm_units_tests

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

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

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

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

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


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

2019-12-17 Thread Sean Feole
SRU 2019.12.02 Bionic linux-oracle, Kernel:

Failure seen in apic-split..

12/06 08:07:06 DEBUG| utils:0153| [stdout] FAIL: TMCCT should not be
reset to TMICT value

** Changed in: ubuntu-kernel-tests
   Status: New => Triaged

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

Title:
  apic-split will fail in kvm_units_tests

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

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

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

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

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


[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

2019-12-17 Thread Seth Forshee
https://lists.ubuntu.com/archives/kernel-team/2019-December/106438.html

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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


[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Packaging
  phase-changed: Thursday, 12. December 2019 19:46 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
+   prepare-package: Stalled -- package tag not yet published
prepare-package-meta: Pending -- package not yet uploaded
  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/1856235

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Packaging
  phase-changed: Thursday, 12. December 2019 19:46 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

2019-12-17 Thread Seth Forshee
** Description changed:

+ SRU Justification
+ 
+ Impact: The nvidia-435 drivers are missing from linux-restricted-modules
+ in eoan. On install ubuntu-drivers picks 435 as the newest version, and
+ users must use self-signed dkms drivers and enroll a MOK.
+ 
+ Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.
+ 
+ Test Case: A test build is available in ppa:sforshee/test-builds. Verify
+ that signed drivers for nvidia-435 can be installed for eoan via the
+ linux-modules-nvidia-435-{generic,lowlatency} packages.
+ 
+ Regression Potential: The nvidia-435 l-r-m drivers are new packages
+ built from the same source as the nvidia-435 dkms driver, so regressions
+ are unlikely.
+ 
+ ---
+ 
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of having
  to locally self-sign and enroll a signing key through MOK.  But lrm in
  eoan is only building driver packages for nvidia 390 and 430, and nvidia
  435 is present in eoan.
  
  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.
  
  We should never allow the archive to get into this situation.  We should
  be enforcing that any version of the nvidia driver that we expect
  ubuntu-drivers to install by default on any hardware is integrated into
  linux-restricted-modules, and we should ensure that ubuntu-drivers
  always prefers the signed drivers over other options.

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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


[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

2019-12-17 Thread Norbert Lanzenberger
@Kedar No, I only tried this with a vanila 19.10 kernel.

cat /sys/power/mem_sleep
s2idle [deep]

Do you mean you don't even get the s2idle option when you run the
command or was deep selected by default?

@Kai-Heng I will try 5.5 Kernel on the weekend and will get back to you.

BTW, how do you make codeblocks in this forum?

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

2019-12-17 Thread Juerg Haefliger
** Summary changed:

- bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.1 -proposed tracker
+ bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

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

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
  phase: Packaging
  phase-changed: Thursday, 12. December 2019 19:46 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1854777] Re: disco/linux-gcp: 5.0.0-1027.28 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1854774
bionic/linux-gke-5.0: bug 1854776
  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/1854777

Title:
  disco/linux-gcp: 5.0.0-1027.28 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1854774
bionic/linux-gke-5.0: bug 1854776
  variant: debs

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

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


[Kernel-packages] [Bug 1854777] Re: disco/linux-gcp: 5.0.0-1027.28 -proposed tracker

2019-12-17 Thread Sean Feole
SRU regression testing done, Existing bugs found here:
https://bugs.launchpad.net/ubuntu-kernel-
tests/+bugs?field.tag=sru-20191202

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

Title:
  disco/linux-gcp: 5.0.0-1027.28 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1854774
bionic/linux-gke-5.0: bug 1854776
  variant: debs

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

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


[Kernel-packages] [Bug 1854777] Re: disco/linux-gcp: 5.0.0-1027.28 -proposed tracker

2019-12-17 Thread Sean Feole
** Tags added: regression-testing-passed

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

Title:
  disco/linux-gcp: 5.0.0-1027.28 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 14:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1854774
bionic/linux-gke-5.0: bug 1854776
  variant: debs

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

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


[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

2019-12-17 Thread Martin Wimpress
Assign Seth Forshee during the desktop team meeting in #ubuntu-desktop
on December 17th. If it turns out these assignments are incorrect we can
reassign them.

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

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

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

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

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

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

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

** Tags added: block-proposed-focal

** Tags added: block-proposed

** 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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Packaging
- phase-changed: Tuesday, 17. December 2019 13:23 UTC
+ phase: Promote to Proposed
+ phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  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/1856701

Title:
  focal/linux: 5.4.0-9.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -proposed tracker

2019-12-17 Thread Seth Forshee
** Summary changed:

- focal/linux: 5.4.0-10.13 -proposed tracker
+ focal/linux: 5.4.0-9.12 -proposed tracker

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

Title:
  focal/linux: 5.4.0-9.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Promote to Proposed
  phase-changed: Tuesday, 17. December 2019 14:11 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

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


[Kernel-packages] [Bug 1855448] Re: focal/linux: 5.4.0-8.11 -proposed tracker

2019-12-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 13. December 2019 11:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  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/1855448

Title:
  focal/linux: 5.4.0-8.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Friday, 13. December 2019 11:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-10.13 -proposed tracker

2019-12-17 Thread Seth Forshee
** Summary changed:

- focal/linux:  -proposed tracker
+ focal/linux: 5.4.0-10.13 -proposed tracker

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

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

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

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

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

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

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

Title:
  focal/linux: 5.4.0-10.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Tuesday, 17. December 2019 13:23 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-10.13 -proposed tracker

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

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Packaging
- phase-changed: Tuesday, 17. December 2019 13:13 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 17. December 2019 13:23 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  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/1856701

Title:
  focal/linux: 5.4.0-10.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Tuesday, 17. December 2019 13:23 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

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


[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

2019-12-17 Thread Kedar Patankar
Also tried with 5.3 kernel that shipped with 19.10 and I see only "deep"
in /sys/power/mem_sleep.

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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


  1   2   >