[Kernel-packages] [Bug 1819614] Re: linux-aws: 4.18.0-1012.14 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

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

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

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

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

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

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

  backports: bug 1819613 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Friday, 15. March 2019 18:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1807550] Re: kernel bug

2019-03-25 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  kernel bug

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have this bug with a couple of different kernels including a locally
  built version dmesg output follows

  
  [   15.126210] BUG: unable to handle kernel paging request at 2d18
  [   15.126213] PGD 0 P4D 0 
  [   15.126216] Oops:  [#1] PREEMPT SMP PTI
  [   15.126219] CPU: 0 PID: 39 Comm: kworker/0:2 Not tainted 4.18.171.0 #1
  [   15.126221] Hardware name: Hewlett-Packard HP EliteBook 8460p/161C, BIOS 
68SCF Ver. F.67 02/13/2018
  [   15.126226] Workqueue: usb_hub_wq hub_event
  [   15.126231] RIP: 0010:cxusb_disconnect+0x18/0x70 [dvb_usb_cxusb]
  [   15.126232] Code: 85 c0 75 e7 31 c0 48 c7 02 00 00 00 00 5d c3 0f 1f 00 66 
66 66 66 90 55 48 89 e5 41 55 41 54 49 89 fc 53 48 8b 87 c8 00 00 00 <4c> 8b a8 
18 2d 00 00 49 8b 5d 10 48 85 db 74 18 48 8b 83 a8 00 00 
  [   15.126256] RSP: :bd0800e1fbf0 EFLAGS: 00010246
  [   15.126258] RAX:  RBX: 9cdfab1e3830 RCX: 

  [   15.126259] RDX:  RSI: 9cdfab1e3800 RDI: 
9cdfab1e3800
  [   15.126260] RBP: bd0800e1fc08 R08:  R09: 
97335400
  [   15.126262] R10: 9cdfaef98b28 R11: 0001 R12: 
9cdfab1e3800
  [   15.126263] R13: c09920a8 R14: 9cdfb3cbf800 R15: 
9cdfb3cbf8a0
  [   15.126265] FS:  () GS:9cdfbdc0() 
knlGS:
  [   15.126266] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.126268] CR2: 2d18 CR3: 0001d3c0a003 CR4: 
000606f0
  [   15.126269] Call Trace:
  [   15.126275]  usb_unbind_interface+0x7a/0x280
  [   15.126279]  device_release_driver_internal+0x18c/0x260
  [   15.126281]  device_release_driver+0x12/0x20
  [   15.126283]  bus_remove_device+0xec/0x160
  [   15.126286]  device_del+0x13b/0x350
  [   15.126288]  ? __dev_printk+0x44/0x70
  [   15.126290]  usb_disable_device+0x9f/0x270
  [   15.126293]  usb_disconnect+0xca/0x2c0
  [   15.126296]  hub_event+0xc42/0x15c0
  [   15.126299]  ? __switch_to_asm+0x34/0x70
  [   15.126301]  ? native_usergs_sysret64+0x1/0x10
  [   15.126305]  process_one_work+0x208/0x3f0
  [   15.126308]  worker_thread+0x34/0x3f0
  [   15.126311]  kthread+0x120/0x140
  [   15.126313]  ? rescuer_thread+0x390/0x390
  [   15.126315]  ? kthread_create_worker_on_cpu+0x70/0x70
  [   15.126317]  ret_from_fork+0x35/0x40
  [   15.126319] Modules linked in: snd_pcm dvb_usb_cxusb videobuf2_v4l2 
snd_seq_midi sparse_keymap wmi_bmof kvm videobuf2_common dib0070 
snd_seq_midi_event videodev irqbypass dvb_usb dvb_core rc_core iwlwifi 
crct10dif_pclmul crc32_pclmul snd_rawmidi ghash_clmulni_intel media pcbc 
snd_seq cfg80211 btusb joydev aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf i915 snd_seq_device snd_timer btrtl 
btbcm btintel drm_kms_helper input_leds serio_raw drm snd bluetooth 
ecdh_generic soundcore wmi hp_accel mei_me mei lis3lv02d video i2c_algo_bit 
fb_sys_fops syscopyarea sysfillrect sysimgblt input_polldev tpm_infineon 
mac_hid sch_fq_codel cuse sunrpc parport_pc ppdev lp parport ip_tables x_tables 
autofs4 gpio_ich firewire_ohci firewire_core sdhci_pci cqhci ahci crc_itu_t 
sdhci libahci
  [   15.126361]  lpc_ich psmouse e1000e
  [   15.126364] CR2: 2d18
  [   15.126367] ---[ end trace 71f2182769f6553a ]---
  [   15.126369] RIP: 0010:cxusb_disconnect+0x18/0x70 [dvb_usb_cxusb]
  [   15.126370] Code: 85 c0 75 e7 31 c0 48 c7 02 00 00 00 00 5d c3 0f 1f 00 66 
66 66 66 90 55 48 89 e5 41 55 41 54 49 89 fc 53 48 8b 87 c8 00 00 00 <4c> 8b a8 
18 2d 00 00 49 8b 5d 10 48 85 db 74 18 48 8b 83 a8 00 00 
  [   15.126394] RSP: :bd0800e1fbf0 EFLAGS: 00010246
  [   15.126396] RAX:  RBX: 9cdfab1e3830 RCX: 

  [   15.126397] RDX:  RSI: 9cdfab1e3800 RDI: 
9cdfab1e3800
  [   15.126398] RBP: bd0800e1fc08 R08:  R09: 
97335400
  [   15.126400] R10: 9cdfaef98b28 R11: 0001 R12: 
9cdfab1e3800
  [   15.126401] R13: c09920a8 R14: 9cdfb3cbf800 R15: 
9cdfb3cbf8a0
  [   15.126403] FS:  () GS:9cdfbdc0() 
knlGS:
  [   15.126404] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.126405] CR2: 2d18 CR3: 0001d3c0a003 CR4: 
000606f0
  [   15.139535] kvm: disabled by bios
  [   15.422524] hp_wmi: query 0xd returned error 0x5

  cat /proc/version
  Linux version 4.18.171.0 (root@elitebook) (gcc version 8.2.0 (Ubuntu 
8.2.0-7ubuntu1)) #1 SMP PREEMPT Sun Dec 9 12:40:53 AEDT 2018

  lspci
  00:00.0 Host 

[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819660
  phase: Promote to Proposed
  phase-changed: Monday, 25. March 2019 20:33 UTC
  reason:
-   promote-to-proposed: Stalled -- packages no longer available
+   promote-to-proposed: Stalled -- review FAILED

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

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Monday, 25. March 2019 20:33 UTC
  reason:
promote-to-proposed: Stalled -- review FAILED

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

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


[Kernel-packages] [Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

2019-03-25 Thread Vic Liu
** Description changed:

  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.
  
  Some more findings:
  
  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).
  
  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging out
  doesn't trigger this bug. So this might(?) also involves systemd-logind
  as well;
  
  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.
  
  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.
  
  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  
   Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
-* 5.0.0-7-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
+    * 5.0.0-7-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 240-6ubuntu1
+    * 240-6ubuntu1
  * gdm3:
-* 3.31.4+git20190225-1ubuntu1
+    * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623
  
  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every case.
  
-  ### Cosmic
+  ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
-* 5.0.0-7-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
+    * 5.0.0-7-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 239-7ubuntu10
+    * 239-7ubuntu10
  * gdm3:
-* 3.30.1-1ubuntu5
+    * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623
  
  Summary: in Ubuntu Cosmic, same with Disco.
  
  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 237-3ubuntu10.12
+    * 237-3ubuntu10.12
  * gdm3:
-* 3.28.3-0ubuntu18.04.3
+    * 3.28.3-0ubuntu18.04.3
  ## Hardware
  * 201811-26623
  
  Summary: only 4.18 kernel with nouveau driver is immune from this issue,
  which follows some changes in user land should be necessary to stabilize
  all the (nouveau) cases. But even with that, from previous results of
  Cosmic/Disco, there should still some works to be done in the nvidia
  driver.
+ 
+ OEM-tag: LP: #1804607

-- 
You received this bug notification because you are a 

[Kernel-packages] [Bug 1690085]

2019-03-25 Thread alfie
> No it hasn't - I'm still waiting for someone to test it and confirm that it
> fixes the issue on their boxes. And by issue I don't mean erratum 1033 -
> that is a red herring anyway - but the lockups people are reporting on some
> broken BIOSes.

Yes, your patch "seems" to work in my case.

"Seems" because this bug is difficult to replicate...

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The 

[Kernel-packages] [Bug 1690085]

2019-03-25 Thread alfie
Created attachment 281999
Add rifw kernel parameter to test a couple of patch to workaround ryzen freezes

Add rifw kernel parameter.

rifw=none - don't do anything
rifw=alfie - ignore BIOS
rifw=boris - use Borislav Petkov patch

I works with kernels 4.19, 4.20 and 5.0.2

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present 

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

2019-03-25 Thread Daniel van Vugt
Thanks for the bug report. Since pulseaudio is unchanged (the same
version) in 19.04 from 18.10 I think we can exclude that as a possible
cause.

1. The first idea I have about possible causes is a kernel change (and
the kernel has changed a lot). Please try some older kernels from here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

(for reference, Ubuntu 18.10 uses kernel 4.18).

2. Also, is the crackling from internal speakers or headphones?

3. Finally, please check that something hasn't accidentally enabled:

  Settings > Sound > Over-Amplification

  as that could cause crackling.

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

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

** Summary changed:

- repeating crackling noise after 19.04 upgrade
+ [snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

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

Title:
  [snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade

Status in linux package in Ubuntu:
  Incomplete

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

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

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

  The system was running smoothly on 18.10

  Alessandro-

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

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

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


[Kernel-packages] [Bug 1821663] [NEW] repeating crackling noise after 19.04 upgrade

2019-03-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

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

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

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

The system was running smoothly on 18.10

Alessandro-

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

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


** Tags: amd64 apport-bug disco third-party-packages
-- 
repeating crackling noise after 19.04 upgrade
https://bugs.launchpad.net/bugs/1821663
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819698
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819704
  phase: Testing
  phase-changed: Monday, 25. March 2019 14:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819704
  phase: Testing
  phase-changed: Monday, 25. March 2019 14:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-certification-testing: Ongoing -- testing in progress
+   snap-release-to-candidate: Pending -- snap not in 18-pi3/candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18-pi3/candidate channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

2019-03-25 Thread Daniel van Vugt
** Also affects: gnome-bluetooth (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Confirmed

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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


[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

2019-03-25 Thread Canonical Certification Team
Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/u6wZK1iC/843-pi-
kernel-4150-103335-25-18-pi3

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

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker

2019-03-25 Thread Marcelo Cerri
** Summary changed:

- linux-fips: 4.15.0-1002.2 -proposed tracker
+ linux-fips: 4.15.0-1002.3 -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/1819707

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

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1819716
  phase: Packaging
  phase-changed: Friday, 22. March 2019 21:12 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1821408] Re: scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery

2019-03-25 Thread dann frazier
** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  scsi: libsas: Support SATA PHY connection rate unmatch fixing during
  discovery

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

Bug description:
  [Impact]
  SATA disks may be unusable
  will not be usable when:
   - The disk is connected through a SAS expander
   - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
   - link rate between expander & disk is greater than link between controller 
and expander

  [Test Case]
  See conditions in "Impact"

  Can be simulated with:
  for f in  /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do
echo "3.0 Gbit" | sudo tee $f
  done

  [Fix]
  cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing 
during discovery

  [Regression Risk]
  Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
  Code change is all within an "if" statement that meets these restrictions.
  A bug in this code could possibly reduce the speed of an otherwise working 
disk connection.

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

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


[Kernel-packages] [Bug 1821408] Re: scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery

2019-03-25 Thread dann frazier
** Description changed:

  [Impact]
  SATA disks may be unusable
  will not be usable when:
-  - The disk is connected through a SAS expander
-  - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
-  - link rate between expander & disk is greater than link between controller 
and expander
+  - The disk is connected through a SAS expander
+  - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
+  - link rate between expander & disk is greater than link between controller 
and expander
  
  [Test Case]
  See conditions in "Impact"
+ 
+ Can be simulated with:
+ for f in  /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do
+   echo "3.0 Gbit" | sudo tee $f
+ done
  
  [Fix]
  cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing 
during discovery
  
  [Regression Risk]
  Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
  Code change is all within an "if" statement that meets these restrictions.
  A bug in this code could possibly reduce the speed of an otherwise working 
disk connection.

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

Title:
  scsi: libsas: Support SATA PHY connection rate unmatch fixing during
  discovery

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

Bug description:
  [Impact]
  SATA disks may be unusable
  will not be usable when:
   - The disk is connected through a SAS expander
   - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
   - link rate between expander & disk is greater than link between controller 
and expander

  [Test Case]
  See conditions in "Impact"

  Can be simulated with:
  for f in  /sys/class/sas_phy/phy-1\:*/maximum_linkrate; do
echo "3.0 Gbit" | sudo tee $f
  done

  [Fix]
  cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing 
during discovery

  [Regression Risk]
  Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
  Code change is all within an "if" statement that meets these restrictions.
  A bug in this code could possibly reduce the speed of an otherwise working 
disk connection.

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

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


[Kernel-packages] [Bug 1804054] Re: [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel

2019-03-25 Thread Joseph Salisbury
** Changed in: linux-azure (Ubuntu)
   Status: Triaged => New

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

Title:
  [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032
  kernel

Status in linux-azure package in Ubuntu:
  New

Bug description:
  While testing linux-azure 4.15.0-1032 kernel from proposed we found
  that kdump is no longer working as expected, on trusty only.

  Here are some info and versions.
  We'll have to verify a few more scenarios with other images and try to 
isolate this, but as least the kdump on trusty issue is there.
  Also remains to be checked in which release this regression was introduced.
  The below can be repro'd on Azure.

  On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

  It looks like the kexec might require some patches from upstream as
  far as I can tell from the data we have so far.

  Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
  Package: kdump-tools1.5.5-2ubuntu1.6

  Errors from logs:
  kdump-config: failed to load kdump kernel
  kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

  ---

  This issue looks resolved with the kexec package build from the
  official kernel.org kexec repo, on top of 14.04.

  kexec-tools 2.0.18
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

  # cat /sys/kernel/kexec_*
  1
  402653184
  And kdump core file gets created when running with 1032 kernel.

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

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


[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share

2019-03-25 Thread Tyler Hicks
Thanks for all your work on this! I've submitted the fixes to be
included in the Disco kernel:

 https://lists.ubuntu.com/archives/kernel-team/2019-March/099491.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/1821053

Title:
  [disco] [5.0.0-7.8] can't mount guest cifs share

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi,

  with a simple smb.conf setup like this:
  [pub]
  path = /pub
  guest ok = yes

  The following mount command fails when the running kernel is 5.0.0-7:
  root@ubuntu:~# dmesg -C
  root@ubuntu:~# mount //localhost/pub /mnt -o guest
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  root@ubuntu:~# dmesg
  [  178.469307] CIFS: Attempting to mount //localhost/pub
  [  178.469343] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.
  [  178.481741] CIFS VFS: failed to connect to IPC (rc=-13)
  [  178.485272] CIFS VFS: cifs_mount failed w/return code = -13

  samba server logs, in debug 5, show:
  [2019/03/20 17:25:19.365445,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.365524,  0] ../../lib/util/util.c:508(dump_data)
[] A6 62 5F 50 9C D7 31 42   14 34 52 9F AA 49 C8 31   .b_P..1B .4R..I.1
  [2019/03/20 17:25:19.365562,  0] ../../lib/util/util.c:508(dump_data)
[] 31 37 12 A2 D5 D4 59 99   0B 63 C5 21 EB 86 70 74   17Y. .c.!..pt
  [2019/03/20 17:25:19.369055,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.369092,  0] ../../lib/util/util.c:508(dump_data)
[] 23 2C 4F 10 0E 4E 46 2E   8A 5B E3 70 0F B3 D3 FB   #,O..NF. .[.p
  [2019/03/20 17:25:19.369120,  0] ../../lib/util/util.c:508(dump_data)
[] 50 F7 C6 8A 6E BC B2 B7   1C 2F 43 30 90 6A 25 CA   P...n... ./C0.j%.

  
  With kernel 4.19.0-12-generic, the exact same system, the command works:

  root@ubuntu:~# dmesg -C

  root@ubuntu:~# mount //localhost/pub /mnt -o guest

  root@ubuntu:~# dmesg
  [  277.745885] FS-Cache: Loaded
  [  277.768408] FS-Cache: Netfs 'cifs' registered for caching
  [  277.768495] Key type cifs.spnego registered
  [  277.768498] Key type cifs.idmap registered
  [  277.768707] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.

  root@ubuntu:~# mount -t cifs
  //localhost/pub on /mnt type cifs 
(rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  root@ubuntu:~# uname -r
  4.19.0-12-generic

  
  Just looking at the list of patches queued up for the next upstream kernel 
release, at 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0,
 this one looks promising:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch


  I can easily test a new kernel for you.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 18:04 seq
   crw-rw 1 root audio 116, 33 Mar 20 18:04 timer
  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'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  

[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   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: 1819660
- phase: Packaging
- phase-changed: Monday, 25. March 2019 18:35 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 25. March 2019 20:33 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
promote-to-proposed: Stalled -- packages no longer available

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

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Monday, 25. March 2019 20:33 UTC
  reason:
promote-to-proposed: Stalled -- packages no longer available

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

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


[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share

2019-03-25 Thread Tyler Hicks
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

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

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

Title:
  [disco] [5.0.0-7.8] can't mount guest cifs share

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi,

  with a simple smb.conf setup like this:
  [pub]
  path = /pub
  guest ok = yes

  The following mount command fails when the running kernel is 5.0.0-7:
  root@ubuntu:~# dmesg -C
  root@ubuntu:~# mount //localhost/pub /mnt -o guest
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  root@ubuntu:~# dmesg
  [  178.469307] CIFS: Attempting to mount //localhost/pub
  [  178.469343] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.
  [  178.481741] CIFS VFS: failed to connect to IPC (rc=-13)
  [  178.485272] CIFS VFS: cifs_mount failed w/return code = -13

  samba server logs, in debug 5, show:
  [2019/03/20 17:25:19.365445,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.365524,  0] ../../lib/util/util.c:508(dump_data)
[] A6 62 5F 50 9C D7 31 42   14 34 52 9F AA 49 C8 31   .b_P..1B .4R..I.1
  [2019/03/20 17:25:19.365562,  0] ../../lib/util/util.c:508(dump_data)
[] 31 37 12 A2 D5 D4 59 99   0B 63 C5 21 EB 86 70 74   17Y. .c.!..pt
  [2019/03/20 17:25:19.369055,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.369092,  0] ../../lib/util/util.c:508(dump_data)
[] 23 2C 4F 10 0E 4E 46 2E   8A 5B E3 70 0F B3 D3 FB   #,O..NF. .[.p
  [2019/03/20 17:25:19.369120,  0] ../../lib/util/util.c:508(dump_data)
[] 50 F7 C6 8A 6E BC B2 B7   1C 2F 43 30 90 6A 25 CA   P...n... ./C0.j%.

  
  With kernel 4.19.0-12-generic, the exact same system, the command works:

  root@ubuntu:~# dmesg -C

  root@ubuntu:~# mount //localhost/pub /mnt -o guest

  root@ubuntu:~# dmesg
  [  277.745885] FS-Cache: Loaded
  [  277.768408] FS-Cache: Netfs 'cifs' registered for caching
  [  277.768495] Key type cifs.spnego registered
  [  277.768498] Key type cifs.idmap registered
  [  277.768707] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.

  root@ubuntu:~# mount -t cifs
  //localhost/pub on /mnt type cifs 
(rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  root@ubuntu:~# uname -r
  4.19.0-12-generic

  
  Just looking at the list of patches queued up for the next upstream kernel 
release, at 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0,
 this one looks promising:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch


  I can easily test a new kernel for you.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 18:04 seq
   crw-rw 1 root audio 116, 33 Mar 20 18:04 timer
  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'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco 

[Kernel-packages] [Bug 1821620] Re: Add HiSilicon SoC quirk for cpufreq

2019-03-25 Thread dann frazier
** Description changed:

  [Impact]
- Some HiSilicon SoCs do not implement registers that the cpufreq subsystem 
uses to calculate current performance. This can result in undefined data being 
used in internal calculations, and being exposed to userspace via sysfs. 
+ Some HiSilicon SoCs do not implement registers that the cpufreq subsystem 
uses to calculate current performance. This can result in undefined data being 
used in internal calculations, and being exposed to userspace via sysfs.
  
  [Test Case]
+ Examine the exposed frequency under idle and load and make sure it looks sane:
+ sudo cat /sys/devices/system/cpu/cpufreq/policy*/cpuinfo_cur_freq
+ 
+ Note: On my test system, it happens to look sane w/o this quirk as well.
+ This is because the undefined reads all happen to return 0x1 today, and
+ that puts us into the avoid-divide-by-zero code path that happens to do
+ the same thing as this quirk (report desired perf instead of actual).
  
  [Fix]
+ 6c8d750f9784c cpufreq / cppc: Work around for Hisilicon CPPC cpufreq
+ 1757d05f3112a ACPI / CPPC: Add a helper to get desired performance
  
  [Regression Risk]
  The fix is a quirk restricted to specific SoCs. It does rely on firmware 
behaving (overloading the desired_perf register w/ a correct actual perf 
value), so changes in firmware could lead to regressions.

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

Title:
  Add HiSilicon SoC quirk for cpufreq

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  Some HiSilicon SoCs do not implement registers that the cpufreq subsystem 
uses to calculate current performance. This can result in undefined data being 
used in internal calculations, and being exposed to userspace via sysfs.

  [Test Case]
  Examine the exposed frequency under idle and load and make sure it looks sane:
  sudo cat /sys/devices/system/cpu/cpufreq/policy*/cpuinfo_cur_freq

  Note: On my test system, it happens to look sane w/o this quirk as
  well. This is because the undefined reads all happen to return 0x1
  today, and that puts us into the avoid-divide-by-zero code path that
  happens to do the same thing as this quirk (report desired perf
  instead of actual).

  [Fix]
  6c8d750f9784c cpufreq / cppc: Work around for Hisilicon CPPC cpufreq
  1757d05f3112a ACPI / CPPC: Add a helper to get desired performance

  [Regression Risk]
  The fix is a quirk restricted to specific SoCs. It does rely on firmware 
behaving (overloading the desired_perf register w/ a correct actual perf 
value), so changes in firmware could lead to regressions.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] [NEW] dmidecode causing system crash

2019-03-25 Thread James Glenn
Public bug reported:

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)

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


** Tags: apport-bug arm64 bionic

-- 
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:
  New

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", 

[Kernel-packages] [Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset

2019-03-25 Thread Kevin
@Kevin (thenewmanium).

I honestly think this is a Intel driver bug. See my thread here on the
Intel forums.

https://forums.intel.com/s/question/0D50P4CK4wZSAT/intel-x550-not-
negotiating-to-10gb-on-x299-chipset?language=en_US

Their conclusion was that it was an Asus changed x550 chip. Asus said
they won't fix it because they "don't support linux". Intel told me they
won't do anything because Asus borked with the firmware. I'm basically
stuck in the middle of two vendors not wanting to do anything because
one doesn't support it and the other doesn't want to look at it because
the other vendor changed it.

If you can validate that its the same issue with different hardware, it
might get some traction (fingers crossed).

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

Title:
  Intel x550 not negotiating to 10Gb on x299 chipset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am having an issue with this particular machine auto negotiating
  10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s
   advertise 0x1000`, the machine will delink and then negotiate
  to 10Gb and work as expecting. Rebooting the machine (or unplugging
  network cable) will cause it to negotiate to 1G again resulting in
  having to run the ethtool command again.

  This is what I have tried:
  Tried different cable from confirmed working machine that auto negotiates to 
10Gb.
  Tried upgrading ixgbe driver to latest (5.5.3)
  Tried upgrading X550 firmware.
  I put an Intel x540-T1 card in the machine and that card works properly and 
negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still 
negotiates to 1Gb.
  I also tried loading a live version of Fedora 29 (Kernel 4.18) with same 
exact symptoms.

  We have several other machine negotiating fine on the same exact
  switch. I have tried those cables to test this problematic machine
  with same result as above.

  We have a machine that is pretty similar in hardware that is not
  exhibiting this issue. It is an ASUS x99 motherboard, with the same
  LOM Intel x550 card, running on 16.04.

  The machine that is causing problems is an Asus x299 motherboard with
  the Intel x550 LOM card running 18.04 (16.04 won't work on the x299
  chipset for some reason). I have a suspicion that it could potentially
  be related to the x299?

  The only way I have been able to get this problematic machine to
  negotiate to 10Gbps automatically is by plugging a cable directly from
  the LOM x550 of the problematic machine to another machines 10Gb
  network card. Doing that, the problematic machine will negotiate
  properly to 10Gb.

  I'm trying to find another 10Gb switch to test with to see if it could
  be unique to this combination of switch and machine. However, I'm
  reluctant to blame it on the switch since we have about several other
  machine working perfectly fine on the switch (some with the same exact
  x550 LOM).

  Other notes:

  
https://serverfault.com/questions/949006/intel-x550-not-negotiating-to-10gb?noredirect=1#comment1233436_949006
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-12-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp179s0f1  no wireless extensions.
   
   lono wireless extensions.
   
   enp179s0f0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=7e94e4fd-ff67-46c2-9b58-3f7bb3840be4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0905
  dmi.board.asset.tag: Default string
  dmi.board.name: WS X299 SAGE/10G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 25. March 2019 14:54 UTC
+ phase: Packaging
+ phase-changed: Monday, 25. March 2019 18:35 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   prepare-package: Pending -- package not yet uploaded
+   promote-to-proposed: Stalled -- packages no longer available

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

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Packaging
  phase-changed: Monday, 25. March 2019 18:35 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
promote-to-proposed: Stalled -- packages no longer available

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

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


[Kernel-packages] [Bug 1800446] Re: kidle_inject constantly running

2019-03-25 Thread Srinivas Pandruvada
Also can you attach acpi.out by issuing the following command

#acpidump > acpi.out

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

Title:
  kidle_inject constantly running

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

Bug description:
  Computer boots up fine, but as soon as any process causes a single
  spike in CPU, `kidle_inject` starts and it just won't stop.

  Even after 1 hour of idling, with low temperatures, no fan, it’s still
  making this computer unresponsive.

  I disabled `kidle_inject` process by creating a file `/etc/modprobe.d
  /blacklist-power.conf` with the following content:

  ```
  blacklist intel_powerclamp
  blacklist intel_rapl
  ``` 

  Then I restarted computer. Since then, my computer is not unresponsive
  anymore, and I use it to work all the time.

  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:  williamivanski   5974 F pulseaudio
   /dev/snd/controlC1:  williamivanski   5974 F pulseaudio
  Date: Mon Oct 29 08:05:09 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=1c6d4273-ae09-412d-9488-78ab7ba2fc4b
  InstallationDate: Installed on 2015-09-23 (1131 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LG Electronics 13Z940-G.BK71P1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=42b637c4-2da3-4c1a-a62d-b4beb93b8243 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  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: Upgraded to cosmic on 2018-10-23 (5 days ago)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 13Z940FF
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: White Tip Mountain
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr13Z940FF:bd09/04/2014:svnLGElectronics:pn13Z940-G.BK71P1:pvr0.1:rvnLGElectronics:rnWhiteTipMountain:rvrFAB3:cvnLGElectronics:ct9:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: 13Z940-G.BK71P1
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

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

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


[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker

2019-03-25 Thread Marcelo Cerri
** Summary changed:

- linux-fips: 4.4.0-1007.8 -proposed tracker
+ linux-fips: 4.4.0-1007.9 -proposed tracker

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

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

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

Title:
  linux-fips: 4.4.0-1007.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. March 2019 14:54 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1812410] Re: Intel x550 not negotiating to 10Gb on x299 chipset

2019-03-25 Thread Kevin
Hi, this issue affects my hosts as well. I have about 40 hosts running
Intel X550s that were working fine on kernel 4.4.0-141-generic with
regard to negotiating 10Gb automatically. Suddenly after booting into
4.15.0-43-generic they automatically negotiate at 1Gb. I have to use
ethtool to force them to 10Gb.

These are all Dell R640 so I don't think the issue is tied to the Asus
x299. Seems more tightly correlated with the Intel X550 and the kernel
version (4.15+ for me).

I tried the 5.0-rc3 kernel you linked and the issue still exists there.
So, somewhere between 4.4 and 4.13 the issue started and it still has
not been fixed.

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

Title:
  Intel x550 not negotiating to 10Gb on x299 chipset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am having an issue with this particular machine auto negotiating
  10Gb. The onboard LOM will only negotiate to 1Gb. If I run `ethtool -s
   advertise 0x1000`, the machine will delink and then negotiate
  to 10Gb and work as expecting. Rebooting the machine (or unplugging
  network cable) will cause it to negotiate to 1G again resulting in
  having to run the ethtool command again.

  This is what I have tried:
  Tried different cable from confirmed working machine that auto negotiates to 
10Gb.
  Tried upgrading ixgbe driver to latest (5.5.3)
  Tried upgrading X550 firmware.
  I put an Intel x540-T1 card in the machine and that card works properly and 
negotiates to 10Gb automatically. Move the cable to the LOM x550, and it still 
negotiates to 1Gb.
  I also tried loading a live version of Fedora 29 (Kernel 4.18) with same 
exact symptoms.

  We have several other machine negotiating fine on the same exact
  switch. I have tried those cables to test this problematic machine
  with same result as above.

  We have a machine that is pretty similar in hardware that is not
  exhibiting this issue. It is an ASUS x99 motherboard, with the same
  LOM Intel x550 card, running on 16.04.

  The machine that is causing problems is an Asus x299 motherboard with
  the Intel x550 LOM card running 18.04 (16.04 won't work on the x299
  chipset for some reason). I have a suspicion that it could potentially
  be related to the x299?

  The only way I have been able to get this problematic machine to
  negotiate to 10Gbps automatically is by plugging a cable directly from
  the LOM x550 of the problematic machine to another machines 10Gb
  network card. Doing that, the problematic machine will negotiate
  properly to 10Gb.

  I'm trying to find another 10Gb switch to test with to see if it could
  be unique to this combination of switch and machine. However, I'm
  reluctant to blame it on the switch since we have about several other
  machine working perfectly fine on the switch (some with the same exact
  x550 LOM).

  Other notes:

  
https://serverfault.com/questions/949006/intel-x550-not-negotiating-to-10gb?noredirect=1#comment1233436_949006
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-12-14 (34 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp179s0f1  no wireless extensions.
   
   lono wireless extensions.
   
   enp179s0f0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=7e94e4fd-ff67-46c2-9b58-3f7bb3840be4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0905
  dmi.board.asset.tag: Default string
  dmi.board.name: WS X299 SAGE/10G
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0905:bd11/30/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnWSX299SAGE/10G:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  

[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

2019-03-25 Thread Nivedita Singhvi
I am not sure we could deterministically provoke the 
issue. At the very least to ensure no other regression
was introduced, I would run it under heavy network load.

The environment in question which saw the issue had 
network load, contention for cpus and several other 
issues occur.

The basic environment is:

1. For any 25Gb NIC/chipset that requires the 4.4 bnxt_en_bpo
   driver, set its 2 ports/interfaces up in bonding mode 
   as follows:

bond-lacp-rate fast
bond-master bond0
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer3+4
mtu 9000 

2. Run any heavy TCP network load test over the systems
   (e.g. iperf, netperf, file transfer, etc.)

3. Theoretically, it would appear that if the number of tx
   ring descriptors were lower, than that would be more
   likely to hit this (not successfully proven by testing
   here), but can lower it and see if that helps:

   # ethtool -G eno49 tx 128  // for example


I am not sure if that helps, Scott. I'll try and smoke
up more specific steps but I cannot guarantee you will
see the issue.

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

Title:
  bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

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

Bug description:
  [Impact]

  The bnxt_en_bpo driver experienced tx timeouts causing the system to
  experience network stalls and fail to send data and heartbeat packets.

  The following 25Gb Broadcom NIC error was seen on Xenial
  running the 4.4.0-141-generic kernel on an amd64 host
  seeing moderate-heavy network traffic (just once):

  * The bnxt_en_po driver froze on a "TX timed out" error
    and triggered the Netdev Watchdog timer under load.

  * From kernel log:
    "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out"
    See attached kern.log excerpt file for full excerpt of error log.

  * Release = Xenial
    Kernel = 4.4.0-141-generic #167
    eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet

  * This caused the driver to reset in order to recover:

    "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting
  reset task!"

    driver: bnxt_en_bpo
    version: 1.8.1
    source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout()

  * The loss of connectivity and softirq stall caused other failures
    on the system.

  * The bnxt_en_po driver is the imported Broadcom driver
    pulled in to support newer Broadcom HW (specific boards)
    while the bnx_en module continues to support the older
    HW. The current Linux upstream driver does not compile
    easily with the 4.4 kernel (too many changes).

  * This upstream and bnxt_en driver fix is a likely solution:
     "bnxt_en: Fix TX timeout during netpoll"
     commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906

    This fix has not been applied to the bnxt_en_po driver
    version, but review of the code indicates that it is
    susceptible to the bug, and the fix would be reasonable.

  [Test Case]

  * Unfortunately, this is not easy to reproduce. Also, it is only seen
  on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo
  driver.

  [Regression Potential]

  * The patch is restricted to the bpo driver, with very constrained
  scope - just the newest Broadcom NICs being used by the Xenial 4.4
  kernel (as opposed to the hwe 4.15 etc. kernels, which would have the
  in-tree fixed driver).

  * The patch is very small and backport is fairly minimal and simple.

  * The fix has been running on the in-tree driver in upstream mainline
  as well as the Ubuntu Linux in-tree driver, although the Broadcom
  driver has a lot of lower level code that is different, this piece is
  still the same.

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

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


[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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 snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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


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

2019-03-25 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/1821617

Title:
  No touchpad Lenovo Laptop V130

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad not working Lenovo Laptop V130 with ubuntu 18.04 mate

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giambattista   1517 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Mar 25 11:32:02 2019
  InstallationDate: Installed on 2019-02-22 (30 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 5986:1135 Acer, Inc 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81HM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=65da6aae-6d40-47cd-b146-16dcc117fa33 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6WCN33WW(V1.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V130-14IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr6WCN33WW(V1.07):bd07/13/2018:svnLENOVO:pn81HM:pvrLenovoV130-14IGM:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV130-14IGM:
  dmi.product.family: V130-14IGM
  dmi.product.name: 81HM
  dmi.product.version: Lenovo V130-14IGM
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1821620] [NEW] Add HiSilicon SoC quirk for cpufreq

2019-03-25 Thread dann frazier
Public bug reported:

[Impact]
Some HiSilicon SoCs do not implement registers that the cpufreq subsystem uses 
to calculate current performance. This can result in undefined data being used 
in internal calculations, and being exposed to userspace via sysfs. 

[Test Case]

[Fix]

[Regression Risk]
The fix is a quirk restricted to specific SoCs. It does rely on firmware 
behaving (overloading the desired_perf register w/ a correct actual perf 
value), so changes in firmware could lead to regressions.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  Add HiSilicon SoC quirk for cpufreq

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  Some HiSilicon SoCs do not implement registers that the cpufreq subsystem 
uses to calculate current performance. This can result in undefined data being 
used in internal calculations, and being exposed to userspace via sysfs. 

  [Test Case]

  [Fix]

  [Regression Risk]
  The fix is a quirk restricted to specific SoCs. It does rely on firmware 
behaving (overloading the desired_perf register w/ a correct actual perf 
value), so changes in firmware could lead to regressions.

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

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


[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2019-03-25 Thread Boris Gjenero
Sorry, I mean bug is not present in 4.18.0-16-generic and present in
5.0.0-7-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/1821564

Title:
  b44 Ethernet driver null pointer during initialization

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem started after upgrading to Ubuntu 19.04. It was not
  present with 4.18.0-16-generic kernel and is present in the
  4.18.0-15-generic kernel. Ever time during boot there is a null
  pointer dereference in the b44 driver for the on-board Ethernet on
  this Dell Inspiron 6400. After that I can log in but networking
  related commands hang and the computer eventually locks up.
  Blacklisting the b44 module so it doesn't load works as a workaround,
  though of course the on board Ethernet can't be used that way. The b43
  WiFi still works then. The following is pasted from the log of one
  crash:

  6.483003] BUG: unable to handle kernel NULL pointer dereference at 

  6.483052] #PF error: [normal kernel read fault]
  6.483093] PGD 0 P4D 0 
  6.483133] Oops:  [#1] SMP PTI
  6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 
5.0.0-7-generic #8-Ubuntu
  6.483217] Hardware name: Dell Inc. MM061   /0XD720, 
BIOS A17 06/13/2007
  6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310
  6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 
44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 
0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f
  6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016
  6.483416] RAX: 0001 RBX:  RCX: 
  6.483467] RDX:  RSI: 001f RDI: 0001
  6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001
  6.483572] R10:  R11:  R12: 
  6.483621] R13:  R14: 0001 R15: 0020
  6.483670] FS:  7f2cb49ccbc0() GS:9d8a4c40() 
knlGS:
  6.483726] CS:  0010 DS:  ES:  CR0: 80050033
  6.483773] CR2:  CR3: c72ce000 CR4: 06f0
  6.483820] Call Trace:
  6.483869]  swiotlb_map+0x6c/0x1c0
  6.483915]  dma_direct_map_page+0xc5/0x160
  6.483965]  b44_alloc_rx_skb+0x18e/0x3f0 [b44]
  6.484013]  b44_init_rings+0xbe/0x1b0 [b44]
  6.484060]  b44_open+0xfc/0x3f0 [b44]
  6.484107]  __dev_open+0xd4/0x170
  6.484153]  __dev_change_flags+0x18f/0x200
  6.484199]  dev_change_flags+0x27/0x60
  6.484246]  do_setlink+0x31c/0xe30
  6.484292]  ? __nla_parse+0xf1/0x120
  6.484340]  ? cpumask_next+0x1b/0x20
  6.484388]  ? __snmp6_fill_stats64.isra.57+0xf6/0x120
  6.484439]  ? __nla_parse+0x38/0x120
  6.484488]  __rtnl_newlink+0x531/0x910
  6.484535]  ? __nla_put+0x20/0x30
  6.484586]  ? __kmalloc_node_track_caller+0x1e6/0x2b0
  6.484636]  ? pskb_expand_head+0x70/0x2e0
  6.484693]  ? __kmalloc_reserve.isra.53+0x31/0x90
  6.484751]  ? apparmor_inet_conn_request+0x40/0x40
  6.484822]  ? security_sock_rcv_skb+0x2f/0x50
  6.484879]  ? skb_queue_tail+0x43/0x50
  6.484934]  ? __netlink_sendskb+0x53/0x70
  6.484992]  ? syscall_return_via_sysret+0xf/0x7f
  6.485043]  ? __switch_to_asm+0x40/0x70
  6.485097]  ? syscall_return_via_sysret+0xf/0x7f
  6.485153]  ? _cond_resched+0x19/0x30
  6.485204]  ? kmem_cache_alloc_trace+0x153/0x1d0
  6.485253]  rtnl_newlink+0x48/0x70
  6.485301]  rtnetlink_rcv_msg+0x213/0x300
  6.485348]  ? __d_lookup+0x126/0x140
  6.485393]  ? rtnl_calcit.isra.31+0x100/0x100
  6.485440]  netlink_rcv_skb+0x4f/0x120
  6.485485]  rtnetlink_rcv+0x15/0x20
  6.485518]  netlink_unicast+0x1a1/0x260
  6.485518]  netlink_sendmsg+0x20d/0x3c0
  6.485518]  sock_sendmsg+0x3e/0x50
  6.485518]  ___sys_sendmsg+0x295/0x2f0
  6.485518]  ? rtnl_unlock+0xe/0x10
  6.485518]  ? addrconf_sysctl_forward+0x114/0x280
  6.485518]  ? dev_forward_change+0x140/0x140
  6.485518]  ? __fget_light+0x54/0x60
  6.485518]  __sys_sendmsg+0x5c/0xa0
  6.485518]  __x64_sys_sendmsg+0x1f/0x30
  6.485518]  do_syscall_64+0x5a/0x110
  6.485518]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  6.485518] RIP: 0033:0x7f2cb6153cb7
  6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 
3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 
ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48
  6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 
002e
  6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7
  6.485518] RDX:  RSI: 7ffe93a35cd0 RDI: 0008
  6.485518] RBP: 7ffe93a35cd0 R08:  R09: 
  6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 
  6.485518] R13: 5598b029e880 R14: 7ffe93a35e7c R15: 

[Kernel-packages] [Bug 1800446] Re: kidle_inject constantly running

2019-03-25 Thread Srinivas Pandruvada
Do we still have this issue?

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

Title:
  kidle_inject constantly running

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

Bug description:
  Computer boots up fine, but as soon as any process causes a single
  spike in CPU, `kidle_inject` starts and it just won't stop.

  Even after 1 hour of idling, with low temperatures, no fan, it’s still
  making this computer unresponsive.

  I disabled `kidle_inject` process by creating a file `/etc/modprobe.d
  /blacklist-power.conf` with the following content:

  ```
  blacklist intel_powerclamp
  blacklist intel_rapl
  ``` 

  Then I restarted computer. Since then, my computer is not unresponsive
  anymore, and I use it to work all the time.

  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:  williamivanski   5974 F pulseaudio
   /dev/snd/controlC1:  williamivanski   5974 F pulseaudio
  Date: Mon Oct 29 08:05:09 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=1c6d4273-ae09-412d-9488-78ab7ba2fc4b
  InstallationDate: Installed on 2015-09-23 (1131 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LG Electronics 13Z940-G.BK71P1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=42b637c4-2da3-4c1a-a62d-b4beb93b8243 ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  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: Upgraded to cosmic on 2018-10-23 (5 days ago)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 13Z940FF
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: White Tip Mountain
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr13Z940FF:bd09/04/2014:svnLGElectronics:pn13Z940-G.BK71P1:pvr0.1:rvnLGElectronics:rnWhiteTipMountain:rvrFAB3:cvnLGElectronics:ct9:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: 13Z940-G.BK71P1
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

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

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


[Kernel-packages] [Bug 1821617] [NEW] No touchpad Lenovo Laptop V130

2019-03-25 Thread Giambattista Russo
Public bug reported:

Touchpad not working Lenovo Laptop V130 with ubuntu 18.04 mate

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  giambattista   1517 F pulseaudio
CurrentDesktop: MATE
Date: Mon Mar 25 11:32:02 2019
InstallationDate: Installed on 2019-02-22 (30 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:1135 Acer, Inc 
 Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical 
mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81HM
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=65da6aae-6d40-47cd-b146-16dcc117fa33 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 6WCN33WW(V1.07)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo V130-14IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr6WCN33WW(V1.07):bd07/13/2018:svnLENOVO:pn81HM:pvrLenovoV130-14IGM:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV130-14IGM:
dmi.product.family: V130-14IGM
dmi.product.name: 81HM
dmi.product.version: Lenovo V130-14IGM
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  No touchpad Lenovo Laptop V130

Status in linux package in Ubuntu:
  New

Bug description:
  Touchpad not working Lenovo Laptop V130 with ubuntu 18.04 mate

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giambattista   1517 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Mar 25 11:32:02 2019
  InstallationDate: Installed on 2019-02-22 (30 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 5986:1135 Acer, Inc 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81HM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=65da6aae-6d40-47cd-b146-16dcc117fa33 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6WCN33WW(V1.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V130-14IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr6WCN33WW(V1.07):bd07/13/2018:svnLENOVO:pn81HM:pvrLenovoV130-14IGM:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV130-14IGM:
  dmi.product.family: V130-14IGM
  dmi.product.name: 81HM
  dmi.product.version: Lenovo V130-14IGM
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-03-25 Thread Ellie Frost
Kai-Heng Feng:

I've been using your kernel for about a week, and it's solved the issue for me!
$ uname -rv
5.0.0-3-generic #4~lp1799988 SMP Mon Feb 4 00:02:55 CST 2019

Any ideas when your change can be upstreamed? Before I tried your kernel
I tried the Mainline kernel and the issue was still present, so I think
I can validate your change.

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

Title:
  Missing wifi and bluetooth after sleep on XPS 9370

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with 
Killer 1435 wireless module.
  And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly 
define preconditions, but it seems there are following steps to reproduce the 
issue
  1. Connect something via bluetooth  (I use bluetooth headset)
  2. Send laptop to sleep
  3. Wake it and find wifi and bluetooth missing.

  I have to mention that I have also been experienced bluetooth only
  missing, but it somehow transformed to the issue with both wireless
  devices.

  Dmesg after waking up with the issue attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kao2362 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-22 (33 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash 
mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0VM1FG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions

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


[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

2019-03-25 Thread Canonical Certification Team
Snap beta testing complete, no regressions found. Ready for promotion.
Results here:
https://trello.com/c/QKHIFEHt/837-pi2-kernel-440-1105113-84

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

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-certification-testing: Ongoing -- testing in progress
+   snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1821607] Re: Disco update: v5.0.4 upstream stable release

2019-03-25 Thread Seth Forshee
** Description changed:

- 
- SRU Justification
- 
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
- 
-v5.0.4 upstream stable release
-from git://git.kernel.org/
- 
- 
+ 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.0.4 upstream stable release
+    from git://git.kernel.org/
+ 
  Linux 5.0.4
  SUNRPC: Respect RPC call timeouts when retrying transmission
  SUNRPC: Fix up RPC back channel transmission
  SUNRPC: Prevent thundering herd when the socket is not connected
  s390/setup: fix boot crash for machine without EDAT-1
  net: dsa: lantiq_gswip: fix OF child-node lookups
  net: dsa: lantiq_gswip: fix use-after-free on failed probe
  KVM: nVMX: Check a single byte for VMCS "launched" in nested early checks
  KVM: nVMX: Ignore limit checks on VMX instructions using flat segments
  KVM: nVMX: Apply addr size mask to effective address for VMX instructions
  KVM: nVMX: Sign extend displacements of VMX instr's mem operands
  KVM: x86/mmu: Do not cache MMIO accesses while memslots are in flux
  KVM: x86/mmu: Detect MMIO generation wrap in any address space
  KVM: VMX: Zero out *all* general purpose registers after VM-Exit
  KVM: VMX: Compare only a single byte for VMCS' "launched" in vCPU-run
  KVM: Call kvm_arch_memslots_updated() before updating memslots
  drm/amd/display: don't call dm_pp_ function from an fpu block
  drm/amd/powerplay: correct power reading on fiji
  drm/radeon/evergreen_cs: fix missing break in switch statement
  drm/fb-helper: generic: Fix drm_fbdev_client_restore()
  media: imx: csi: Stop upstream before disabling IDMA channel
  media: imx: csi: Disable CSI immediately after last EOF
  media: imx-csi: Input connections to CSI should be optional
  media: vimc: Add vimc-streamer for stream control
  media: uvcvideo: Avoid NULL pointer dereference at the end of streaming
  media: sun6i: Fix CSI regmap's max_register
  media: lgdt330x: fix lock status reporting
  media: imx: prpencvf: Stop upstream before disabling IDMA channel
  rcu: Do RCU GP kthread self-wakeup from softirq and interrupt
  tpm: Unify the send callback behaviour
  tpm/tpm_crb: Avoid unaligned reads in crb_recv()
  x86/ftrace: Fix warning and considate ftrace_jmp_replace() and 
ftrace_call_replace()
  x86/kvmclock: set offset for kvm unstable clock
  md: Fix failed allocation of md_register_thread
  perf intel-pt: Fix divide by zero when TSC is not available
  perf/x86/intel/uncore: Fix client IMC events return huge result
  perf intel-pt: Fix overlap calculation for padding
  perf auxtrace: Define auxtrace record alignment
  perf tools: Fix split_kallsyms_for_kcore() for trampoline symbols
  perf intel-pt: Fix CYC timestamp calculation after OVF
  x86/unwind/orc: Fix ORC unwind table alignment
  vt: perform safe console erase in the right order
  stable-kernel-rules.rst: add link to networking patch queue
  bcache: use (REQ_META|REQ_PRIO) to indicate bio for metadata
  bcache: treat stale && dirty keys as bad keys
- bcache: never writeback a discard operation
  PM / OPP: Update performance state when freq == old_freq
  PM / wakeup: Rework wakeup source timer cancellation
  svcrpc: fix UDP on servers with lots of threads
  NFSv4.1: Reinitialise sequence results before retransmitting a request
  nfsd: fix wrong check in write_v4_end_grace()
  nfsd: fix memory corruption caused by readdir
  nfsd: fix performance-limiting session calculation
  NFS: Don't recoalesce on error in nfs_pageio_complete_mirror()
  NFS: Fix an I/O request leakage in nfs_do_recoalesce
  NFS: Fix I/O request leakages
  cpuidle: governor: Add new governors to cpuidle_governors again
  cpcap-charger: generate events for userspace
  mfd: sm501: Fix potential NULL pointer dereference
  media: cx25840: mark pad sig_types to fix cx231xx init
  dm integrity: limit the rate of error messages
  dm: fix to_sector() for 32bit
  ipmi_si: fix use-after-free of resource->name
  ipmi_si: Fix crash when using hard-coded device
  Revert "KVM/MMU: Flush tlb directly in the kvm_zap_gfn_range()"
  arm64: KVM: Fix architecturally invalid reset value for FPEXC32_EL2
  arm64: debug: Ensure debug handlers check triggering exception 

[Kernel-packages] [Bug 1818854] Re: [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures

2019-03-25 Thread Frank Heimes
Kernel SRU request submitted: 
https://lists.ubuntu.com/archives/kernel-team/2019-March/099478.html
https://lists.ubuntu.com/archives/kernel-team/2019-March/thread.html#99478

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ 
+ * The vfio-ap driver will create a matrix device in sysfs without a
+ subsystem link.
+ 
+ * This causes failures in libudev that might also lead to libvirt
+ errors.
+ 
+ * A fix is upstream in master branch for kernel 5.1
+ 
+ [Fix]
+ 
+ * 36360658eb5a6cf04bb9f2704d1e4ce54037ec99 3636065 "s390: vfio_ap: link
+ the vfio_ap devices to the vfio_ap bus subsystem"
+ 
+ [Test Case]
+ 
+ * An s390x machine with at least one CryptoExpress card,
+   where at least one AP and one 'Domain' is assigned to a particular LPAR.
+ 
+ * Now running virsh nodedev-list before (and later after) construction
+ the matrix device should expose the issue.
+ 
+ * For details about how to setup a vfio-ap matrix device see: 
http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html
+   (see 2nd bullet: virtio-ap)
+ 
+ [Regression Potential]
+ 
+ * The regression potential can be considered as low since it only
+ affects the s390x platform
+ 
+ * and there it only affects the usage of AP (CryptoExpress) cards and
+ it's driver/module
+ 
+ * and again only affects the recently introduced virtual IO function of
+ AP (vfio-ap).
+ 
+ [Other Info]
+ 
+ * It was already briefly discussed here:
+   https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html
+   as well as reviewed and pushed.
+ 
+ * Commit 3636065 from v5.1-rc1
+ 
+ * This affects ccw cards and their vf only, NOT vf of PCI/PCIe cards!
+ 
+ * For details on virtio-ap/vfio-ap see bullet #2 here: 
http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html
+ _
+ 
  ---Problem Description---
  The vfio-ap driver will create a matrix device in sysfs without a subsystem 
link. This triggers failures in libudev that might also lead to libvirt errors 
(e.g. see 
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html)
  
  The proper fix is to add a subsystem link (e.g. by providing a dummy
  bus).
  
- 
  A fix for that is upstream in master branch already for kernel 5.1
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99
  
  This  need to be applied to Bionic, Cosmic and Disco

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

Title:
  [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev
  failures

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  * The vfio-ap driver will create a matrix device in sysfs without a
  subsystem link.

  * This causes failures in libudev that might also lead to libvirt
  errors.

  * A fix is upstream in master branch for kernel 5.1

  [Fix]

  * 36360658eb5a6cf04bb9f2704d1e4ce54037ec99 3636065 "s390: vfio_ap:
  link the vfio_ap devices to the vfio_ap bus subsystem"

  [Test Case]

  * An s390x machine with at least one CryptoExpress card,
where at least one AP and one 'Domain' is assigned to a particular LPAR.

  * Now running virsh nodedev-list before (and later after) construction
  the matrix device should expose the issue.

  * For details about how to setup a vfio-ap matrix device see: 
http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html
(see 2nd bullet: virtio-ap)

  [Regression Potential]

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

  * and there it only affects the usage of AP (CryptoExpress) cards and
  it's driver/module

  * and again only affects the recently introduced virtual IO function
  of AP (vfio-ap).

  [Other Info]

  * It was already briefly discussed here:
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html
as well as reviewed and pushed.

  * Commit 3636065 from v5.1-rc1

  * This affects ccw cards and their vf only, NOT vf of PCI/PCIe cards!

  * For details on virtio-ap/vfio-ap see bullet #2 here: 
http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html
  _

  ---Problem Description---
  The vfio-ap driver will create a matrix device in sysfs without a subsystem 
link. This triggers failures in libudev that might also lead to libvirt errors 
(e.g. see 
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html)

  The proper fix is to add a subsystem link (e.g. by providing a dummy
  bus).

  A fix for that is upstream in master branch already for kernel 5.1

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99

  This  need to be applied to Bionic, Cosmic and Disco

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1821607] [NEW] Disco update: v5.0.4 upstream stable release

2019-03-25 Thread Seth Forshee
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:

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

Linux 5.0.4
SUNRPC: Respect RPC call timeouts when retrying transmission
SUNRPC: Fix up RPC back channel transmission
SUNRPC: Prevent thundering herd when the socket is not connected
s390/setup: fix boot crash for machine without EDAT-1
net: dsa: lantiq_gswip: fix OF child-node lookups
net: dsa: lantiq_gswip: fix use-after-free on failed probe
KVM: nVMX: Check a single byte for VMCS "launched" in nested early checks
KVM: nVMX: Ignore limit checks on VMX instructions using flat segments
KVM: nVMX: Apply addr size mask to effective address for VMX instructions
KVM: nVMX: Sign extend displacements of VMX instr's mem operands
KVM: x86/mmu: Do not cache MMIO accesses while memslots are in flux
KVM: x86/mmu: Detect MMIO generation wrap in any address space
KVM: VMX: Zero out *all* general purpose registers after VM-Exit
KVM: VMX: Compare only a single byte for VMCS' "launched" in vCPU-run
KVM: Call kvm_arch_memslots_updated() before updating memslots
drm/amd/display: don't call dm_pp_ function from an fpu block
drm/amd/powerplay: correct power reading on fiji
drm/radeon/evergreen_cs: fix missing break in switch statement
drm/fb-helper: generic: Fix drm_fbdev_client_restore()
media: imx: csi: Stop upstream before disabling IDMA channel
media: imx: csi: Disable CSI immediately after last EOF
media: imx-csi: Input connections to CSI should be optional
media: vimc: Add vimc-streamer for stream control
media: uvcvideo: Avoid NULL pointer dereference at the end of streaming
media: sun6i: Fix CSI regmap's max_register
media: lgdt330x: fix lock status reporting
media: imx: prpencvf: Stop upstream before disabling IDMA channel
rcu: Do RCU GP kthread self-wakeup from softirq and interrupt
tpm: Unify the send callback behaviour
tpm/tpm_crb: Avoid unaligned reads in crb_recv()
x86/ftrace: Fix warning and considate ftrace_jmp_replace() and 
ftrace_call_replace()
x86/kvmclock: set offset for kvm unstable clock
md: Fix failed allocation of md_register_thread
perf intel-pt: Fix divide by zero when TSC is not available
perf/x86/intel/uncore: Fix client IMC events return huge result
perf intel-pt: Fix overlap calculation for padding
perf auxtrace: Define auxtrace record alignment
perf tools: Fix split_kallsyms_for_kcore() for trampoline symbols
perf intel-pt: Fix CYC timestamp calculation after OVF
x86/unwind/orc: Fix ORC unwind table alignment
vt: perform safe console erase in the right order
stable-kernel-rules.rst: add link to networking patch queue
bcache: use (REQ_META|REQ_PRIO) to indicate bio for metadata
bcache: treat stale && dirty keys as bad keys
PM / OPP: Update performance state when freq == old_freq
PM / wakeup: Rework wakeup source timer cancellation
svcrpc: fix UDP on servers with lots of threads
NFSv4.1: Reinitialise sequence results before retransmitting a request
nfsd: fix wrong check in write_v4_end_grace()
nfsd: fix memory corruption caused by readdir
nfsd: fix performance-limiting session calculation
NFS: Don't recoalesce on error in nfs_pageio_complete_mirror()
NFS: Fix an I/O request leakage in nfs_do_recoalesce
NFS: Fix I/O request leakages
cpuidle: governor: Add new governors to cpuidle_governors again
cpcap-charger: generate events for userspace
mfd: sm501: Fix potential NULL pointer dereference
media: cx25840: mark pad sig_types to fix cx231xx init
dm integrity: limit the rate of error messages
dm: fix to_sector() for 32bit
ipmi_si: fix use-after-free of resource->name
ipmi_si: Fix crash when using hard-coded device
Revert "KVM/MMU: Flush tlb directly in the kvm_zap_gfn_range()"
arm64: KVM: Fix architecturally invalid reset value for FPEXC32_EL2
arm64: debug: Ensure debug handlers check triggering exception level
arm64: debug: Don't propagate UNKNOWN FAR into si_code for debug signals
arm64: Fix HCR.TGE status for NMI contexts
ARM: s3c24xx: Fix boolean expressions in osiris_dvs_notify
powerpc/traps: Fix the message printed when stack overflows
powerpc/traps: fix recoverability of machine check handling on book3s/32
powerpc/smp: Fix NMI IPI xmon timeout
powerpc/smp: Fix NMI IPI timeout
powerpc/hugetlb: Don't do runtime allocation of 16G pages in LPAR configuration
powerpc/ptrace: Simplify vr_get/set() to avoid GCC warning
powerpc: Fix 32-bit KVM-PR lockup and host crash with MacOS guest
powerpc/64s/hash: Fix assert_slb_presence() use of the slbfee. instruction
powerpc/powernv: Don't reprogram SLW image on every KVM guest entry/exit
powerpc/kvm: Save and restore host 

[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819660
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Pending -- Ready
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe)
  derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 
(linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 
(linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 23:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 18/beta channel
-   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-47.50 -proposed tracker

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

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

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

  backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe)
  derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 
(linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 
(linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 23:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819621] Re: linux-kvm: 4.18.0-1009.9 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

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

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

Title:
  linux-kvm: 4.18.0-1009.9 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Friday, 15. March 2019 08:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.4.0-1078.88 -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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

2019-03-25 Thread Scott Smith
Are there repro steps that can be passed along to test?

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

Title:
  bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

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

Bug description:
  [Impact]

  The bnxt_en_bpo driver experienced tx timeouts causing the system to
  experience network stalls and fail to send data and heartbeat packets.

  The following 25Gb Broadcom NIC error was seen on Xenial
  running the 4.4.0-141-generic kernel on an amd64 host
  seeing moderate-heavy network traffic (just once):

  * The bnxt_en_po driver froze on a "TX timed out" error
    and triggered the Netdev Watchdog timer under load.

  * From kernel log:
    "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out"
    See attached kern.log excerpt file for full excerpt of error log.

  * Release = Xenial
    Kernel = 4.4.0-141-generic #167
    eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet

  * This caused the driver to reset in order to recover:

    "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting
  reset task!"

    driver: bnxt_en_bpo
    version: 1.8.1
    source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout()

  * The loss of connectivity and softirq stall caused other failures
    on the system.

  * The bnxt_en_po driver is the imported Broadcom driver
    pulled in to support newer Broadcom HW (specific boards)
    while the bnx_en module continues to support the older
    HW. The current Linux upstream driver does not compile
    easily with the 4.4 kernel (too many changes).

  * This upstream and bnxt_en driver fix is a likely solution:
     "bnxt_en: Fix TX timeout during netpoll"
     commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906

    This fix has not been applied to the bnxt_en_po driver
    version, but review of the code indicates that it is
    susceptible to the bug, and the fix would be reasonable.

  [Test Case]

  * Unfortunately, this is not easy to reproduce. Also, it is only seen
  on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo
  driver.

  [Regression Potential]

  * The patch is restricted to the bpo driver, with very constrained
  scope - just the newest Broadcom NICs being used by the Xenial 4.4
  kernel (as opposed to the hwe 4.15 etc. kernels, which would have the
  in-tree fixed driver).

  * The patch is very small and backport is fairly minimal and simple.

  * The fix has been running on the in-tree driver in upstream mainline
  as well as the Ubuntu Linux in-tree driver, although the Broadcom
  driver has a lot of lower level code that is different, this piece is
  still the same.

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

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


[Kernel-packages] [Bug 1820605] Re: linux-azure: 5.0.0-1001.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
  phase: Testing
  phase-changed: Saturday, 23. March 2019 21:37 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
stakeholder-signoff: Pending -- waiting for signoff

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

Title:
  linux-azure: 5.0.0-1001.1 -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:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Disco:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
  phase: Testing
  phase-changed: Saturday, 23. March 2019 21:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

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

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


[Kernel-packages] [Bug 1819699] Re: linux-kvm: 4.15.0-1031.31 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819716
  phase: Testing
  phase-changed: Friday, 15. March 2019 08:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.15.0-1031.31 -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:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Friday, 15. March 2019 08:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819660] Re: linux: 4.4.0-144.170 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819658 (trusty/linux-aws), bug 1819659 
(trusty/linux-lts-xenial)
  derivatives: bug 1819653 (linux-aws), bug 1819654 (linux-euclid), bug 1819655 
(linux-kvm), bug 1819656 (linux-raspi2), bug 1819657 (linux-snapdragon), bug 
1820326 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-144.170 -proposed tracker

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

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

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

  backports: bug 1819658 (trusty/linux-aws), bug 1819659 
(trusty/linux-lts-xenial)
  derivatives: bug 1819653 (linux-aws), bug 1819654 (linux-euclid), bug 1819655 
(linux-kvm), bug 1819656 (linux-raspi2), bug 1819657 (linux-snapdragon), bug 
1820326 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819698] Re: linux-gcp: 4.15.0-1029.31 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819695 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 18/beta channel
-   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1029.31 -proposed tracker

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

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

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

  backports: bug 1819695 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 18:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
- phase: Promote to Proposed
- phase-changed: Monday, 25. March 2019 10:11 UTC
+ phase: Testing
+ phase-changed: Monday, 25. March 2019 15:03 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   automated-testing: Ongoing -- testing in progress
+   promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: Pending -- snap not in beta channel
+   snap-release-to-edge: Pending -- snap not in edge channel
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1029
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 22. March 2019 13:33 UTC
+ phase: Testing
+ phase-changed: Monday, 25. March 2019 15:07 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Pending -- ready for review
+   automated-testing: Pending -- Ready
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Monday, 25. March 2019 15:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Pending -- Ready
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1820310] Re: linux-gcp: 5.0.0-1001.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
- phase: Testing
- phase-changed: Saturday, 23. March 2019 21:03 UTC
+ phase: Ready for Testing
+ phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 5.0.0-1001.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 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:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Disco:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
  phase: Ready for Testing
  phase-changed: Monday, 25. March 2019 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

Title:
  linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819704
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 14:08 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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


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

2019-03-25 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-25 10:39 EDT---
Steps to reproduce the issue:

In order to reproduce the behavior, it is necessary to have a crypto
adapter assigned to the hypervisor LPAR.

The following link contains instructions on how to setup a vfio-ap
matrix device.

http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html

Running virsh nodedev-list before and after construction the matrix device 
should expose the issue.
If libvirt bails out on the vfio-ap device, all devices that would be scanned 
subsequently will vanish from the returned list of devices.

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

Title:
  [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev
  failures

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  The vfio-ap driver will create a matrix device in sysfs without a subsystem 
link. This triggers failures in libudev that might also lead to libvirt errors 
(e.g. see 
https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html)

  The proper fix is to add a subsystem link (e.g. by providing a dummy
  bus).

  
  A fix for that is upstream in master branch already for kernel 5.1

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99

  This  need to be applied to Bionic, Cosmic and Disco

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

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


[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1819616 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 18/beta channel
-   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   snap-release-to-candidate: Pending -- snap not in 18/candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1014.14~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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

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

  derivatives: bug 1819616 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
-   snap-release-to-edge: Pending -- snap not in 18-pi3/edge channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819693 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in 18/beta channel
-   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1035.37 -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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in 18/candidate channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-release-to-candidate: Pending -- snap not in candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1041.45 -proposed tracker

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

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

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

  backports: bug 1819711 (trusty/linux-azure)
  derivatives: bug 1819710 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819704
- phase: Promote to Proposed
- phase-changed: Thursday, 21. March 2019 14:08 UTC
+ phase: Testing
+ phase-changed: Monday, 25. March 2019 14:59 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819704
  phase: Testing
  phase-changed: Monday, 25. March 2019 14:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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 snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.8 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1819660
- phase: Promote to Proposed
- phase-changed: Friday, 22. March 2019 16:11 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 25. March 2019 14:54 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-fips: 4.4.0-1007.8 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. March 2019 14:54 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


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

2019-03-25 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 1821597

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

Title:
  USB suspend / resume with docking station and laptop lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The components:
  - Dell Precision M4800 laptop
  - Dell docking station, with USB keyboard attached

  Ubuntu 16.04 installed

  Test case A) Booting in Docking Station with laptop lid closed:
  ===
  Boot will proceed through unlocking disk encryption. When graphical user 
interface starts, screen will go black and start spewing `unable to enumerate 
USB device on port` messages

  
  Test case B) In docking station, close lid and resume:
  =
  If laptop lid is closed when resuming from suspend, screen will go black and 
start spewing `unable to enumerate USB device on port` messages

  
  Test case C) Suspend without docking station (this one works):
  ==
  1. Boot to laptop without docking station attached
  2. Suspend
  3. Attach to docking station with lid closed
  4. Resume

  C) is currently the only case where everything works properly.

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

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


[Kernel-packages] [Bug 1821597] [NEW] USB suspend / resume with docking station and laptop lid closed

2019-03-25 Thread Eero Aaltonen
Public bug reported:

The components:
- Dell Precision M4800 laptop
- Dell docking station, with USB keyboard attached

Ubuntu 16.04 installed

Test case A) Booting in Docking Station with laptop lid closed:
===
Boot will proceed through unlocking disk encryption. When graphical user 
interface starts, screen will go black and start spewing `unable to enumerate 
USB device on port` messages


Test case B) In docking station, close lid and resume:
=
If laptop lid is closed when resuming from suspend, screen will go black and 
start spewing `unable to enumerate USB device on port` messages


Test case C) Suspend without docking station (this one works):
==
1. Boot to laptop without docking station attached
2. Suspend
3. Attach to docking station with lid closed
4. Resume

C) is currently the only case where everything works properly.

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

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

Title:
  USB suspend / resume with docking station and laptop lid closed

Status in linux package in Ubuntu:
  New

Bug description:
  The components:
  - Dell Precision M4800 laptop
  - Dell docking station, with USB keyboard attached

  Ubuntu 16.04 installed

  Test case A) Booting in Docking Station with laptop lid closed:
  ===
  Boot will proceed through unlocking disk encryption. When graphical user 
interface starts, screen will go black and start spewing `unable to enumerate 
USB device on port` messages

  
  Test case B) In docking station, close lid and resume:
  =
  If laptop lid is closed when resuming from suspend, screen will go black and 
start spewing `unable to enumerate USB device on port` messages

  
  Test case C) Suspend without docking station (this one works):
  ==
  1. Boot to laptop without docking station attached
  2. Suspend
  3. Attach to docking station with lid closed
  4. Resume

  C) is currently the only case where everything works properly.

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

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


[Kernel-packages] [Bug 1820326] Re: linux-fips: 4.4.0-1007.8 -proposed tracker

2019-03-25 Thread Andy Whitcroft
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
-   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Friday, 22. March 2019 16:11 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- review in progress

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

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

Title:
  linux-fips: 4.4.0-1007.8 -proposed tracker

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

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

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

  -- swm properties --
  kernel-stable-master-bug: 1819660
  phase: Promote to Proposed
  phase-changed: Friday, 22. March 2019 16:11 UTC
  reason:
    promote-to-proposed: Ongoing -- review in progress

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

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


[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-03-25 Thread Mauricio Faria de Oliveira
Updating bug tags to verification done.

As mentioned by users in this LP bug, the verification period of 5 days
is _usually_ not enough to reproduce this problem, however, we have some
datapoints that support the fix is good.

1) The fix has been first delivery in linux-azure, 3 weeks ago, and has
reportedly resolved the issue for @alanjcastonguay: the issue was
experienced within 4 days at the most, and hasn't happened for 2 weeks
in 8 nodes (which is statistically very positive; and it helps that the
fix is not specific to -azure).

2) One of the users who reported this in linux (-generic), has verified
a test kernel with this fix for weeks, based upon which the fix has been
submitted after linux-azure had it. The same user has verified -proposed
for about a week now, and it's looking good.

3) Users in this LP bug have been running the -proposed kernel in
multiple nodes for about a week now too, and haven't hit the issue yet.

On top of 1), with 2) and 3) combined, and the schedule for -proposed
verification, this seems to be a reasonable compromise between results
and test time.

cheers,
Mauricio

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

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  

[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

2019-03-25 Thread Jamie Strandboge
Are there additional steps that need to occur?

** Changed in: iptables (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/1820114

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

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

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

2019-03-25 Thread Jamie Strandboge
FYI, I cannot reproduce this with even less memory:

$ iptables --version
iptables v1.6.1

$ free
  totalusedfree  shared  buff/cache   available
Mem: 265712  114824   667441024   84144   36024
Swap: 0   0   0

$ cat /proc/version_signature
Ubuntu 5.0.0-7.8-generic 5.0.0

$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

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

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1815831] Re: [ALSA] [PATCH] System76 darp5 and oryp5 fixups

2019-03-25 Thread Seth Forshee
The xenial hwe kernel uses the same source as the bionic kernel, so
getting it into bionic also gets it into the xenial hwe kernel.

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

Title:
  [ALSA] [PATCH] System76 darp5 and oryp5 fixups

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

Bug description:
  SRU Justification

  Impact: The System76 darp5 and oryp5 platforms need audio driverquirks
  to fix up the pin configuration.

  Fix: One backport from upstream, and one cherry pick from the upstream
  sound tree.

  Test Case: Backports have been tested on the affected hardware.

  Regression Potential: These are quirks for specific PCI device ids and
  thus are not expected to introduce regressions for any other hardware.

  ---

  Two fixups are needed to support the headset microphone on the
  System76 darp5 and oryp5. The darp5 patch is attached here, the oryp5
  patch will be attached on the next comment.

  On the System76 Darter Pro (darp5), there is a headset microphone
  input attached to 0x1a that does not have a jack detect. In order to
  get it working, the pin configuration needs to be set correctly, and
  the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied.
  This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops,
  except we have a separate microphone jack that is already configured
  correctly.

  On the System76 Oryx Pro (oryp5), there is a headset microphone input
  attached to 0x19 that does not have a jack detect. In order to get it
  working, the pin configuration needs to be set correctly, and the
  ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is
  similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we
  have a separate microphone jack that is already configured correctly.
  Since the ALC1220 does not have a fixup similar to
  ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC, I have exposed the fixup from the
  ALC269 in a way that it can be accessed from the
  alc1220_fixup_system76_oryp5 function. In addition, the
  alc1220_fixup_clevo_p950 needs to be applied to gain speaker output.

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

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


[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

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

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

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

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-base source package in Xenial:
  Confirmed

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

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

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


[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

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

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

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

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-base source package in Xenial:
  Confirmed

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

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

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


[Kernel-packages] [Bug 1773897]

2019-03-25 Thread bugzilla
(In reply to Kai-Heng Feng from comment #9)
> My intention is to ask you to try adding this entry to pin-code-database.xml:
> 

See https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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


[Kernel-packages] [Bug 1813721] Re: SECURITY_SELINUX_DISABLE should be enable on X s390x

2019-03-25 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu)
   Status: Won't Fix => 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/1813721

Title:
  SECURITY_SELINUX_DISABLE should be enable on X s390x

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

Bug description:
  This test from q-r-t has failed exclusively on Xenial s390x:
==
FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2158, in 
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
  File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be set in 
the kernel config

--

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-142-generic 4.4.0-142.168
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Jan 29 02:30:42 2019
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-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/1813721/+subscriptions

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


[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-25 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. March 2019 13:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1821573] Re: Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

2019-03-25 Thread Po-Hsu Lin
Tried old 4.15 kernels on Xenial.

4.15.0-43
4.15.0-45
4.15.0-46 (updates)
4.15.0-47 (proposed)

Non of them are working, however we got test reports from this node for
4.15.0-45 and 4.15.0-43.

So it looks like a (strange) HW issue to me.


** Tags removed: regression-release

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

Title:
  Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

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

Bug description:
  Node "amaura" cannot be deployed with Bionic / Cosmic / Disco image.

  
  I tried to connect to the IPMI console, there is no output after the prompt:
  Press  to enter setup,  Boot Menu,  Network Boot

  
  The system can be deployed with T/X without any issue, I tried to install the 
4.15 HWE kernel on it, but it's not working as well.

  BTW, I can see some RAM related messages probably indicates a hardware issue, 
not sure if it has something to do with that.
  [0.00] *BAD*gran_size: 4M chunk_size: 128Mnum_reg: 10 
lose cover RAM: -112M
  [0.00] *BAD*gran_size: 4M chunk_size: 256Mnum_reg: 10 
lose cover RAM: -128M
  [0.00] *BAD*gran_size: 4M chunk_size: 512Mnum_reg: 10 
lose cover RAM: -192M
  [0.00] *BAD*gran_size: 4M chunk_size: 1G  num_reg: 10 lose 
cover RAM: -192M
  [0.00] *BAD*gran_size: 4M chunk_size: 2G  num_reg: 10 lose 
cover RAM: -192M
  [0.00]  gran_size: 8M chunk_size: 8M  num_reg: 10 lose 
cover RAM: 0G
  [0.00] *BAD*gran_size: 8M chunk_size: 16M num_reg: 10 
lose cover RAM: -8M
  
  [0.00]  gran_size: 256M   chunk_size: 1G  num_reg: 5  lose 
cover RAM: 232M
  [0.00]  gran_size: 256M   chunk_size: 2G  num_reg: 5  lose 
cover RAM: 232M
  [0.00]  gran_size: 512M   chunk_size: 512Mnum_reg: 5  
lose cover RAM: 488M
  [0.00]  gran_size: 512M   chunk_size: 1G  num_reg: 5  lose 
cover RAM: 488M
  [0.00]  gran_size: 512M   chunk_size: 2G  num_reg: 5  lose 
cover RAM: 488M
  [0.00]  gran_size: 1G chunk_size: 1G  num_reg: 4  lose 
cover RAM: 1000M
  [0.00]  gran_size: 1G chunk_size: 2G  num_reg: 5  lose 
cover RAM: 1000M
  [0.00]  gran_size: 2G chunk_size: 2G  num_reg: 2  lose 
cover RAM: 3048M
  [0.00] mtrr_cleanup: can not find optimal value
  [0.00] please specify mtrr_gran_size/mtrr_chunk_size
  [0.00] e820: last_pfn = 0x4e000 max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fc980-0x000fc98f] mapped at 
[880fc980]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] Using GB pages for direct mapping
  [0.00] RAMDISK: [mem 0x33466000-0x35a2afff]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.15.0.47.68
  ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Mar 25 09:51:36 2019
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1715577] Re: linux-aws package lacks zram.ko, but builds it.

2019-03-25 Thread Ricardo Cescon
switched for tests to generic kernel (currently without other problems),
but hope it will be fixed soon for aws kernel

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

Title:
  linux-aws package lacks zram.ko, but builds it.

Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  The linux-aws package lacks zram.ko module, but according to delivered
  /boot/config-*-aws, the zram is built. Would it be possible to add the
  zram module into linux-aws package in Ubuntu 16.04 just like linux-
  image-lowlatency have? (Or via linux-image-extra packages, like other
  variants have)

  I've checked linux-aws-4.4.0.1032.34 and no module is present there,
  the 'apt-file search zram.ko' did not yield any of the 'aws' packages.

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

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


[Kernel-packages] [Bug 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-25 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. March 2019 13:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Promote to Proposed
  phase-changed: Monday, 25. March 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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


[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

2019-03-25 Thread Zygmunt Krynicki
This has been fixed now. Marking it as such.

** Project changed: snappy => snapd

** Changed in: snapd
   Status: In Progress => 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/1567597

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in snapd:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in libseccomp source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Test Case]

  All of the libseccomp test cases apply here.

  

  Running the seccomp kernel selftests is also a great to exercise
  seccomp and the kernel patch set proposed for the SRU includes
  additional seccomp selftests. To build, enter into the root of the
  kernel source tree and build the seccomp test binary:

  $ make -C tools/testing/selftests TARGETS=seccomp

  Now you can execute 

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

2019-03-25 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 1821573

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

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

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

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

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

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

Title:
  Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

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

Bug description:
  Node "amaura" cannot be deployed with Bionic / Cosmic / Disco image.

  
  I tried to connect to the IPMI console, there is no output after the prompt:
  Press  to enter setup,  Boot Menu,  Network Boot

  
  The system can be deployed with T/X without any issue, I tried to install the 
4.15 HWE kernel on it, but it's not working as well.

  BTW, I can see some RAM related messages probably indicates a hardware issue, 
not sure if it has something to do with that.
  [0.00] *BAD*gran_size: 4M chunk_size: 128Mnum_reg: 10 
lose cover RAM: -112M
  [0.00] *BAD*gran_size: 4M chunk_size: 256Mnum_reg: 10 
lose cover RAM: -128M
  [0.00] *BAD*gran_size: 4M chunk_size: 512Mnum_reg: 10 
lose cover RAM: -192M
  [0.00] *BAD*gran_size: 4M chunk_size: 1G  num_reg: 10 lose 
cover RAM: -192M
  [0.00] *BAD*gran_size: 4M chunk_size: 2G  num_reg: 10 lose 
cover RAM: -192M
  [0.00]  gran_size: 8M chunk_size: 8M  num_reg: 10 lose 
cover RAM: 0G
  [0.00] *BAD*gran_size: 8M chunk_size: 16M num_reg: 10 
lose cover RAM: -8M
  
  [0.00]  gran_size: 256M   chunk_size: 1G  num_reg: 5  lose 
cover RAM: 232M
  [0.00]  gran_size: 256M   chunk_size: 2G  num_reg: 5  lose 
cover RAM: 232M
  [0.00]  gran_size: 512M   chunk_size: 512Mnum_reg: 5  
lose cover RAM: 488M
  [0.00]  gran_size: 512M   chunk_size: 1G  num_reg: 5  lose 
cover RAM: 488M
  [0.00]  gran_size: 512M   chunk_size: 2G  num_reg: 5  lose 
cover RAM: 488M
  [0.00]  gran_size: 1G chunk_size: 1G  num_reg: 4  lose 
cover RAM: 1000M
  [0.00]  gran_size: 1G chunk_size: 2G  num_reg: 5  lose 
cover RAM: 1000M
  [0.00]  gran_size: 2G chunk_size: 2G  num_reg: 2  lose 
cover RAM: 3048M
  [0.00] mtrr_cleanup: can not find optimal value
  [0.00] please specify mtrr_gran_size/mtrr_chunk_size
  [0.00] e820: last_pfn = 0x4e000 max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fc980-0x000fc98f] mapped at 
[880fc980]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] Using GB pages for direct mapping
  [0.00] RAMDISK: [mem 0x33466000-0x35a2afff]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.15.0.47.68
  ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Mar 25 09:51:36 2019
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1819663] Re: linux: 3.13.0-168.218 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819662 (precise/linux-lts-trusty)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 23:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 3.13.0-168.218 -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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

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

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

  backports: bug 1819662 (precise/linux-lts-trusty)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 15. March 2019 23:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1821573] Re: Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

2019-03-25 Thread Po-Hsu Lin
** Tags added: regression-release

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

Title:
  Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

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

Bug description:
  Node "amaura" cannot be deployed with Bionic / Cosmic / Disco image.

  
  I tried to connect to the IPMI console, there is no output after the prompt:
  Press  to enter setup,  Boot Menu,  Network Boot

  
  The system can be deployed with T/X without any issue, I tried to install the 
4.15 HWE kernel on it, but it's not working as well.

  BTW, I can see some RAM related messages probably indicates a hardware issue, 
not sure if it has something to do with that.
  [0.00] *BAD*gran_size: 4M chunk_size: 128Mnum_reg: 10 
lose cover RAM: -112M
  [0.00] *BAD*gran_size: 4M chunk_size: 256Mnum_reg: 10 
lose cover RAM: -128M
  [0.00] *BAD*gran_size: 4M chunk_size: 512Mnum_reg: 10 
lose cover RAM: -192M
  [0.00] *BAD*gran_size: 4M chunk_size: 1G  num_reg: 10 lose 
cover RAM: -192M
  [0.00] *BAD*gran_size: 4M chunk_size: 2G  num_reg: 10 lose 
cover RAM: -192M
  [0.00]  gran_size: 8M chunk_size: 8M  num_reg: 10 lose 
cover RAM: 0G
  [0.00] *BAD*gran_size: 8M chunk_size: 16M num_reg: 10 
lose cover RAM: -8M
  
  [0.00]  gran_size: 256M   chunk_size: 1G  num_reg: 5  lose 
cover RAM: 232M
  [0.00]  gran_size: 256M   chunk_size: 2G  num_reg: 5  lose 
cover RAM: 232M
  [0.00]  gran_size: 512M   chunk_size: 512Mnum_reg: 5  
lose cover RAM: 488M
  [0.00]  gran_size: 512M   chunk_size: 1G  num_reg: 5  lose 
cover RAM: 488M
  [0.00]  gran_size: 512M   chunk_size: 2G  num_reg: 5  lose 
cover RAM: 488M
  [0.00]  gran_size: 1G chunk_size: 1G  num_reg: 4  lose 
cover RAM: 1000M
  [0.00]  gran_size: 1G chunk_size: 2G  num_reg: 5  lose 
cover RAM: 1000M
  [0.00]  gran_size: 2G chunk_size: 2G  num_reg: 2  lose 
cover RAM: 3048M
  [0.00] mtrr_cleanup: can not find optimal value
  [0.00] please specify mtrr_gran_size/mtrr_chunk_size
  [0.00] e820: last_pfn = 0x4e000 max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fc980-0x000fc98f] mapped at 
[880fc980]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] Using GB pages for direct mapping
  [0.00] RAMDISK: [mem 0x33466000-0x35a2afff]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.15.0.47.68
  ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Mar 25 09:51:36 2019
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

2019-03-25 Thread Louis Bouchard
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux-base source package in Xenial:
  New

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

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

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


[Kernel-packages] [Bug 1819618] Re: linux-azure: 4.18.0-1014.14 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

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

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

Title:
  linux-azure: 4.18.0-1014.14 -proposed tracker

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

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

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

  backports: bug 1819617 (bionic/linux-azure)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 20:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819691] Re: linux-raspi2: 4.15.0-1033.35 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19: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: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
snap-release-to-edge: Pending -- snap not in 18-pi3/edge channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.15.0-1033.35 -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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 19:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18-pi3/beta channel
snap-release-to-edge: Pending -- snap not in 18-pi3/edge channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819698
- phase: Ready for Promote to Proposed
- phase-changed: Monday, 25. March 2019 09:28 UTC
+ phase: Promote to Proposed
+ phase-changed: Monday, 25. March 2019 10:11 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Promote to Proposed
  phase-changed: Monday, 25. March 2019 10:11 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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


[Kernel-packages] [Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** 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: 1819704
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 14:08 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819704
  phase: Promote to Proposed
  phase-changed: Thursday, 21. March 2019 14:08 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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


[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1819616 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1014.14~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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

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

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

  derivatives: bug 1819616 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819618
  phase: Testing
  phase-changed: Wednesday, 20. March 2019 19:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819693 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1035.37 -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 snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

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

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

Title:
  linux-oracle: 4.15.0-1010.12 -proposed tracker

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

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

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

  backports: bug 1819703 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Thursday, 21. March 2019 17:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1821573] [NEW] Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

2019-03-25 Thread Po-Hsu Lin
Public bug reported:

Node "amaura" cannot be deployed with Bionic / Cosmic / Disco image.


I tried to connect to the IPMI console, there is no output after the prompt:
Press  to enter setup,  Boot Menu,  Network Boot


The system can be deployed with T/X without any issue, I tried to install the 
4.15 HWE kernel on it, but it's not working as well.

BTW, I can see some RAM related messages probably indicates a hardware issue, 
not sure if it has something to do with that.
[0.00] *BAD*gran_size: 4M   chunk_size: 128Mnum_reg: 10 
lose cover RAM: -112M
[0.00] *BAD*gran_size: 4M   chunk_size: 256Mnum_reg: 10 
lose cover RAM: -128M
[0.00] *BAD*gran_size: 4M   chunk_size: 512Mnum_reg: 10 
lose cover RAM: -192M
[0.00] *BAD*gran_size: 4M   chunk_size: 1G  num_reg: 10 lose 
cover RAM: -192M
[0.00] *BAD*gran_size: 4M   chunk_size: 2G  num_reg: 10 lose 
cover RAM: -192M
[0.00]  gran_size: 8M   chunk_size: 8M  num_reg: 10 lose cover RAM: 
0G
[0.00] *BAD*gran_size: 8M   chunk_size: 16M num_reg: 10 
lose cover RAM: -8M

[0.00]  gran_size: 256M chunk_size: 1G  num_reg: 5  lose 
cover RAM: 232M
[0.00]  gran_size: 256M chunk_size: 2G  num_reg: 5  lose 
cover RAM: 232M
[0.00]  gran_size: 512M chunk_size: 512Mnum_reg: 5  
lose cover RAM: 488M
[0.00]  gran_size: 512M chunk_size: 1G  num_reg: 5  lose 
cover RAM: 488M
[0.00]  gran_size: 512M chunk_size: 2G  num_reg: 5  lose 
cover RAM: 488M
[0.00]  gran_size: 1G   chunk_size: 1G  num_reg: 4  lose cover RAM: 
1000M
[0.00]  gran_size: 1G   chunk_size: 2G  num_reg: 5  lose cover RAM: 
1000M
[0.00]  gran_size: 2G   chunk_size: 2G  num_reg: 2  lose cover RAM: 
3048M
[0.00] mtrr_cleanup: can not find optimal value
[0.00] please specify mtrr_gran_size/mtrr_chunk_size
[0.00] e820: last_pfn = 0x4e000 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fc980-0x000fc98f] mapped at 
[880fc980]
[0.00] Scanning 1 areas for low memory corruption
[0.00] Using GB pages for direct mapping
[0.00] RAMDISK: [mem 0x33466000-0x35a2afff]

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic-hwe-16.04 4.15.0.47.68
ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170
Uname: Linux 4.4.0-143-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Mar 25 09:51:36 2019
SourcePackage: linux-meta-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

** Affects: linux-meta-hwe (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

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

** Affects: linux-meta-hwe (Ubuntu Disco)
 Importance: Undecided
 Status: New


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

** Summary changed:

- Unable to boot 4.15 / 4.18 /5.0 kernel on Intel Denlow SDP
+ Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

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

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

** Also affects: linux-meta-hwe (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: linux-meta-hwe (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  Unable to boot 4.15 / 4.18 /5.0 kernel on an Intel Denlow SDP

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

[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. March 2019 09:28 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

2019-03-25 Thread Thadeu Lima de Souza Cascardo
That affects all kernels, because that needs kvm modules parameter
enable_vmware_backdoor. I am not comfortable enabling that by default on
our kernels. We could enable that during the kvm-unit-tests. But for
now, on our own branch of kvm-unit-tests, I decided to simply disable
that test to be run by default.

Cascardo.

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

Title:
  vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  Confirmed

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=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  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/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.QldMaGLdve
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 5 unexpected failures

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

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


[Kernel-packages] [Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-25 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

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

** Tags added: block-proposed-xenial

** 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: 1819698
- phase: Packaging
- phase-changed: Friday, 22. March 2019 12:38 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Monday, 25. March 2019 09:28 UTC
  reason:
-   prepare-package-meta: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- source package tags missing
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819698
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 25. March 2019 09:28 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1821537] Re: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16

2019-03-25 Thread Renne
I suggest to enable CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP in
Bionic HWE kernels as this will allow to debug via serial console with a
simple USB 3 crossover-cable (aka "USB 3.0 super-speed A-to-A debugging
cable") without the need of a physical RS-232 interface.

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

Title:
  Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP
  for serial Superspeed(+) connections with kernels >= 4.16

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

Bug description:
  Since kernel 4.13 Linux supports an USB debug console with passive USB 3.x 
host-to-host cables aka "USB 3.0 super-speed A-to-A debugging cable".
  Beginning with kernel 4.16 a serial port (/dev/ttyDbC) has been added 
(https://www.kernel.org/doc/html/v4.16/driver-api/usb/usb3-debug-port.html#serial-tty).

  I suggest to enable USB DbC by enabling the kernel options
  "CONFIG_EARLY_PRINTK_USB_XDBC=Y" and "USB_XHCI_DBGCAP=Y" in Ubuntu
  kernels >= 4.16 for Bionic HWE and newer ubuntu versions.

  It would also be great to get feedback about line speed from others as
  USB_XHCI_DBGCAP serial ports could be used for network connections via
  tun/tap devices or PPP/SLIP.

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

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


[Kernel-packages] [Bug 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

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

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

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

Title:
  vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  Confirmed

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=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  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/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.QldMaGLdve
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 5 unexpected failures

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

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


[Kernel-packages] [Bug 1765367] Re: vmware_backdoors test in kvm-unit-test failed on Artful

2019-03-25 Thread Po-Hsu Lin
*** This bug is a duplicate of bug 1821393 ***
https://bugs.launchpad.net/bugs/1821393

** This bug has been marked a duplicate of bug 1821393
   vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

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

Title:
  vmware_backdoors test in kvm-unit-test failed on Artful

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Won't Fix

Bug description:
  I believe this is a new test [1], so it should not be considered as a
  regression.

  # TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  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/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.MinDTiojkJ
  warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 8 unexpected failures

  There are several KVM changes landed into 4.17 kernel [2], maybe it is
  related.

  [1] https://www.spinics.net/lists/kvm/msg161243.html
  [2] http://lkml.iu.edu/hypermail/linux/kernel/1804.1/01739.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-39-generic 4.13.0-39.44
  ProcVersionSignature: User Name 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 19 10:07 seq
   crw-rw 1 root audio 116, 33 Apr 19 10:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  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: Thu Apr 19 10:11:49 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic.efi.signed 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1006D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1006D:bd03/01/2018:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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


[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

2019-03-25 Thread Kai-Heng Feng
Please test this kernel:
https://people.canonical.com/~khfeng/lp1821434/

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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


[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

2019-03-25 Thread You-Sheng Yang
I had a try on kernel 4.15.0-46 in Bionic with efi-pstore module loaded
as pstore backend, but I cannot reproduce that kernel panic. It really
takes more information before one can investigation more into this
issue, so apport runs, even before the panic taking place, is really
mandatory. Please give apport a chance to collect some more information
by executing `apport-collect 1821434`.

By the way, have you tried to enable efi-pstore _without_ that SATA card
installed. Maybe it's not related to efi-pstore at all?

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

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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


[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-03-25 Thread Christian Ehrhardt 
src:linux-firmware is only accepted into cosmic-proposed but still waiting in 
Bionic-unapproved.
AFAIK the current status of "Fix committed" will make it not to be seen by the 
SRU Team (at least for similar cases I had in the past).
Therefore to increase the chance to get also the Bionic portion accepted into 
-proposed lets dial back the current status of the bug task.

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

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  In Progress
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi 

  1   2   >